Comparing Intelligent Software Evolution to Chaotic Biological Evolution
Join the DZone community and get the full member experience.Join For Free
biological evolution is a different story: chaotic raise and fall of different species, without any plan and goals. new traits and variations appear all the time and many are useless or even harmful. small modifications accumulate over time, cause significant changes and emergence of new species, better adapted for the evolving world. survival of individual organisms and species is the matter of chance, pressure from environment and competition with other organisms.
intentional growth of software versus chaotic evolution of organisms... do they have anything in common?
biological evolutionin biology, evolution is the process of change in the inherited traits of a population of organisms from one generation to the next.
species - a group of organisms that can reproduce with one another and produce fertile offspring.
population - a localized group of individuals belonging to the same species.
traits - particular characteristics of an organism.
genes -portions of dna molecule, which control inherited traits.
genotype - complete set of genes within an organism's genome.
phenotype - the complete set of observable traits that make up the structure and behavior of an organism. these traits come from the interaction of its genotype with the environment.
variations - the variation in phenotypes in a population reflects the variation in these organisms' genotypes.
most of the genome of a species is identical in all individuals of that species. however, even relatively small changes in genotype can lead to dramatic changes in phenotype: chimpanzees and humans differ in only about 5% of their genomes.
mechanisms of increasing gene variations
- mutations - mistakes that occur during dna replication, which alternate version of a gene ( alleles ). mutations give the new characteristics to the organism and can have positive and negative effects.
- reshuffling of genes through sexual reproduction with random mixtures of their parents' chromosomes.
- gene flow - genes from one population enter the gene pool of another, e.g. migration between distant populations.
mechanisms of decreasing gene variations
- a process causing heritable traits that are helpful for survival and reproduction to become more common in a population, and harmful traits to become more rare. natural selection is the result of pressure from environment and competition between organisms.
- produces random changes in the frequency of traits in a population, which results from the role chance plays in whether a given individual will survive and reproduce.
though the changes produced in any one generation by drift and selection are small, differences accumulate with each subsequent generation and can, over time, cause substantial changes in the organisms.
natural selection usually predominates in large populations, while genetic drift dominates in small populations. some theories suggest that genetic drift and mutation play much larger role than natural selection in evolution.
fitness is the central concept of natural selection. fit does not necessarily mean biggest, fastest, strongest or having more children. instead fitness measures the organism's genetic contribution to the next generations - the proportion of subsequent generations that carry an organism's genes.
now we can provide another definition of evolution : the change in the gene pool of a population over time.
- adaptation - structures or behaviors that enhance a specific function, causing organisms to become better at surviving and reproducing
- co-evolution - the evolution of one species causes adaptations in a second species, such as a conflict between predator and its pray.
- mutually beneficial interactions. can be found in social insects, such as bees, termites and ants, where sterile insects feed and guard the small number of organisms in a colony that are able to reproduce.
- speciation - the process where a species diverges into two or more descendant species, mostly occurs in populations isolated geographically. it caused by gradual accumulation of small genetic changes.
- the disappearance of an entire species. indeed, virtually all animal and plant species that have lived on earth are now extinct.
software development ecosystem
the first question: what is the object of evolution in software development?
i don't have guts to suggest interbreeding most successful programmers and receive new generations of the best programmers. very impractical, too long to wait and modern people are not an easy target for experiments...
code is a good candidate. we constantly evolve and change code. but individual code doesn't have comparable set of genes and variations (unless it is a genetic algorithm or you create mutants with intensive copy and paste) and don't compete with other code for survival (only at level of products where code is one factor from many). we could apply only limited evolutionary principles to code and they are mostly related to ideas behind the software systems.
can we find a better candidate?
i believe that genome of software development is the knowledge about how to build software systems .
knowledge, dna of software development , has two components
: principles, activities, roles and flow (agile, extreme programming, scrum, cmm, rup, waterfall, cleanroom, crystal clear, swe-bok, context driven testing, etc.)
: design, programming and domain (algorithms, object oriented design and programming, design and enterprise architecture patterns, refactoring, domain driven design, behavior driven design, relational databases, web design, information architecture, usability, etc.)
in essence, this is the knowledge about what software team members do at any given time to create the system: understanding requirements, design and build, verification. humans are the best carriers of this knowledge, but it is possible to transfer it with less effective documents, books and other media. people carry huge amount of intrinsic knowledge that comes with experience, which is difficult to extract, describe and transfer to other people. our methodologies are created to represent software development knowledge (genome) in the formal way convinient to carry between people heads and projects. however, this genome immediately meets the harsh reality of environment pressure.
software development environment:
- people : experience, capabilities, skills, motivation, personalities
software needs, expectations, constraints, regulations
- customer : knowledgeability, relations and attitude
: trends, competition, standards
- technology : development platforms and tools, technical infrastructure
: goals, plans, management, culture, leadership style, resources, finances
software development ecosystem characteristics:
- populations - there are different kinds of software development (web, desktop, embedded devices; system, productivity, games; business, military, science; commercial, in-house, open source; for fun, business-critical or life-critical, etc.)
- characteristics of approaches used in software development
- software knowledge carried by individual team and used in the project to build software system
encoding of information
- contains enough information to build an individual software system
- knowledge can be passed to the next project iterations, other projects or to the whole development community
- encoding of information - contains enough information to build an individual software system
- phenotype - all the activities in software project that are outcome of interaction between this knowledge and project environment.
- ideas compete (waterfall vs. agile, procedural vs. object-oriented vs. functional programming), cooperate and enhance each other (extreme programming and scrum, refactoring and design patterns)
- mutations - continious invention and modification of the new approaches
- reshuffling - frequent recombination of various ideas
- gene flow - exchange of ideas with other populations and industries (e.g. nasa, lean manufacturing)
- software development knowledge is often under the pressure to achieve success, better meet customers needs and be effecient. better methods have more chances to survive and become more common (e.g. adoption of iterative approach that successfully solves challenge of changing requirements)
- some ideas and approaches become popular by chance, some great ideas disappear without wide acceptance. management and leadership change, politics, better sponsors, strong opinion of less qualified people, lack of knowledge about alternative approaches could play significant role in establishing far from optimal development knowledge for the project.
software development evolution is change over time in the essential knowledge about how to build software systems.
examples of software development evolutionary genes (views, ideas and activities):
|main ideas||understand requirements||design and build||verify|
|extreme programming||iterations, emergent design, customer can change mind||write user stories, customer prioritize, developers estimate||write unit test, make it work, refactor; work in pairs||build automated acceptance tests|
|cmmi||process improvement framework, five levels of maturity based on practice areas that define goals, practices and work products|
|swe-bok||guide to the software engineering body of knowledge: characterizes and organizes contents of the software engineering discipline in ten knowledge areas|
|traditional sdlc||sequential process separated into distinct phases: analysis, design, implementation, maintenance||analyze, prepare functional and technical specifications||design and build according to specifications||test according to specifications; security, performance and user acceptance testing|
|context driven testing||testing is driven by an understanding of the environment, culture, and intended use of software||exploratory testing: concurrent test design and test execution; adapt testing plans based on test results|
|domain driven design||the system design should be based on domain model||form common language between business and developers||build code that represents domain model and concepts||use automated tests for domain model assertions|
|object oriented design||a software program is the system of interacting objects||create object model for the problem space: base classes, responsibilities, collaboration; uml diagrams||find abstractions, inherit, delegate, encapsulate, package; use design patterns|
|user centered design||active participation of real users on all stages; iterations of design solutions||focus groups, interviews||participatory design||frequent usability testing|
|information architecture||organization of information and functionality to increase web site usability, intuitive navigation and findability||understand business context, content and users||build site map, wireframes, personas, user interaction scenarios|
|database design||data storage and retrieval||analyze data elements and relationship; build logical data model||relational databases: design and normalize tables, build views, stored procedures and functions|
there is no best set of ideas. success of the every software creation gene depends on interaction with a project environment. biological evolution can teach us few lessons of selecting and evolving most advantageous genes for our projects. the next post will explore these lessons.
evolution , wikipedia
introduction to evolutionary biology
Opinions expressed by DZone contributors are their own.