View TRAK:TRAK Views
A view in TRAK contains a defined set of TRAK metamodel elements and addresses a particular question or concern, for example, the structure or relationships. It is specified by a viewpoint in accordance with IEEE 1471 / ISO/IEC 42010.
If the architectural model is the collection is the collection of connected stereotypes that represent a particular subject, the views represent windows looking onto the model each taking a slightly different aspect.
Views deliberately overlap slightly so that there is some continuity between views to allow the reader to be able to navigate the views - the overlap in content provides a mechanism to jump to other views.
TRAK views are organised by perspective. Each TRAK view conforms to a TRAK Architecture Viewpoint in addition to global rules applied by TRAK Bye Laws.
Enterprise Perspective
The TRAK Enterprise Perspective has the following 3 views:
Concept Perspective
The TRAK Concept Perspective has the following 5 views:
- CV-01 Concept Need
- CV-03 Concept Item Exchange
- CV-04 Concept Activity to Capability Mapping
- CV-05 Concept Activity
- CV-06 Concept Sequence
TRAK:Procurement Perspective
The TRAK Procurement Perspective has the following 3 views:
TRAK:Solution Perspective
The TRAK Solution Perspective has the following 9 views:
- SV-01 Solution Structure
- SV-02 Solution Resource Interaction
- SV-03 Solution Resource Interaction to Function Mapping
- SV-04 Solution Function
- SV-05 Solution Function to Concept Activity Mapping
- SV-06 Solution Competence
- SV-07 Solution Sequence
- SV-11 Solution Event Causes
- SV-13 Solution Risk
Management Perspective
The TRAK Management Perspective has the following 4 views:
- MV-01 Architecture Dictionary
- MV-02 Architecture Design Record
- MV-03 Requirements & Standards
- MV-04 Assurance
The numbering of the TRAK views has no significance with respect to the order in which views are developed.
Other Frameworks
Category:Framework -> Collection
Category:Framework -> View