Download Latest Version TRAK_ArchitectureViewpoints.pdf (2.4 MB)
Email in envelope

Get an email when there's a new version of TRAK Viewpoints

Home
Name Modified Size InfoDownloads / Week
TRAK_Viewpoints_vs_UPDM_Diagrams 2025-02-27
0
TRAK Viewpoints Working Groups 2025-02-27
0
readme.md 2025-05-25 13.9 kB
0
revisions.md 2025-04-30 33.5 kB
0
TRAK_ArchitectureViewpoints.pdf 2025-04-30 2.4 MB
1 1 weekly downloads
license.txt 2025-04-30 2.6 kB
0
Totals: 6 Items   2.5 MB 1

Contents

Defining TRAK Documents

Overall Structure (trakviewpoints) - TRAK is Defined by 3 Agnostic Specification Documents

TRAK is defined by 3 documents.

Other Documents

TRAK Architecture Viewpoints

In accordance with ISO/IEC/IEEE 42010 - the international standard for architecture description - an architecture viewpoint is a specification that governs the interpretation and content of an architecture view. Each architecture view has its own governing architecture viewpoint. In TRAK an architecture viewpoint has a 'Vp' in its identifier e.g. 'SVp-01' as opposed to the governed ('SV-01') architecture view.

Metamodel Triples Provide the Basis for TRAK Architecture View Content Rules - They Address the Architecture Viewpoint Framed Concerns

Every TRAK architecture viewpoint specifies both the allowed architecture view content and the minimum allowed content in an atomic and unambiguous way using triples from the TRAK metamodel based on a non-TRAK set of architecture viewpoints defined in ‘Architecture Description Viewpoints. Metamodel Description, Implementation and Model Changes’, Eclectica Systems Ltd, 3736126–001. This allows TRAK architecture view and TRAK architecture description content to be verified. TRAK is the only architecture framework that has a verifiable set of architecture view content requirements.

The 24 TRAK architecture viewpoints are:-

These are listed with the stakeholder concerns that each TRAK architecture viewpoint addresses.

TRAK on the Internet

See also:

This Release

30th April 2025

See [r79]:

  • Added Glossary and Abbreviations.
  • Added new context 'Figure 1-2: The trakviewpoints Sourceforge Project is One of Three Defining TRAK'.
  • Split implementation text into 2 Implementation of TRAK

  • Added Table 3.2 Well-Formedness Criteria – AD Elements

  • Turtle (RDF) examples added: EVp-01 Enterprise Goal, EVp-02 Capability Hierarchy, EVp-03 Capability Phasing, CVp-01 Concept Need, CVp-03 Concept Item Exchange, CVp-04 Concept Activity to Enterprise Capability Mapping, CVp-05 Concept Activity, CVp-06 Concept Sequence, PrVp-01 Procurement Structure, PrVp-02 Procurement Timeline, PrVp-03 Procurement Responsibility, SVp-01 Solution Structure, SVp-02 Solution Resource Interaction, SVp-03 Solution Resource Interaction to Function Mapping, SVp-04 Solution Function, SVp-05 Solution Function to Concept Activity Mapping, SVp-06 Solution Competence, SVp-07 Solution Sequence, SVp-11 Solution Event Causes, SVp-13 Solution Risk, MVp-02 Architecture Description Design Record, MVp-03 Requirements & Standards, MVp-04 Assurance.

  • Table legends added. EVp-03 Capability Phasing, CVp-01 Concept Need, CVp-03 Concept Item Exchange, CVp-04 Concept Activity to Enterprise Capability Mapping, SVp-02 Solution Resource Interaction, SVp-03 Solution Resource Interaction to Function Mapping, SVp-05 Solution Function to Concept Activity Mapping, MVp-01 Architecture Description Dictionary

  • SVp-03 Solution Resource Interaction to Function Mapping. Optional Tuples. Added 'System is configured with Resource' and 'Software hosted on Physical'

  • SVp-06 Solution Competence. Added 'Job requires Competence' and 'Competence has part Competence'. Removed tabular presentation.

  • SVp-11 Solution Event Causes. Subject Tuples. Added N-ary tuples 'Event caused by ('Event AND / OR / NOT Event')' to describe causal event combinational logic. Added note concerning description of event tree e.g. fault tree. Added Fault Tree fragment example

  • MVp-03 Requirements & Standards. Subject Tuples. Added 'Organisation is party to Contract'. Optional Tuples. Conformance Claims – N-ary 'Claim about ('Architecture Description Element satisfies Contract / Requirement / Standard')' and Claim about ('Contract / Requirement / Standard governs Architecture Description Element')' triples added.

  • MVp-04 Assurance. Subject Tuples. Identification of Claim / Forming Argument. 'Claim about ('Architecture Description Element satisfies Contract / Requirement / Standard')' and Claim about ('Contract / Requirement / Standard governs Architecture Description Element')' triples added.

The changes are outlined at https://trakviewpoints.svn.sourceforge.net/viewvc/trakviewpoints/trunk/?view=log.

Get Notified of Files Released on this Site

If you'd like to be notified of file releases rather than having to remember to visit the site and check you can do so using RSS. Simply add (subscribe to) the following URL in your RSS reader or MS Outlook / Apple Mail etc:

RSS icon https://sourceforge.net/api/file/index/project-id/304405/mtime/desc/limit/20/rss

Structure on Sourceforge

Overall Structure (trakmetamodel) - TRAK is Defined by 3 Specifications Across 3 Sourceforge Projects

The TRAK architecture framework is split across 3 Sourceforge project sites:-

This Site - trakviewpoints

license.txt - the GNU Free Documentation License under which the TRAK Viewpoints document is released.

Sub-folders under Files:

Source: readme.md, updated 2025-05-25