View Architecture Description Tuple

The basic or fundamental unit of an architecture description.


The essential point is that you need at least one node (noun) with a named relationship to itself or a named relationship between 2 nodes in order to have an architectural sentence - it should be a language with grammar (metamodel) i.e. subject - predicate - object - the basis of a sentence or an assertion. An Architecture Description Tuple may therefore be represented by a graph.

ISO/IEC/IEEE 42010 defines architecture as:

(system) fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.


Since architecture always involves relationships of elements to each other or to the “Residual World” architecture description must include these relationships. The minimum unit of architecture description is therefore a tuple - in TRAK this is represented by the TRAK::Architecture Description Tuple.

Solitons, orphans, only-children, unconnected nodes are not architecture. Remember, you can always identify a problem using a Concern and then you have the tuple - ‘Concern about TRAK::Architecture Description Element’ which can be used to convert an orphan node into a valid architecture description tuple.



© 2010 Eclectica Systems Ltd.