TRAK Architecture Viewpoints & Views

TRAK Architecture Viewpoints

A TRAK architecture viewpoint is a specification against which a TRAK architecture view is prepared and interpreted. This is explained in more detail separately.

TRAK viewpoint identifiers always have 'Vp' whereas a TRAK View identifier just has a 'V' e.g. SVp-01 identifies the Solution Structure Viewpoint whereas a SV-01 refers to a Solution Structure View. Links provide more information on the views and examples.

In accordance with ISO/IEC/IEEE 42010 each TRAK Viewpoint addresses a set of concerns. These are the typical questions or concerns that a stakeholder might have i.e. if you were concerned with understanding the structure of the system of interest or the membership of an organisation you would select the SVp-01 Solution Structure Viewpoint.

Stakeholder Concerns

A summary of all of the typical concerns addressed by each TRAK Viewpoint are listed separately.

Architecture Perspectives

The TRAK architecture viewpoints are grouped into 5 architecture perspectives:-

Enterprise Perspective
Concept Perspective
Procurement Perspective
Solution Perspective
Management Perspective

The architecture perspectives, the colours and rules applying to the perspectives are defined within the overall TRAK specification:

‘TRAK00004. TRAK. Architecture Framework’, https://sourceforge.net/projects/trak/files/TRAK_Overall.pdf.

Enterprise Perspective

The Enterprise perspective describes the enterprise in terms of its goals and the enduring capabilities that are required to support the goals.These are high level business needs that everything else contributes to and form part of the long term strategic objectives that need to be managed.

Concept Perspective

The Concept Perspective describes the solution-free (logical) view of what is needed in response to the capabilities required by the enterprise in the Enterprise Perspective. It describes the logical connection of nodes, for example a service control centre, to other nodes with no recognition of how this might be realised either by organisation or technology. It also implies no particular part of a life cycle - it covers everything from concept to disposal ('lust to dust'!) - time is only introduced deliberately in either the Enterprise and / or Procurement perspectives. Any normative documents or standards applied to the concept and described in the Management Perspective are likely to be technology-free - they won't describe 'the how'.

Procurement Perspective

The Procurement Perspective provides a top level view of the procurement of a solution to satisfy the enterprise capability needs outlined in the Enterprise Perspective and developed in the concept perspective. It provides a way of showing how projects deliver the solutions described in the Solution Perspective to provide capability. It provides a way of showing time dependency between projects owing to dependencies on systems being introduced or removed and is an essential for investigating capability gaps. It also provides a way of showing how responsibility boundaries change over time.

Solution Perspective

The Solution Perspective describes the solution - whether proposed or realised. It covers the parts of 'systems' whether human or machine, their exchanges and protocols. It describes how organisations and equipments are organised and governed.The Solution Per- spective describes how the logical requirements outlined in the Concept Perspective are realised and shows how the solution(s) realise the capabilities needed by the enterprise and described in the Enterprise Perspective.

Management Perspective

The Management Perspective describes the architectural task and those relationships that are common across other perspectives. It provides ways of defining the scope and findings of the architectural task - structuring the approach and modelling. The Management Perspective provides ways of describing the requirements and normative standards that apply and the assurance against these based on claims, arguments and evidence.

It provides supporting information to aid the portability and understanding of the architecture description produced as a result of the task.

As the Management Perspective underpins all other perspectives all roles are beneficiaries including the lay reader (or external third party) to the architecture description.

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.