TRAK Architecture ViewpointsTRAK Viewpoints
Health Warning
This web site is informative only. It is not the definitive or master source for any TRAK viewpoint. The definitive / master source is:- TRAK00001. TRAK. Enterprise Architecture Framework. Viewpoints
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.
It is important to note that TRAK views are defined as wholly triples - node - relationship - node e.g. 'Claim about System' or a contiguous set of triples e.g. 'Organisation plays Role extends to Software'. These form sentences or assertions which can be tested for consistency, path closure. They are readable by a non technical audience. It is the TRAK metamodel that provides these triples for the various TRAK Viewpoint definitions.
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
An overview of the viewpoints and some examples of TRAK architecture views are provided.
Governance of TRAK
Release of the TRAK Viewpoints are under the control of the TRAK Steering Group.
TRAK Viewpoints Specification
The TRAK00001. TRAK. Enterprise Architecture Framework. Viewpoints specification defines architecture viewpoints - specifications against each of which a view is prepared and interpreted.
It contains:
- identification of a TRAK architecture viewpoint
- how to select the appropriate TRAK architecture viewpoint(s)
- the structure of a TRAK architecture viewpoint including:
- stakeholder concerns framed
- allowed architecture view content
- minimum acceptable architecture view content
- consistency rules between architecture views and across an architecture description or repository
- examples
- TRAK architecture viewpoint definitions
- Enterprise
- Concept
- Procurement
- Solution
- Management
- originating or master source architecture views for metamodel node elements and triples
- minimum TRAK architecture view sets
Where Does this Fit In?
TRAK00001. TRAK. Viewpoints
Overall Structure (trakviewpoints) - TRAK is Defined by 3 Specifications Across 3 Sourceforge Projects
The TRAK Viewpoints specification (TRAK00001. TRAK. Architecture Framework) forms part of the logical definition of TRAK together with:
- TRAK00004. TRAK. Enterprise Architecture Framework - an overall set of requirements (e.g. colour, conformance with TRAK, Bye Laws etc)
- TRAK00002. TRAK. Enterprise Architecture Framework. Metamodel - the allowed elements and relationships and the triples that form the basis of the TRAK architecture viewpoints
The definition of TRAK is released through Sourceforge as open source.
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 TRAK00001 TRAK. Enterprise Architecture Framework. Viewpoints specification is available here ...