TRAK Architecture Framework MetamodelTRAK Metamodel
Health Warning
This web site is informative only. It is not the definitive or master source for any TRAK metamodel element. The definitive / master source is:- TRAK00002. TRAK. Enterprise Architecture Framework. Metamodel
Introduction
TRAK is an enterprise architecture framework based on the UK MoD's MODAF 1.2. but substantially different in terms of its metamodel and the way in which view content is specified and applying consistency rules across the collection of views. TRAK metamodel elements have many properties that can be used to capture/better describe real world entities.
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.
Governance
Release of the TRAK Metamodel is under the control of the TRAK Steering Group.
The TRAK Metamodel Provides Triples - Statements or Assertions - to Describe the Real World Architecture e.g. a Threat Expoiting a Vulnerability and Mitigation of the Resulting Risk
TRAK Metamodel Document
The TRAK Metamodel document is a specification. It is released under an open source GNU Free Documentation License.
- 'TRAK. Architecture Framework. Metamodel.', TRAK00002, Jun. 2024..
It contains:
- the context of the TRAK Metamodel specification with respect to the other TRAK specifications
- TRAK00004. TRAK. Architecture Framework - the overall specification and rules
- TRAK00001. TRAK. Architecture Framework. Viewpoints - specification for each TRAK architecture view
- TRAK00005. TRAK. Implementation. Architecture Description Elements - how to implement elements of the TRAK metamodel
- the TRAK metamodel
- main - the architecture description tuples (e.g. node - connector - node) most often used
- safety & security - the node elements (Event, Risk, Threat, Vulnerability, Mitigation) and triples used describe safety/security/risk
- management - the triples used to describe an architecture task and the composition of an architecture framework
- a definition of every part of the TRAK metamodel
- each triple used for every TRAK architecture view
- each node element forming a triple
- each connector element forming a triple
- each attribute used for a node and/or connector element (with allowed and default values where relevant)
- TRAK relationships & combinational rules
- rules applying to sequences of triples (e.g. 'Physical contains System' followed by 'System is configured with Resource (Job, Organisation, Physical, Role, Software and System)') with rationale
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
Metamodel diagrams provide a visual overview of the TRAK metamodel triples. The TRAK metamodel specification defines properties of the elements and rules affecting the order of use of triples.
The definition of TRAK is released through Sourceforge as open source.
The TRAK Metamodel document specifies the triples e.g. 'Claim about Organisation' (from TRAK MVp-04 Assurance Architecture Viewpoint) that form the basis for the allowed and subject matter for each TRAK architecture view. The TRAK architecture view content is specified by a set of architecture viewpoints.
Implementations of TRAK
TRAK can be implemented in a wide range of modelling tools and architecture description languagesISO/IEC/IEEE 42010:2011 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.
Where Do I Get It?
The TRAK metamodel document is available here ...
The TRAK metamodel is subject to the terms of open source license: GNU Free Documentation License (Version 1.3, November 2008) at https://www.gnu.org/licenses/fdl-1.3.html.