TRAK is an enterprise architecture framework based on the UK MoD's MODAF 1.2.
TRAK provides a way of describing systems and their place in the world through architectural models. The elements used to make the TRAK models is defined by the TRAK Metamodel. The TRAK views that contain these elements are defined by TRAK Viewpoints.
TRAK adopts the ISO/IEC/IEEE 42010:2011 approach where each viewpoint specifies an individual TRAK architecture view.
Release of the TRAK Metamodel is under the control of the TRAK Steering Group, chaired by the UK Department of Transport.
The TRAK Metamodel document is a specification. It is released under an open source GNU Free Documentation License.
- a description of the TRAK perspectives used to group views of a similar nature
- a definition of the colours used in TRAK
- TRAK Bye Laws - overall rules
- simplified TRAK metamodel. Every element and relationship on a single A3 sheet.
- a definition of every single TRAK stereotype, including those not needed for modelling.
- TRAK relationships & combinational rules
Where Does this Fit In?
The TRAK Metamodel document is one of 3 documents that defines the logical definition (free of implementation or solution) of TRAK together with:
- an overall set of requirements (e.g. colour, conformance with TRAK, Bye Laws etc)
- the architecture viewpoints that specify each architecture view - TRAK Viewpoints
The definition of TRAK is released through Sourceforge as open source.
TRAK can be implemented in a wide range of modelling tools and architecture description languages (a term taken from ISO 42010) such as UML, BPMN etc can be used to represent parts of the TRAK metamodel and therefore can be used in creating TRAK architecture views.
The TRAK metamodel document is available here ...