TRAK Architecture ViewpointsQuestions/ Concerns Addressed by TRAK Architecture Viewpoints
In accordance with ISO/IEC/IEEE 42010 each TRAK architecture viewpoint is a specification against which a TRAK architecture view is prepared and interpreted. Each TRAK architecture viewpoint frames one or more concerns. Each of these concerns is addressed by the allowed core content ('subject tuples') presented by a conforming architecture view.
The TRAK architecture viewpoints are defined in TRAK00001. TRAK. Architecture Framework. Viewpoints specification. The current release is dated 30 April 2025.
A list of the 24 TRAK architecture viewpoints is provided below together with the concerns addressed by each.
| Perspective | Viewpoint | Title | Questions / Concerns |
| Enterprise | EVp-01 | Enterprise Goal | What is the Enterprise and what goals does it set out to achieve? |
| EVp-02 | Capability Hierarchy | How is capability measured? What are the enduring capabilities the enterprise requires? |
|
| EVp-03 | Capability Phasing | Are there any capability gaps? Is the capability realised by any solutions? When is capability required? |
|
| Concept | CVp-01 | Concept Need | What are the concept needs? |
| CVp-03 | Concept Item Exchange | Have the items exchanged by concept nodes been identified? What is required to satisfy the concept needs? |
|
| CVp-04 | Concept Activity to Capability Mapping | How / are concept activities sufficient to deliver capability? |
|
| CVp-05 | Concept Activity | What does each node need to do? |
|
| CVp-06 | Concept Sequence | How are concept activities ordered? Is the concept activity order important? |
|
| Procurement | PrVp-01 | Procurement Structure | How is the project governed? What is the project structure? |
| PrVp-02 | Procurement Timeline | How does their delivery time affect us? What other projects is this dependent on? |
|
| PrVp-03 | Procurement Responsibility | Are their boundaries clear? What responsibilities do organisations, jobs, software or systems have in relation to a project or time? |
|
| Solution | SVp-01 | Solution Structure | How does responsibility (scope/jurisdiction) apply to the solution components? How does the solution realise the concept or enterprise? Is the solution structured sensibly? What does the solution consist of? What is the organisation structure / membership? |
| SVp-02 | Solution Resource Interaction | Do the solution interactions realise any conceptual exchange(s)? Does the solution realise any concept? Have the interactions / interfaces / exchanges been characterised? How are resources connected together? How are the organisations, jobs and roles connected? |
|
| SVp-03 | Solution Resource Interaction to Function Mapping | Are there interactions / interfaces that cannot be justified by functional need? Do we have functions that cannot be realised because there isn’t an interchange? |
|
| SVp-04 | Solution Function | Have all the solution functions been identified? What does each part do? |
|
| SVp-05 | Solution Function to Concept Activity Mapping | Do the solution functions meet all of the concept activities? Is there unwanted solution functionality? |
|
| SVp-06 | Solution Competence | Does the organisation or job through its role have the necessary competence to conduct the function? Is the competence consistent with the solution? |
|
| SVp-07 | Solution Sequence | In what order do things need to happen? |
|
| SVp-11 | Solution Event Causes | How dependable is the system? How robust is the system to unwanted events? What causes events? |
|
| SVp-13 | Solution Risk | How are the resulting risks mitigated or controlled? How does the solution design mitigate or address the vulnerabilities, threats and risks? What are the risks posed to the subject system, or to a third party by any other system? What are the vulnerabilities of the system of interest? What threats is the system of interest exposed to? |
|
| Management | MVp-01 | Architecture Description Dictionary | Can the architecture description be understood in the way it was intended to be? Is the architecture description portable? |
| MVp-02 | Architecture Description Design Record | Do we understand the scope of the architecture task? What are the issues and findings that resulted? |
|
| MVp-03 | Requirements and Standards | What other constraints / requirements through normative documents / standards apply (or will apply) to the enterprise, concept, procurement, solution or architecture task? What other constraints/requirements through normative documents/standards apply (or will apply) to the system, project, enterprise? |
|
| MVp-04 | Assurance | Is the claim supported by evidence? What are the claims made? What is the basis of the claim? |
Return to the summary of the TRAK views.
The TRAK architecture viewpoints are 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.