TRAK - started off in life in 2010 as The Rail Architecture Framework when it was thought that the result might be rail-specific. It has long-since been referred to as just TRAK without spelling out the acronym since the framework contains no rail-specific views or metamodel elements - it is domain agnostic.

TRAK is a general systems-oriented architecture framework that can be used to describe both hard and soft systems It is based on MODAF 1.2 (which evolved from DODAF) and conforms to the standard for architecture description ISO/IEC 42010.

There are important ideas behind TRAK.

TRAK has 5 architecture perspectives each of which contains a number of related views  (24 in total). The TRAK metamodel specifies the allowed object types that can be used when modelling and the relationships between them.

Each TRAK view is specified by an architectural viewpoint in accordance with ISO/IEC 42010 which states what stakeholder concerns it addresses, determines what is shown and how it is presented and how the view must be consistent with other views.

TRAK also has a set of global rules referred to as the TRAK Bye Laws.

TRAK is subject to copyright for the original parts and released under a set of open source licenses. The major differences between the TRAK metamodel elements and the MODAF metamodel elements at the initial release of TRAK are outlined separately.


© 2010 Eclectica Systems Ltd.