TRAK is a general purpose and pragmatic enterprise architecture framework which has its roots in the UK MoD's MODAF 1.2.
TRAK allows you to describe an enterprise, a concept, a solution (and its procurement) and an architecture task. In ISO/IEC 42010 terms each is a ‘system of interest’ and has stakeholders who have concerns that need to be addressed through the resulting architecture description.
TRAK provides a way of describing systems and their place in the world through architectural descriptions. The elements used to make the TRAK views is defined by the TRAK Metamodel. The TRAK views that contain these elements are each defined by a TRAK Viewpoint.
TRAK adopts the ISO/IEC 42010 / IEEE 1471 approach where
- the architecture description task sets out to answer concerns raised by the task stakeholder(s)
- a multiple view architecture description is the product of the task
- 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
Release of the TRAK Viewpoints are under the control of the TRAK Steering Group, chaired by the UK Department of Transport.
The TRAK Enterprise Architecture Framework document is a specification.
- important ideas for TRAK - general statements about TRAK - what it is, what it isn't and how it is organised
- standards affecting TRAK
- how TRAK relates to ISO/IEC 42010 (Final Committee Draft - expected issue 2011)
- overall glossary for terms used
- advice on choosing an architecture description language e.g. UML, BPMN to represent TRAK architecture views
- conformance / non-conformance with TRAK - including how to incorporate non-conforming architecture views
- TRAK architecture perspectives
- a definition of the colours used in TRAK
- TRAK Bye Laws - overall rules
- minimal modelling process for TRAK
Where Does this Fit In?
The TRAK Enterprise Architecture Framework document is part of the logical definition of TRAK.
The TRAK Enterprise Architecture Framework document invokes the other parts of the definition:
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 document is available here ...