TRAK Architecture FrameworkThis page reproduces parts of the overall TRAK0004 specification for information only. It may not therefore reflect the master source content at https://sourceforge.net/projects/trak.
TRAK
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/IEEE 42010 terms each is a ‘system of interest’ and has stakeholders who have concerns that need to be addressed through the resulting architecture description.TRAK00004. TRAK. Architecture Framework
TRAK provides a way of describing systems and their place in the world through architectural descriptions. The triples used to make the TRAK architecture views (the "language" of TRAK) is defined by the TRAK Metamodel. The TRAK architecture views are each defined by a TRAK architecture viewpoint where an architecture viewpoint is defined as work product establishing the conventions for the construction, interpretation and use of architecture views to frame specific system concerns
ISO/IEC/IEEE 42010:2011
TRAK adopts the ISO/IEC/IEEE 42010 approach where
- the architecture description task sets out to answer concerns raised by the task stakeholder(s)
- the task produces an architecture description consisting of multiple architecture views describing the same system of interest
- each TRAK architecture viewpoint specifies an individual TRAK architecture view in terms of:
- the questions or concerns the architecture view 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
TRAK Architecture Framework Document
The TRAK Enterprise Architecture Framework document is a specification.
It contains:
- important ideas for TRAK - general statements about TRAK - what it is, what it isn't and how it is organised
- standards affecting TRAK
- 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
Governance of TRAK
Release of the TRAK Viewpoints are under the control of the TRAK Steering Group,
ISO/IEC/IEEE 42010
TRAK was designed from the outset to be compliant with international standard ISO/IEC/IEEE 42010 Systems & Software - Architecture Description. Since ISO/IEC/IEEE 42010 is a significant topic in its own right more information on TRAK in the context of the standard is provided separately.
TRAK follows the ISO/IEC/IEEE 42010 concern-led approach based on a set architecture viewpoints that specify the use, scope and allowed architecture view content.
TRAK has produced a compliance assessment against ISO/IEC/IEEE 42010 which includes a compliance matrix with evidence to support the claims of compliance.
Where Does this Fit In?
TRAK00004. TRAK. Architecture Framework
Overall Structure (trak) - TRAK is Defined Across 3 Sourceforge Projects
The TRAK Architecture Framework document (TRAK00004. TRAK. Architecture Framework’, TRAK00004, https://sourceforge.net/projects/trak/files/TRAK_Overall.pdf) forms part of the logical definition of TRAK.
TRAK00004. TRAK. Architecture Framework
The TRAK Specification Documents
The TRAK Architecture Framework document invokes the other parts of the definition:
Implementations of TRAK
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 known implementations of TRAK are listed separately.
Where Do I Get It?
The TRAK document is available here ...