Growth Beyond Requirements

A radar chart is sometimes called a "spider chart" because it also look vaguely like a spider web.

5

[…] Another feature of our models is that every element can be thought of as having a unique “lineage”, in that it was created by a particular updating event, which in turn was the result of some other updating event, and so on. When we introduced our models in section 2, we just said that any element created by applying a rule should be **new and distinct from all others**. If we were implementing the model, this might then make us imagine that the element would have a name based on some global counter, or a UUID.

15 images -1 interpretation SUM images -1 interpretation SUM images

But there is another, more deterministic (as well as more local and distributed) alternative: think of each new element as being a kind of encapsulation of its lineage (analogous to a chain of pointers, or to a hash like in blockchains or Git). In the evolution above, for example, we could describe element 10 by just saying it was created as part of the relation {2,10} from the relations {{2,4},{2,5}} (as the second part of the output of an update that uses them)—but then we could say that these relations were in turn created from earlier relations, and so on recursively, all the way back to the initial state of the system:

\

From Overview of United States Software Industry Results Circa 2012

Version 8.1. July 27, 2012

Copyright © 2008-2012 by Capers Jones. All rights reserved.