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 in terms of:
- the questions or concerns it is designed to answer
- a description of the view
- what you must show
- what you can show if you want
- rules to help ensure that your model remains consistent
Some examples of TRAK architecture views are included in the project gallery and can be added to by those who wish to.
Release of the TRAK Viewpoints are under the control of the TRAK Steering Group, chaired by the UK Department of Transport.
The TRAK Viewpoints document is a specification.
- 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
- minimal modelling process for TRAK.
- how to select the views needed for the task
- a definition of every single TRAK viewpoint (view)
- minimum allowed TRAK view sets
Where Does this Fit In?
The TRAK Viewpoints 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 allowed elements and relationships - TRAK Metamodel
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 Viewpoints document is available here ...