TRAK Viewpoints Wiki

Specifications for TRAK architecture views

Brought to you by: wikitect

TRAK Viewpoint Selection

Important: This Wiki is informative and not a definitive / master source for TRAK. TRAK is specified by 3 documents:-

This page reproduces the https://trakviewpoints.sourceforge.io/viewpoint_concerns.html web page.

TRAK defines a total of 24 viewpoints. Each viewpoint is a specification for the content and interpretation of a TRAK architecture view(1).

Note - this use of the term 'viewpoint' complies with the international standard for architecture description, ISO/IEC/IEEE 42010:2011(2). Other architecture frameworks such as MODAF and NAF use 'viewpoint' to mean a collection(3), not a specification.

Viewpoints are grouped into perspectives.

TRAK Viewpoints - Concerns Addressed
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	What are the enduring capabilities the enterprise requires and how is capability measured?
	EVp-03	Capability Phasing	How is capability delivered over time? Are there any gaps?
Concept	CVp-01	Concept Need	Have the concept needs been identified?
	CVp-02	Concept	Has the concept purpose been identified? How is it seen as being used?
	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 concept node need to do?
	CVp-06	Concept Sequence	How are concept activities ordered? Is it important?
Procurement	PrVp-01	Procurement Structure	What is the project structure? How is it governed?
	PrVp-02	Procurement Timeline	What other projects is this dependent on? How does their delivery time affect us?
	PrVp-03	Procurement Responsibility	What responsibilities do organisations or jobs have in relation to a project or time? Are their boundaries clear?
Solution	SVp-01	Solution Structure	What does the solution consist of? Is it structured sensibly? What is the organisation structure / membership? How does responsibility (scope/jurisdiction) apply to the solution components?
	SVp-02	Solution Resource Interaction	How are resources connected together? How are the organisations, jobs & roles connected? Have the interactions/ interfaces/exchanges been characterised?
	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 solution functions been identified? What does each part do?
	SVp-05	Solution Function to Operational 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 robust is the system to unwanted events? How dependable is the system? What causes events?
	SVp-13	Solution Risk	What threats is the system exposed to? How are the threats mitigated or controlled? What are the vulnerabilities of the system? What are the risks posed to the system or a third party? How does the solution design address vulnerabilities, threats and risks?
Management	MVp-01	Architecture Description Dictionary	Is the architecture description portable? Can it be understood in the way it was intended to be?
	MVp-02	Architecture Description Design Record	Do we understand the scope of the architectural task? What are the issues and findings that resulted?
	MVp-03	Stardards & Requirements	Have all the constraints been identified? What constraints/ requirements through normative documents/standards apply (or will apply) to the system, project, enterprise?
	MVp-04	Assurance	What are the claims made? What is the basis of the claim? Is the claim supported by evidence?

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.

The minimal modelling process in TRAK consists of 4 steps and is defined in the overall TRAK Specification(4).

TRAK views are prepared using elements (node - relationship - node defining. a 'triple' or 'tuple' from the TRAK Metamodel Specification(5).

References

(1): http://www.iso-architecture.org/42010/cm/ ISO/IEC/IEEE 42010 Conceptual Model
(2): https://www.iso.org/standard/50508.html ISO/IEC/IEEE 42010:2011 Systems and Software Engineering - Architecture Description
(3): https://trak-community.org/index.php/wiki/Architecture_Framework_Comparison trak-community.org - Wiki - Comparison of Architecture Frameworks
(4): https://sf.net/p/trak TRAK000004 TRAK. Enterprise Architecture Framework
(5): https://sf.net/p/trakmetamodel TRAK000002 TRAK. Enterprise Architecture Framework. Metamodel.