Important: This Wiki is informative and not a definitive / master source for TRAK. TRAK is specified by 3 documents:-
The architecture viewpoints (specifications for architecture views iaw ISO 42010) for TRAK. TRAK is a general systems-thinkers'/system engineering enterprise architecture framework. It is simple, user-friendly, pragmatic and not limited to IT.
Defines a total of 24 viewpoints.
The ones needed for any task are selected by taking the task sponsor's concerns and matching them to the typical concerns that each TRAK viewpoint addresses.
Each viewpoint defines the triples (node - relationship - node) that is allowed. For example:-
- SVp-01Solution Structure Viewpoint
- System is configured with System / Software / Physical / Role / Job / Organisation
- Organisation governs Organisation
- Job governs Job
- Organisation is member of Organisation
- Organisation plays Role extends to System / Software / Physical / Role / Job / Organisation e.g. a company might play the role of System Design Authority for a particular system
- SVp-13 Solution Risk Viewpoint
- Threat (syn Hazard) exploits Vulnerability
- Software poses Threat
- Vulnerability results in Risk
- MVp-03 Requirements and Standards Viewpoint) - used to describe contracts, normative documents and atomic requirements (and apply them)
- Contract applies Standard
- Contract / Standard / Requirement governs System
- System satisfies Requirement
- Requirement derived from Requirement
- MVp-04 Assurance Viewpoint - typical Claim - Argument - Evidence CAE structure which can be used for design verification against requirements including:
- Organisation / Role makes Claim
- Claim about Requirement
- Argument supports / opposes Claim
- Evidence supports / opposes Argument
- Evidence proves / disproves Claim
Since the view content is defined using triples you don't have to understand software notation to understand it.
The minimal process is defined in the overall TRAK specification. The allowed elements and relationships are taken from the TRAK metamodel.
TRAK Viewpoints Are Selected According to Stakeholder Concerns
Each TRAK view is specified by a Viewpoint in accordance with ISO 42010 using simple triples (node - relationship node statement)
Well-Formedness Rules Specify the Minimum Acceptable Content to help consistency
Each Viewpoint Specifies Acceptable Presentation Methods
Minimum Allowed View Sets Provide Visibility / Navigation
Each Metamodel Element Has an Associated View(point) Master where the element is first defined / introduced
Project Admins: