page_title: TRAK
section_title: TRAK Metamodel
hierarchical_section_title: TRAK / TRAK Metamodel
caption_attribution_description: English: Defines the Architecture Description Elements (the triples / tuples that may appear in TRAK architecture views) that describe safety, security and risk.
context_page_description: TRAK is a general enterprise architecture framework aimed at systems engineers based on MODAF 1.2.
context_section_description: The TRAK Metamodel both simplifies and extends the basic concepts within the MODAF 1.2 metamodel. It has removed and redefined stereotypes and any defence-specific constructs have been removed. The TRAK Metamodel specification contains a comparison of the TRAK metamodel at initial release against MODAF 1.2.003. This is also outlined separately.
  The TRAK metamodel is shown below. Note that this is not a controlled copy.
  Significant changes vs MODAF include:
  the TRAK metamodel is aimed at users (the MODAF M3 is an abstract UML profile intended as a specification for tool vendors to implement MODAF - there is no metamodel for users only fragments of 'simplified metamodel' which aim to represent the more complicated M3). In TRAK the metamodel shown is the master one.
  System is central to TRAK and can represent hard systems and soft systems (in MODAF 1.2.003 System is an artefact and part of the Physical Architecture and cannot include non physical parts )
  TRAK can represent any type of interface exchange / flow - information, energy or resource
  TRAK can represent exchange characteristics associated with human resources - Organisations, Jobs and Roles
  TRAK includes means to represent requirements through the Standard (document/collection) and Requirement (atomic) metamodel elements and enforced by Contract
  TRAK includes the means to plan and describe the architecture task and architecture description and its organisation as a view (MV-02 Architecture Description Design Record)
  other types of dependency and associations can be represented - physical, membership, responsibility extent
  TRAK includes the means to describe assurance cases (including design verification) using the Claim - Argument - Evidence construct
  TRAK includes the means to describe safety / security - threats/hazards, vulnerabilities, mitigations and risk and causes / impacts
  addition of ISO/IEC 42010 concepts to represent the architectural task, architecture description and architecture views - to allow a description of the task scope, purpose, findings
  addition of consistency rules for content that apply to the entire collection of views and context to improve navigation and visibility of content
  rules that constrain how and in what order relationships can be made to improve the consistency of the set of views that forms the architecture description
  Structurally there are other changes:
  TRAK has 24 viewpoints (vs c 47 views in MODAF)
  the each viewpoint content is defined in terms of tuples (a node - relationship - node element construct i.e. a triple or 1,tuple ) and has allowed and minimum acceptable content and correspondence rules with respect to other views within the architecture description because this is needed to specify a uniquely addressable path in a metamodel (specifying a block metamodel element is not sufficient on its own where there are several relationships involving the element).
  Since ISO/IEC/IEEE 42010:2011 defines architecture in terms of the relationship of a system to its environment the smallest unit of architecture description that may appear in a TRAK architecture view is therefore the Architecture Description Tuple i.e. node - relationship - node.
  The way in which TRAK is managed and released via a set of open source projects is also quite different from other enterprise architecture frameworks. All change requests and feature requests and the sentencing of them are fully visible to anyone, not restricted to those who specify or develop the framework. Releases are under change control and all history is maintained by versioning software (Subversion (SVN)).
caption: Defines the Architecture Description Elements (the triples / tuples that may appear in TRAK architecture views) that describe safety, security and risk.
exif: {"Image PhotometricInterpretation": "2", "Image Orientation": "Horizontal (normal)", "Image XResolution": "144", "Image YResolution": "144", "Image ResolutionUnit": "Pixels/Inch", "Image ExifOffset": "102", "EXIF ColorSpace": "sRGB", "EXIF ExifImageWidth": "1950", "EXIF ExifImageLength": "1422"}