MVp-03 Requirements and Standards

This page reproduces part of the MVp-03 Requirements and Standards architecture viewpoint definition from the specification - TRAK00001. TRAK. Architecture Framework. Viewpoints. The page content is therefore subject to the same GNU Free Documentation License terms and conditions - see https://www.gnu.org/licenses/fdl-1.3.html

Most of the content is produced from a model of TRAK produced using a different set of architecture viewpoints!

Version

The TRAK MVp-03 Requirements and Standards architecture viewpoint is one of 24 architecture viewpoints defined in TRAK00001. TRAK. Architecture Framework. Viewpoints - current release is dated 30 April 2025.

MVp-03 Requirements and Standards Architecture Viewpoint Configuration
Perspective	Viewpoint	View ID	Version	Modified
Management	MVp-03	MV-03	13	2025-04-30

Summary

The TRAK MVp-03 Requirements and Standards architecture viewpoint defines the requirements for the TRAK MV-03 Requirements and Standards architecture view. This involves allowed content and minimum acceptable content ('well-formedness' criteria). The TRAK00001. TRAK. Architecture Framework. Viewpoints specification also defines consistency rules that apply to a set of architecture views (an Architecture Description).

The TRAK MVp-03 Requirements and Standards architecture viewpoint content is summarised under the following sections:

stakeholder concerns
description
allowed content
- Subject Statements (Triples)
- Optional Statements (Triples)
well-formedness criteria
presentation methods
examples
views needed to construct
consistency rules
comments

The TRAK Architecture Viewpoints specification provides are complete definition not only of the MVp-03 Requirements and Standards architecture viewpoint but considerations for the architecture description formed from a set of architecture views.

Something needs fixing?

Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns.

Stakeholder Concerns

Stakeholder Concerns Addressed by the MVp-03 Requirements and Standards Architecture Viewpoint

The TRAK MVp-03 Requirements and Standards architecture viewpoint addresses the following concerns:

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?

Concerns addressed by all the TRAK architecture viewpoints.

Description

Describes the constraints that apply to an architecture element through requirements and standards or how standards depend on one another.

Allowed Content

TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Standard traces to Contract' that form short statements about the thing(s) being described.

Example of a 'Standard traces to Contract' subject triple for the MV-03 Requirements and Standards Architecture View

'Standard traces to Contract' is a Statement or Assertion in a MV-03 Architecture View

The rationale and theory for the allowed content of an architecture view is explained separately.

The allowed MV-03 architecture view content is split into:-

subject statement (triples)
optional statements (triples)

Subject Statements (Triples)

These are statements (triples) that describe the subject of the MV-03 Requirements and Standards architecture view. Specifically these statements address the concerns for this MVp-03 Requirements and Standards architecture viewpoint. These form the basis for the well-formedness section of the MVp-03 Requirements and Standards architecture viewpoint.

The MV-03 Requirements and Standards architecture view includes statements about applicable requirements, compliance and requirement sources that apply to the architecture being described. These involve every metamodel element and may be added as content on any other architecture view. This is why the MV-03 Requirements and Standards architecture view is part of the Management Perspective.

There are 397 possible subject statements in total which include 42 metamodel elements ( Architecture Description , Architecture Task , Architecture View , Argument , Capability , Claim , Competence , Concept Activity , Concern , Contract , Document , Enterprise , Enterprise Goal , Event , Evidence , Function , Interaction Element , Item , Item Exchange , Job , Metric , Milestone , Mitigation , Need , Node , Organisation , Physical , Port , Port Connection , Project , Project Activity , Protocol , Requirement , Resource Interaction , Risk , Role , Software , Standard , System , Threat , Vulnerability and Zone ).

The subject statements are split into 6 groups:

Applicable Requirements
Contract Requirement Assessment
Requirement Compliance
Requirement Development
Requirement Structure
Traceability or Reference

Return to the top of the Requirements and Standards page.

Applicable Requirements

129 possible subject statements:

Contract governs Architecture Description
Contract governs Architecture Task
Contract governs Architecture View
Contract governs Argument
Contract governs Capability
Contract governs Claim
Contract governs Competence
Contract governs Concept Activity
Contract governs Concern
Contract governs Contract
Contract governs Document
Contract governs Enterprise
Contract governs Enterprise Goal
Contract governs Event
Contract governs Evidence
Contract governs Function
Contract governs Interaction Element
Contract governs Item
Contract governs Item Exchange
Contract governs Job
Contract governs Metric
Contract governs Milestone
Contract governs Mitigation
Contract governs Need
Contract governs Node
Contract governs Organisation
Contract governs Physical
Contract governs Port
Contract governs Port Connection
Contract governs Project
Contract governs Project Activity
Contract governs Protocol
Contract governs Requirement
Contract governs Resource Interaction
Contract governs Risk
Contract governs Role
Contract governs Software
Contract governs Standard
Contract governs System
Contract governs Threat
Contract governs Vulnerability
Contract governs Zone
Contract issued by Organisation
Organisation is party to Contract
Requirement governs Architecture Description
Requirement governs Architecture Task
Requirement governs Architecture View
Requirement governs Argument
Requirement governs Capability
Requirement governs Claim
Requirement governs Competence
Requirement governs Concept Activity
Requirement governs Concern
Requirement governs Contract
Requirement governs Document
Requirement governs Enterprise
Requirement governs Enterprise Goal
Requirement governs Event
Requirement governs Evidence
Requirement governs Function
Requirement governs Interaction Element
Requirement governs Item
Requirement governs Item Exchange
Requirement governs Job
Requirement governs Metric
Requirement governs Milestone
Requirement governs Mitigation
Requirement governs Need
Requirement governs Node
Requirement governs Organisation
Requirement governs Physical
Requirement governs Port
Requirement governs Port Connection
Requirement governs Project
Requirement governs Project Activity
Requirement governs Protocol
Requirement governs Requirement
Requirement governs Resource Interaction
Requirement governs Risk
Requirement governs Role
Requirement governs Software
Requirement governs Standard
Requirement governs System
Requirement governs Threat
Requirement governs Vulnerability
Requirement governs Zone
Standard governs Architecture Description
Standard governs Architecture Task
Standard governs Architecture View
Standard governs Argument
Standard governs Capability
Standard governs Claim
Standard governs Competence
Standard governs Concept Activity
Standard governs Concern
Standard governs Contract
Standard governs Document
Standard governs Enterprise
Standard governs Enterprise Goal
Standard governs Event
Standard governs Evidence
Standard governs Function
Standard governs Interaction Element
Standard governs Item
Standard governs Item Exchange
Standard governs Job
Standard governs Metric
Standard governs Milestone
Standard governs Mitigation
Standard governs Need
Standard governs Node
Standard governs Organisation
Standard governs Physical
Standard governs Port
Standard governs Port Connection
Standard governs Project
Standard governs Project Activity
Standard governs Protocol
Standard governs Requirement
Standard governs Resource Interaction
Standard governs Risk
Standard governs Role
Standard governs Software
Standard governs Standard
Standard governs System
Standard governs Threat
Standard governs Vulnerability
Standard governs Zone
Standard issued by Organisation

Return to the top of the MV-03 subject statements (triples).

Contract Requirement Assessment

10 possible subject statements:

Contract applies Standard
Contract depends on Contract
Contract issued by Organisation
Contract supersedes Contract
Standard applies Standard
Standard depends on Standard
Standard enacts Standard
Standard is equivalent to Standard
Standard issued by Organisation
Standard supersedes Standard

Return to the top of the MV-03 subject statements (triples).

Requirement Compliance

126 possible subject statements:

Architecture Description satisfies Contract
Architecture Description satisfies Requirement
Architecture Description satisfies Standard
Architecture Task satisfies Contract
Architecture Task satisfies Requirement
Architecture Task satisfies Standard
Architecture View satisfies Contract
Architecture View satisfies Requirement
Architecture View satisfies Standard
Argument satisfies Contract
Argument satisfies Requirement
Argument satisfies Standard
Capability satisfies Contract
Capability satisfies Requirement
Capability satisfies Standard
Claim satisfies Contract
Claim satisfies Requirement
Claim satisfies Standard
Competence satisfies Contract
Competence satisfies Requirement
Competence satisfies Standard
Concept Activity satisfies Contract
Concept Activity satisfies Requirement
Concept Activity satisfies Standard
Concern satisfies Contract
Concern satisfies Requirement
Concern satisfies Standard
Contract satisfies Contract
Contract satisfies Requirement
Contract satisfies Standard
Document satisfies Contract
Document satisfies Requirement
Document satisfies Standard
Enterprise Goal satisfies Contract
Enterprise Goal satisfies Requirement
Enterprise Goal satisfies Standard
Enterprise satisfies Contract
Enterprise satisfies Requirement
Enterprise satisfies Standard
Event satisfies Contract
Event satisfies Requirement
Event satisfies Standard
Evidence satisfies Contract
Evidence satisfies Requirement
Evidence satisfies Standard
Function satisfies Contract
Function satisfies Requirement
Function satisfies Standard
Interaction Element satisfies Contract
Interaction Element satisfies Requirement
Interaction Element satisfies Standard
Item Exchange satisfies Contract
Item Exchange satisfies Requirement
Item Exchange satisfies Standard
Item satisfies Contract
Item satisfies Requirement
Item satisfies Standard
Job satisfies Contract
Job satisfies Requirement
Job satisfies Standard
Metric satisfies Contract
Metric satisfies Requirement
Metric satisfies Standard
Milestone satisfies Contract
Milestone satisfies Requirement
Milestone satisfies Standard
Mitigation satisfies Contract
Mitigation satisfies Requirement
Mitigation satisfies Standard
Need satisfies Contract
Need satisfies Requirement
Need satisfies Standard
Node satisfies Contract
Node satisfies Requirement
Node satisfies Standard
Organisation satisfies Contract
Organisation satisfies Requirement
Organisation satisfies Standard
Physical satisfies Contract
Physical satisfies Requirement
Physical satisfies Standard
Port Connection satisfies Contract
Port Connection satisfies Requirement
Port Connection satisfies Standard
Port satisfies Contract
Port satisfies Requirement
Port satisfies Standard
Project Activity satisfies Contract
Project Activity satisfies Requirement
Project Activity satisfies Standard
Project satisfies Contract
Project satisfies Requirement
Project satisfies Standard
Protocol satisfies Contract
Protocol satisfies Requirement
Protocol satisfies Standard
Requirement satisfies Contract
Requirement satisfies Requirement
Requirement satisfies Standard
Resource Interaction satisfies Contract
Resource Interaction satisfies Requirement
Resource Interaction satisfies Standard
Risk satisfies Contract
Risk satisfies Requirement
Risk satisfies Standard
Role satisfies Contract
Role satisfies Requirement
Role satisfies Standard
Software satisfies Contract
Software satisfies Requirement
Software satisfies Standard
Standard satisfies Contract
Standard satisfies Requirement
Standard satisfies Standard
System satisfies Contract
System satisfies Requirement
System satisfies Standard
Threat satisfies Contract
Threat satisfies Requirement
Threat satisfies Standard
Vulnerability satisfies Contract
Vulnerability satisfies Requirement
Vulnerability satisfies Standard
Zone satisfies Contract
Zone satisfies Requirement
Zone satisfies Standard

Return to the top of the MV-03 subject statements (triples).

Requirement Development

1 possible subject statements:

Requirement derived from Requirement

Return to the top of the MV-03 subject statements (triples).

Requirement Structure

5 possible subject statements:

Contract has part Contract
Contract has part Requirement
Requirement has part Requirement
Standard has part Requirement
Standard has part Standard

Return to the top of the MV-03 subject statements (triples).

Traceability or Reference

126 possible subject statements:

Architecture Description traces to Contract
Architecture Description traces to Requirement
Architecture Description traces to Standard
Architecture Task traces to Contract
Architecture Task traces to Requirement
Architecture Task traces to Standard
Architecture View traces to Contract
Architecture View traces to Requirement
Architecture View traces to Standard
Argument traces to Contract
Argument traces to Requirement
Argument traces to Standard
Capability traces to Contract
Capability traces to Requirement
Capability traces to Standard
Claim traces to Contract
Claim traces to Requirement
Claim traces to Standard
Competence traces to Contract
Competence traces to Requirement
Competence traces to Standard
Concept Activity traces to Contract
Concept Activity traces to Requirement
Concept Activity traces to Standard
Concern traces to Contract
Concern traces to Requirement
Concern traces to Standard
Contract traces to Contract
Contract traces to Requirement
Contract traces to Standard
Document traces to Contract
Document traces to Requirement
Document traces to Standard
Enterprise Goal traces to Contract
Enterprise Goal traces to Requirement
Enterprise Goal traces to Standard
Enterprise traces to Contract
Enterprise traces to Requirement
Enterprise traces to Standard
Event traces to Contract
Event traces to Requirement
Event traces to Standard
Evidence traces to Contract
Evidence traces to Requirement
Evidence traces to Standard
Function traces to Contract
Function traces to Requirement
Function traces to Standard
Interaction Element traces to Contract
Interaction Element traces to Requirement
Interaction Element traces to Standard
Item Exchange traces to Contract
Item Exchange traces to Requirement
Item Exchange traces to Standard
Item traces to Contract
Item traces to Requirement
Item traces to Standard
Job traces to Contract
Job traces to Requirement
Job traces to Standard
Metric traces to Contract
Metric traces to Requirement
Metric traces to Standard
Milestone traces to Contract
Milestone traces to Requirement
Milestone traces to Standard
Mitigation traces to Contract
Mitigation traces to Requirement
Mitigation traces to Standard
Need traces to Contract
Need traces to Requirement
Need traces to Standard
Node traces to Contract
Node traces to Requirement
Node traces to Standard
Organisation traces to Contract
Organisation traces to Requirement
Organisation traces to Standard
Physical traces to Contract
Physical traces to Requirement
Physical traces to Standard
Port Connection traces to Contract
Port Connection traces to Requirement
Port Connection traces to Standard
Port traces to Contract
Port traces to Requirement
Port traces to Standard
Project Activity traces to Contract
Project Activity traces to Requirement
Project Activity traces to Standard
Project traces to Contract
Project traces to Requirement
Project traces to Standard
Protocol traces to Contract
Protocol traces to Requirement
Protocol traces to Standard
Requirement traces to Contract
Requirement traces to Requirement
Requirement traces to Standard
Resource Interaction traces to Contract
Resource Interaction traces to Requirement
Resource Interaction traces to Standard
Risk traces to Contract
Risk traces to Requirement
Risk traces to Standard
Role traces to Contract
Role traces to Requirement
Role traces to Standard
Software traces to Contract
Software traces to Requirement
Software traces to Standard
Standard traces to Contract
Standard traces to Requirement
Standard traces to Standard
System traces to Contract
System traces to Requirement
System traces to Standard
Threat traces to Contract
Threat traces to Requirement
Threat traces to Standard
Vulnerability traces to Contract
Vulnerability traces to Requirement
Vulnerability traces to Standard
Zone traces to Contract
Zone traces to Requirement
Zone traces to Standard

Return to the top of the MV-03 subject statements (triples).

Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..

Optional Statements (Triples)

These optional statements (triples) for the MV-03 Requirements and Standards architecture view provide useful context with respect to a subject or universally allowed statements involving the subject or object (start or finish) elements in the Subject Statements (triples).

Universal statements may be added to any TRAK architecture view and describe typical concepts such as compliance or traceability:

... traces to Argument, Contract, Requirement, Document or Standard
... satisfies Contract, Requirement, Document or Standard
Concern or Claim about ...
Contract, Requirement, Document or Standard governs ...

Example of a 'Concern about Node' optional triple for the MV-03 Requirements and Standards Architecture View

'Concern about Node' - an optional statement or assertion for the MV-03 Architecture View

These statements address the concerns of their respective architecture viewpoint and will have been created first on these other architecture views.

There are 420 possible statements which may be used to augment the MV-03 Requirements and Standards architecture view, split into 4 groups:

Conformance Claims
Universal - Assurance
Universal - Concern Identified
Universal - Traceability or Reference

Return to the top of the Requirements and Standards page.

Conformance Claims

252 additional context statements:

Claim about Architecture Description satisfies Contract
Claim about Architecture Description satisfies Requirement
Claim about Architecture Description satisfies Standard
Claim about Architecture Task satisfies Contract
Claim about Architecture Task satisfies Requirement
Claim about Architecture Task satisfies Standard
Claim about Architecture View satisfies Contract
Claim about Architecture View satisfies Requirement
Claim about Architecture View satisfies Standard
Claim about Argument satisfies Contract
Claim about Argument satisfies Requirement
Claim about Argument satisfies Standard
Claim about Capability satisfies Contract
Claim about Capability satisfies Requirement
Claim about Capability satisfies Standard
Claim about Claim satisfies Contract
Claim about Claim satisfies Requirement
Claim about Claim satisfies Standard
Claim about Competence satisfies Contract
Claim about Competence satisfies Requirement
Claim about Competence satisfies Standard
Claim about Concept Activity satisfies Contract
Claim about Concept Activity satisfies Requirement
Claim about Concept Activity satisfies Standard
Claim about Concern satisfies Contract
Claim about Concern satisfies Requirement
Claim about Concern satisfies Standard
Claim about Contract governs Architecture Description
Claim about Contract governs Architecture Task
Claim about Contract governs Architecture View
Claim about Contract governs Argument
Claim about Contract governs Capability
Claim about Contract governs Claim
Claim about Contract governs Competence
Claim about Contract governs Concept Activity
Claim about Contract governs Concern
Claim about Contract governs Contract
Claim about Contract governs Document
Claim about Contract governs Enterprise Goal
Claim about Contract governs Enterprise
Claim about Contract governs Event
Claim about Contract governs Evidence
Claim about Contract governs Function
Claim about Contract governs Interaction Element
Claim about Contract governs Item Exchange
Claim about Contract governs Item
Claim about Contract governs Job
Claim about Contract governs Metric
Claim about Contract governs Milestone
Claim about Contract governs Mitigation
Claim about Contract governs Need
Claim about Contract governs Node
Claim about Contract governs Organisation
Claim about Contract governs Physical
Claim about Contract governs Port Connection
Claim about Contract governs Port
Claim about Contract governs Project Activity
Claim about Contract governs Project
Claim about Contract governs Protocol
Claim about Contract governs Requirement
Claim about Contract governs Resource Interaction
Claim about Contract governs Risk
Claim about Contract governs Role
Claim about Contract governs Software
Claim about Contract governs Standard
Claim about Contract governs System
Claim about Contract governs Threat
Claim about Contract governs Vulnerability
Claim about Contract governs Zone
Claim about Contract satisfies Contract
Claim about Contract satisfies Requirement
Claim about Contract satisfies Standard
Claim about Document satisfies Contract
Claim about Document satisfies Requirement
Claim about Document satisfies Standard
Claim about Enterprise Goal satisfies Contract
Claim about Enterprise Goal satisfies Requirement
Claim about Enterprise Goal satisfies Standard
Claim about Enterprise satisfies Contract
Claim about Enterprise satisfies Requirement
Claim about Enterprise satisfies Standard
Claim about Event satisfies Contract
Claim about Event satisfies Requirement
Claim about Event satisfies Standard
Claim about Evidence satisfies Contract
Claim about Evidence satisfies Requirement
Claim about Evidence satisfies Standard
Claim about Function satisfies Contract
Claim about Function satisfies Requirement
Claim about Function satisfies Standard
Claim about Interaction Element satisfies Contract
Claim about Interaction Element satisfies Requirement
Claim about Interaction Element satisfies Standard
Claim about Item Exchange satisfies Contract
Claim about Item Exchange satisfies Requirement
Claim about Item Exchange satisfies Standard
Claim about Item satisfies Contract
Claim about Item satisfies Requirement
Claim about Item satisfies Standard
Claim about Job satisfies Contract
Claim about Job satisfies Requirement
Claim about Job satisfies Standard
Claim about Metric satisfies Contract
Claim about Metric satisfies Requirement
Claim about Metric satisfies Standard
Claim about Milestone satisfies Contract
Claim about Milestone satisfies Requirement
Claim about Milestone satisfies Standard
Claim about Mitigation satisfies Contract
Claim about Mitigation satisfies Requirement
Claim about Mitigation satisfies Standard
Claim about Need satisfies Contract
Claim about Need satisfies Requirement
Claim about Need satisfies Standard
Claim about Node satisfies Contract
Claim about Node satisfies Requirement
Claim about Node satisfies Standard
Claim about Organisation satisfies Contract
Claim about Organisation satisfies Requirement
Claim about Organisation satisfies Standard
Claim about Physical satisfies Contract
Claim about Physical satisfies Requirement
Claim about Physical satisfies Standard
Claim about Port Connection satisfies Contract
Claim about Port Connection satisfies Requirement
Claim about Port Connection satisfies Standard
Claim about Port satisfies Contract
Claim about Port satisfies Requirement
Claim about Port satisfies Standard
Claim about Project Activity satisfies Contract
Claim about Project Activity satisfies Requirement
Claim about Project Activity satisfies Standard
Claim about Project satisfies Contract
Claim about Project satisfies Requirement
Claim about Project satisfies Standard
Claim about Protocol satisfies Contract
Claim about Protocol satisfies Requirement
Claim about Protocol satisfies Standard
Claim about Requirement governs Architecture Description
Claim about Requirement governs Architecture Task
Claim about Requirement governs Architecture View
Claim about Requirement governs Argument
Claim about Requirement governs Capability
Claim about Requirement governs Claim
Claim about Requirement governs Competence
Claim about Requirement governs Concept Activity
Claim about Requirement governs Concern
Claim about Requirement governs Contract
Claim about Requirement governs Document
Claim about Requirement governs Enterprise Goal
Claim about Requirement governs Enterprise
Claim about Requirement governs Event
Claim about Requirement governs Evidence
Claim about Requirement governs Function
Claim about Requirement governs Interaction Element
Claim about Requirement governs Item Exchange
Claim about Requirement governs Item
Claim about Requirement governs Job
Claim about Requirement governs Metric
Claim about Requirement governs Milestone
Claim about Requirement governs Mitigation
Claim about Requirement governs Need
Claim about Requirement governs Node
Claim about Requirement governs Organisation
Claim about Requirement governs Physical
Claim about Requirement governs Port Connection
Claim about Requirement governs Port
Claim about Requirement governs Project Activity
Claim about Requirement governs Project
Claim about Requirement governs Protocol
Claim about Requirement governs Requirement
Claim about Requirement governs Resource Interaction
Claim about Requirement governs Risk
Claim about Requirement governs Role
Claim about Requirement governs Software
Claim about Requirement governs Standard
Claim about Requirement governs System
Claim about Requirement governs Threat
Claim about Requirement governs Vulnerability
Claim about Requirement governs Zone
Claim about Requirement satisfies Contract
Claim about Requirement satisfies Requirement
Claim about Requirement satisfies Standard
Claim about Resource Interaction satisfies Contract
Claim about Resource Interaction satisfies Requirement
Claim about Resource Interaction satisfies Standard
Claim about Risk satisfies Contract
Claim about Risk satisfies Requirement
Claim about Risk satisfies Standard
Claim about Role satisfies Contract
Claim about Role satisfies Requirement
Claim about Role satisfies Standard
Claim about Software satisfies Contract
Claim about Software satisfies Requirement
Claim about Software satisfies Standard
Claim about Standard governs Architecture Description
Claim about Standard governs Architecture Task
Claim about Standard governs Architecture View
Claim about Standard governs Argument
Claim about Standard governs Capability
Claim about Standard governs Claim
Claim about Standard governs Competence
Claim about Standard governs Concept Activity
Claim about Standard governs Concern
Claim about Standard governs Contract
Claim about Standard governs Document
Claim about Standard governs Enterprise Goal
Claim about Standard governs Enterprise
Claim about Standard governs Event
Claim about Standard governs Evidence
Claim about Standard governs Function
Claim about Standard governs Interaction Element
Claim about Standard governs Item Exchange
Claim about Standard governs Item
Claim about Standard governs Job
Claim about Standard governs Metric
Claim about Standard governs Milestone
Claim about Standard governs Mitigation
Claim about Standard governs Need
Claim about Standard governs Node
Claim about Standard governs Organisation
Claim about Standard governs Physical
Claim about Standard governs Port Connection
Claim about Standard governs Port
Claim about Standard governs Project Activity
Claim about Standard governs Project
Claim about Standard governs Protocol
Claim about Standard governs Requirement
Claim about Standard governs Resource Interaction
Claim about Standard governs Risk
Claim about Standard governs Role
Claim about Standard governs Software
Claim about Standard governs Standard
Claim about Standard governs System
Claim about Standard governs Threat
Claim about Standard governs Vulnerability
Claim about Standard governs Zone
Claim about Standard satisfies Contract
Claim about Standard satisfies Requirement
Claim about Standard satisfies Standard
Claim about System satisfies Contract
Claim about System satisfies Requirement
Claim about System satisfies Standard
Claim about Threat satisfies Contract
Claim about Threat satisfies Requirement
Claim about Threat satisfies Standard
Claim about Vulnerability satisfies Contract
Claim about Vulnerability satisfies Requirement
Claim about Vulnerability satisfies Standard
Claim about Zone satisfies Contract
Claim about Zone satisfies Requirement
Claim about Zone satisfies Standard

Return to the top of the MV-03 optional statements (triples).

Universal - Assurance

84 additional context statements:

Architecture Description traces to Argument
Architecture Task traces to Argument
Architecture View traces to Argument
Argument traces to Argument
Capability traces to Argument
Claim about Architecture Description
Claim about Architecture Task
Claim about Architecture View
Claim about Argument
Claim about Capability
Claim about Claim
Claim about Competence
Claim about Concept Activity
Claim about Concern
Claim about Contract
Claim about Document
Claim about Enterprise
Claim about Enterprise Goal
Claim about Event
Claim about Evidence
Claim about Function
Claim about Interaction Element
Claim about Item
Claim about Item Exchange
Claim about Job
Claim about Metric
Claim about Milestone
Claim about Mitigation
Claim about Need
Claim about Node
Claim about Organisation
Claim about Physical
Claim about Port
Claim about Port Connection
Claim about Project
Claim about Project Activity
Claim about Protocol
Claim about Requirement
Claim about Resource Interaction
Claim about Risk
Claim about Role
Claim about Software
Claim about Standard
Claim about System
Claim about Threat
Claim about Vulnerability
Claim about Zone
Claim traces to Argument
Competence traces to Argument
Concept Activity traces to Argument
Concern traces to Argument
Contract traces to Argument
Document traces to Argument
Enterprise Goal traces to Argument
Enterprise traces to Argument
Event traces to Argument
Evidence traces to Argument
Function traces to Argument
Interaction Element traces to Argument
Item Exchange traces to Argument
Item traces to Argument
Job traces to Argument
Metric traces to Argument
Milestone traces to Argument
Mitigation traces to Argument
Need traces to Argument
Node traces to Argument
Organisation traces to Argument
Physical traces to Argument
Port Connection traces to Argument
Port traces to Argument
Project Activity traces to Argument
Project traces to Argument
Protocol traces to Argument
Requirement traces to Argument
Resource Interaction traces to Argument
Risk traces to Argument
Role traces to Argument
Software traces to Argument
Standard traces to Argument
System traces to Argument
Threat traces to Argument
Vulnerability traces to Argument
Zone traces to Argument

Return to the top of the MV-03 optional statements (triples).

Universal - Concern Identified

42 additional context statements:

Concern about Architecture Description
Concern about Architecture Task
Concern about Architecture View
Concern about Argument
Concern about Capability
Concern about Claim
Concern about Competence
Concern about Concept Activity
Concern about Concern
Concern about Contract
Concern about Document
Concern about Enterprise
Concern about Enterprise Goal
Concern about Event
Concern about Evidence
Concern about Function
Concern about Interaction Element
Concern about Item
Concern about Item Exchange
Concern about Job
Concern about Metric
Concern about Milestone
Concern about Mitigation
Concern about Need
Concern about Node
Concern about Organisation
Concern about Physical
Concern about Port
Concern about Port Connection
Concern about Project
Concern about Project Activity
Concern about Protocol
Concern about Requirement
Concern about Resource Interaction
Concern about Risk
Concern about Role
Concern about Software
Concern about Standard
Concern about System
Concern about Threat
Concern about Vulnerability
Concern about Zone

Return to the top of the MV-03 optional statements (triples).

Universal - Traceability or Reference

42 additional context statements:

Architecture Description traces to Document
Architecture Task traces to Document
Architecture View traces to Document
Argument traces to Document
Capability traces to Document
Claim traces to Document
Competence traces to Document
Concept Activity traces to Document
Concern traces to Document
Contract traces to Document
Document traces to Document
Enterprise Goal traces to Document
Enterprise traces to Document
Event traces to Document
Evidence traces to Document
Function traces to Document
Interaction Element traces to Document
Item Exchange traces to Document
Item traces to Document
Job traces to Document
Metric traces to Document
Milestone traces to Document
Mitigation traces to Document
Need traces to Document
Node traces to Document
Organisation traces to Document
Physical traces to Document
Port Connection traces to Document
Port traces to Document
Project Activity traces to Document
Project traces to Document
Protocol traces to Document
Requirement traces to Document
Resource Interaction traces to Document
Risk traces to Document
Role traces to Document
Software traces to Document
Standard traces to Document
System traces to Document
Threat traces to Document
Vulnerability traces to Document
Zone traces to Document

Return to the top of the MV-03 optional statements (triples).

Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..

Well-Formedness Criteria

This web site is a partial representation of the TRAK Architecture Viewpoints Specification

Well-formedness criteria define the minimum acceptable view content based on the subject statements (triples). These criteria are not included in this web page.

Please refer to the Well Formedness section within the MVp-03 Requirements and Standards architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (30 April 2025).

Presentation Methods

The MV-03 Requirements and Standards architecture view may use any of following means to represent the statements (triples):

Block diagram
Table
textual representation of triples e.g. Turtle / RDF

Note that a textual presentation is acceptable for any TRAK architecture view.

Examples

Example of a MV-03 Requirements and Standards Architecture View - Example MV-03 Requirements & Standards Architecture View - Part of ISO/IEC/IEEE 42010:2011

Example MV-03 Requirements & Standards Architecture View - Part of ISO/IEC/IEEE 42010:2011

An example of a TRAK MV-03 Requirements & Standards architecture view describing the top level structure of ISO/IEC/IEEE 42010:2011 - the international standard for architecture description.

This is a UML implementation. The outer shaded boundary is purely for ornamentation - a UML boundary element has no formal meaning with respect to elements inside the rectangular boundary shape unlike other UML elements where positioning inside an element implies that there is a relationship with the containing element, for example, ownership. This inconsistency of presentation vs meaning is a weakness of the UML.

Produced using (Sparx Systems Enterprise Architect UML modelling tool in conjunction with the MDG for TRAK plugin (https://sf.net/p/mdgfortrak.)

Requirement Structure

Example of a MV-03 Requirements and Standards Architecture View - MV-03 Illustrating Structure of ISO/IEC/IEEE 42010:2011 for Architecture Viewpoints

MV-03 Illustrating Structure of ISO/IEC/IEEE 42010:2011 for Architecture Viewpoints

This example illustrates the use of the MV-03 to describe a requirement hierarchy. It describes the ISO/IEC/IEEE 42010:2011 requirements that apply to architecture viewpoints. Note that local requirement identifiers and sequence identifiers are used a) because the standard has no requirement identifiers and b) to preserve the order of the printed version.

The MV-03 can be used to form the "front part" of a Compliance Matrix outlining the applicable requirements and the compliance level required. The degree of compliance achieved is then described using the MV-04 Assurance architecture view using Claims of compliance with each Requirement.

The TRAK Requirement metamodel element has many properties incuding 'requirement identifier', 'sequence identifier', 'compliance level required', 'requirement paragraph number' and 'verification method' amongst many others.

Produced using (Sparx Systems Enterprise Architect UML modelling tool in conjunction with the MDG for TRAK plugin (https://sf.net/p/mdgfortrak.)

Requirement Structure

              
              
             
@prefix trak: <https://purl.org/trak/elements/#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ad: <http://ad_base_uri#> .
 
 # Standard - ISO/IEC/IEEE 42010:2011
 ad:42010_2011 a trak:Standard;
	trak:DCMI_title "Systems and Software – Architecture Description"@en ;
	trak:DCMI_identifier "ISO/IEC/IEEE 42010:2011"@en ;
	trak:has_part ad:reqt1 ;
	trak:has_part ad:reqt2 ;
	trak:has_part ad:reqt3 .
 
 # requirement 1
 ad:reqt1 a trak:Requirement ;
	trak:requirement_identifier "5.2 1.1" ;
	trak:compliance_level_required "Mandatory" ;
	trak:requirement_text "An architecture description shall identify the system-of-interest"@en .
 
 # requirement 2
ad:reqt2 a trak:Requirement ;
	trak:requirement_identifier "6.1 a" ;
 	trak:compliance_level_required "Mandatory" ;
 	trak:requirement_text "An architecture framework shall include: a) information identifying the architecture framework;"@en .
 
 # requirement 3
ad:reqt3 a trak:Requirement ;
	trak:requirement_identifier "7 a" ;
 	trak:compliance_level_required "Mandatory" ;
 	trak:requirement_text "An architecture viewpoint shall specify: a) one or more concerns framed by this viewpoint"@en .

MV-03 Turtle (RDF) Describing 3 Requirements

This illustrates the use of Turtle (RDF) triples to describe a standard having 3 atomic requirements.

Views Needed to Construct

This web site is a partial representation of the TRAK Architecture Viewpoints Specification

Since a triple originates in a particular architecture view if there is a subsequent architecture view that uses the same triple it need not be created. Similarly you might wish to create a triple but in order to do so the node element has first to be created in its originating architecture view.

For example, you cannot describe the functionality of an element without first defining the element having that functionality. These dependencies between architecture views create a natural sequence or order in which architecture views are created by virtue of their content. These criteria are not yet included in this web page.

Please refer to the Views Needed in Order to Construct section within the MVp-03 Requirements and Standards architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (30 April 2025).

Consistency Rules

This web site is a partial representation of the TRAK Architecture Viewpoints Specification

Consistency rules define rules applied to keep the collection of architecture views consistent and also to keep the logic formed by the statements using triples consistent. These criteria are not included in this web page.

Please refer to the Consistency Rules section within the MVp-03 Requirements and Standards architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (30 April 2025).

Comments

The MV-03 Requirements and Standards architecture view is the master source (origin) on which you first create the following elements or statements:

The views produced are expected to focus primarily on contracts, standards and requirements. Requirement-focussed views will make it possible to show how the architecture description links to products from requirement management tools such as DOORS and also act as a justification for the way in which the architecture has been represented in the architecture description. It is not the purpose of an architecture framework to manage requirements. Is it the purpose of TRAK to provide a means of integrating architecture description with dedicated requirement management tools.

Attributes should be used to add appropriate detail (TRAK Metamodel document)

Requirement has attributes that include requirement identifier, sequence identifier (to describe an order of requirements such as in a document), compliance level (e.g. mandatory or desirable), priority, paragraph number, type (e.g. legal, commercial or technical)
Architecture Description Element has attributes that include security descriptors
Document has attributes that include Dublin Core Metadata elements
Contract has attributes for start and finish dates and parties to the contract.
Standard has attributes that include issue date, part, number and withdrawal date. If no issue or version number for Standard is identified it is assumed that the latest version applies (even if subsequently withdrawn). This allows an architect to declare that a standard applies before they’ve identified the version.

The MV-03 can be used to describe Capability Requirement Documents, Operational Requirement Documents and System Requirement Documents. Requirements aren’t just technical - they may be commercial such as in a Contract. Any constraint has at some stage to be formally captured by a requirement.

More complicated forms are possible by using the date of issue of the standard as a filter. Note that usually, with the exception of national law and safety, once a standard has been applied by contract it will fix the requirements at the issue of the standard applied irrespective of any more recent issues.

Neighbouring Architecture Views

The MV-03 Requirements and Standards architecture view content may overlap that of the following neighbouring architecture views:

Navigation & Website Tracker

Spotted an error or want to suggest something - create a ticket

Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..

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.