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.
Minimal Modelling Process
TRAK adopts a simple, straight-forwards "bare-bones" approach to creating an architecture description.
TRAK does not specify a detailed modelling process or the minimum views that must be produced for any architecture task. Elements of process or sequence are introduced because:
- there are dependencies between TRAK views
- a MV-02 Architecture Description Design Record architecture view must always be produced for each architecture description. This is needed where an architecture description conforms to ISO/IEC/IEEE 42010.
- being based on ISO/IEC/IEEE 42010 TRAK requires that an architecture description is produced to address the task sponsor’s concerns. These concerns drive the selection of appropriate TRAK Architecture Viewpoints with corresponding concerns.
The minimal process and the requirements for a TRAK-conforming architecture description are designed to enable the resulting TRAK architecture description to conform to ISO/IEC/IEEE 42010.
Subject Triples for the TRAK MV-02 Architecture Description Design Record Provide the Means to Describe the Task
The bare-bones process mandated in conforming to TRAK is therefore:
- Agree architectural task scope with task sponsor and stakeholders and record using the MV-02 Architecture Description Design Record architecture view. The MV-02 architecture view includes the constructs needed to capture the task scope.
- Choose appropriate TRAK architecture views for the task In accordance with ISO 42010 architecture views are selected using the concerns specified in the viewpoints [3]. These will in turn, owing to the concept of Master Architecture Views in TRAK, define the minimum set of architecture views needed for the task.
- Create the architecture description.
- Close-out the architecture description with another MV-02 and, if necessary, the MV-01. This will capture the findings from the modelling and provide enough information for others to understand why the architecture description was done and what resulted. The MV-01 is needed for portability.
The minimal process is only concerned with the minimum set of requirements to ensure that a TRAK architecture description documents its purpose, what was found and what the results or observations are.
TRAK00004. TRAK. Architecture FrameworkWhat TRAK or any other architecture framework won’t specify but which are important considerations are:
- how to plan for the models needed or to be developed for the task
- how to organise the structure of the repository
- how to model
- how to organise views for readability or ease of navigation
It isn't for TRAK to mandate any extensive process. Businesses typically have their own quality management systems and you cannot unilaterally impose a third party process without possible conflicts, gaps or disjointedness etc.
The TRAK architecture viewpoints and specified TRAK architecture view content is designed to provide the means to allow overlap between 'adjacent' architecture views - in terms of the metamodel. Conforming TRAK architecture views that satisfy the minimum allowed view content criteria will permit navigation. A badly organised set of architecture views, however, can still make navigation difficult and unintuitive.
TRAK 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.