TRAK Enterprise Architecture
=============================
The TRAK Enterprise Architecture Framework document (TRAK_Overall.pdf) is one of 3 that collectively define the TRAK Enterprise Architecture framework. The others are:
- TRAK Viewpoints at https://sf.net/p/trakviewpoints (specifications for views)
- TRAK Metamodel at https://sf.net/p/trakmetamodel (the objects and relationships)
This document provides the top level specification for TRAK, its relationship with ISO/IEC 42010, defines conformance with TRAK and provides overall rules. It invokes the TRAK Viewpoints and TRAK Metamodel documents.
TRAK-on-a-page.pdf provides a vert short guide to using TRAK.
TRAK on the Internet
====================
See also:
- TRAK Community - https://trak-community.org
- TRAK Group on LinkedIn - https://www.linkedin.com/groups/TRAK-Enterprise-Architecture-Framework-3256940
- TRAK Group on Facebook - https://www.facebook.com/home.php?sk=group_172938462752985
- Twitter - https://twitter.com/trak_af
- Mastodon - https://fosstodon.org/@trak_af
- Implementations of TRAK e.g. Sparx Systems Enterprise Architect, Salamander MooD, Microsoft Visio, OmniGraffle (Mac, iPad) etc. https://trak.sourceforge.net/implementations.html
This Release
============
TRK00004 TRAK. Enterprise Architecture Framework
-------------------------------------------------
28th February 2022
- Updated URLs from http:// to https://
- ‘stereotype’ replaced with ‘metamodel element’ or ‘element type’.
- Structure of TRAK Number of viewpoints changed to 24.
- Choice of Architecture Description Language (ADL). Minor tweak to scenario of choosing an ADL.
- 10.1 Introduction. Added consistency of meaning, consistency of values. Added TRAK-Designer and TRAK-User roles to clarify the stakeholders to which the requirements apply.
- Added stakeholder / role to headings: 10.2 Metamodel [TRAK-Designer], 10.3 Viewpoint Definition [TRAK-Designer] and 10.4 View and Architecture Definition [TRAK-User].
- 10.3 Viewpoint Definition [TRAK-Designer]. BLV-8. Expanded rationale for viewpoint differentiation.
- 10.4. Changed heading title ‘View and Architecture Definition’ to ‘Architecture View and Architecture Description’.
- 11 TRAK Minimal Modelling Process. Added rationale to reasons why there is a minimal process.
- References. Added URLs for DODAF 1.5[Ref. 2] . Added reference to TRAK conformance assessment against ISO/IEC/IEEE 42010:2011 [Ref. 16] [Ref. 15] [Ref. 17] . Added link to trak ‘code’ repository. Added [Ref. 20], [Ref. 21].
Folder Structure on Sourceforge
===============================
Implementation
______________
- documents concerned with implementation of TRAK in modelling or drawing tools. Includes specification of names to be used for objects, attributes, enumerated lists, standards that apply e.g. RFCs etc.
Suitability of Architecture Description Language
- documents mapping notation languages to TRAK
ISO42010
________
- documents relating to the compliance of TRAK with the international standard for architecture description ISO/IEC/IEEE 42010:2011.
Note that there is a set of web pages (an architecture description) that presents the claims, supporting arguments and supporting evidence (assurance - Claims, Arguments, Evidence - CAE) in respect of:-
1) the conformance of TRAK as an architecture framework against section 6 of the standard
2) the conformance of a TRAK-conforming architecture description against section 5 of the standard
This is located at:- https://trak.sourceforge.io/index.html#ISO_42010
Miscellaneous
_____________
Steering Group Documents
- documents created or used by the TRAK Steering Group responsible for directing and co-ordinating the definition of TRAK
INCOSE
- documents relating to the International Council on Systems Engineering. Currently comments from the UK Architecture Working Group.
