MVp-04 Assurance
This page reproduces part of the MVp-04 Assurance 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-04 Assurance architecture viewpoint is one of 24 architecture viewpoints defined in TRAK00001. TRAK. Architecture Framework. Viewpoints - current release is dated 30 April 2025.
Perspective | Viewpoint | View ID | Version | Modified |
Management | MVp-04 | MV-04 | 6 | 2025-04-30 |
Summary
The TRAK MVp-04 Assurance architecture viewpoint defines the requirements for the TRAK MV-04 Assurance 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-04 Assurance architecture viewpoint content is summarised under the following sections:
- stakeholder concerns
- description
- allowed content
- 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-04 Assurance architecture viewpoint but considerations for the architecture description formed from a set of architecture views.
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns.
Stakeholder Concerns
Stakeholder Concerns Addressed by the MVp-04 Assurance Architecture Viewpoint
The TRAK MVp-04 Assurance architecture viewpoint addresses the following concerns:
- Is the claim supported by evidence?
- What are the claims made?
- What is the basis of the claim?
Description
Describes a claim made about any other element with supporting (or opposing) arguments and evidence to establish how and whether a claim is proved or disproved. (as a result of the assessed evidence).
Typical claims for solutions include that a system is safe, fit for purpose and meets its requirements.
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Claim about Event' that form short statements about the thing(s) being described.
'Claim about Event' is a Statement or Assertion in a MV-04 Architecture View
The rationale and theory for the allowed content of an architecture view is explained separately.
The allowed MV-04 architecture view content is split into:-
Subject Statements (Triples)
These are statements (triples) that describe the subject of the MV-04 Assurance architecture view. Specifically these statements address the concerns for this MVp-04 Assurance architecture viewpoint. These form the basis for the well-formedness section of the MVp-04 Assurance architecture viewpoint.
These involve every metamodel element and may be added as content on any other architecture view. This is why the MV-04 Assurance architecture view is part of the Management Perspective.
There are 351 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 5 groups:
- Identification of Argument
- Identification of Claim
- Identification of Claim (N-ary)
- Response to Argument
- Verification of Claim / Argument
Return to the top of the Assurance page.
Identification of Argument
5 possible subject statements:
- Argument has part Argument
- Argument opposes Argument
- Argument opposes Claim
- Argument supports Argument
- Argument supports Claim
Return to the top of the MV-04 subject statements (triples).
Identification of Claim
47 possible subject statements:
- 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 has part Claim
- Claim opposes Claim
- Claim supports Claim
- Organisation makes Claim
- Role makes Claim
Return to the top of the MV-04 subject statements (triples).
Identification of Claim (N-ary)
252 possible subject 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-04 subject statements (triples).
Response to Argument
42 possible subject 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 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-04 subject statements (triples).
Verification of Claim / Argument
5 possible subject statements:
- Evidence disproves Claim
- Evidence has part Evidence
- Evidence opposes Argument
- Evidence proves Claim
- Evidence supports Argument
Return to the top of the MV-04 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-04 Assurance 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 ...
'Architecture View traces to Requirement' - an optional statement or assertion for the MV-04 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 434 possible statements which may be used to augment the MV-04 Assurance architecture view, split into 5 groups:
- Context - Roles
- Document Publisher
- Universal - Applicable Requirements
- Universal - Requirement Compliance
- Universal - Traceability or Reference
Return to the top of the Assurance page.
Context - Roles
8 additional context statements:
- Job plays Role
- Organisation plays Role
- Role extends to Job
- Role extends to Organisation
- Role extends to Physical
- Role extends to Role
- Role extends to Software
- Role extends to System
Return to the top of the MV-04 optional statements (triples).
Document Publisher
6 additional context statements:
- Architecture Description issued by Organisation
- Architecture View issued by Organisation
- Contract issued by Organisation
- Document issued by Organisation
- Evidence issued by Organisation
- Standard issued by Organisation
Return to the top of the MV-04 optional statements (triples).
Universal - Applicable Requirements
126 additional context 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
- 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
Return to the top of the MV-04 optional statements (triples).
Universal - Requirement Compliance
126 additional context 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-04 optional statements (triples).
Universal - Traceability or Reference
168 additional context statements:
- Architecture Description traces to Contract
- Architecture Description traces to Document
- Architecture Description traces to Requirement
- Architecture Description traces to Standard
- Architecture Task traces to Contract
- Architecture Task traces to Document
- Architecture Task traces to Requirement
- Architecture Task traces to Standard
- Architecture View traces to Contract
- Architecture View traces to Document
- Architecture View traces to Requirement
- Architecture View traces to Standard
- Argument traces to Contract
- Argument traces to Document
- Argument traces to Requirement
- Argument traces to Standard
- Capability traces to Contract
- Capability traces to Document
- Capability traces to Requirement
- Capability traces to Standard
- Claim traces to Contract
- Claim traces to Document
- Claim traces to Requirement
- Claim traces to Standard
- Competence traces to Contract
- Competence traces to Document
- Competence traces to Requirement
- Competence traces to Standard
- Concept Activity traces to Contract
- Concept Activity traces to Document
- Concept Activity traces to Requirement
- Concept Activity traces to Standard
- Concern traces to Contract
- Concern traces to Document
- Concern traces to Requirement
- Concern traces to Standard
- Contract traces to Contract
- Contract traces to Document
- Contract traces to Requirement
- Contract traces to Standard
- Document traces to Contract
- Document traces to Document
- Document traces to Requirement
- Document traces to Standard
- Enterprise Goal traces to Contract
- Enterprise Goal traces to Document
- Enterprise Goal traces to Requirement
- Enterprise Goal traces to Standard
- Enterprise traces to Contract
- Enterprise traces to Document
- Enterprise traces to Requirement
- Enterprise traces to Standard
- Event traces to Contract
- Event traces to Document
- Event traces to Requirement
- Event traces to Standard
- Evidence traces to Contract
- Evidence traces to Document
- Evidence traces to Requirement
- Evidence traces to Standard
- Function traces to Contract
- Function traces to Document
- Function traces to Requirement
- Function traces to Standard
- Interaction Element traces to Contract
- Interaction Element traces to Document
- Interaction Element traces to Requirement
- Interaction Element traces to Standard
- Item Exchange traces to Contract
- Item Exchange traces to Document
- Item Exchange traces to Requirement
- Item Exchange traces to Standard
- Item traces to Contract
- Item traces to Document
- Item traces to Requirement
- Item traces to Standard
- Job traces to Contract
- Job traces to Document
- Job traces to Requirement
- Job traces to Standard
- Metric traces to Contract
- Metric traces to Document
- Metric traces to Requirement
- Metric traces to Standard
- Milestone traces to Contract
- Milestone traces to Document
- Milestone traces to Requirement
- Milestone traces to Standard
- Mitigation traces to Contract
- Mitigation traces to Document
- Mitigation traces to Requirement
- Mitigation traces to Standard
- Need traces to Contract
- Need traces to Document
- Need traces to Requirement
- Need traces to Standard
- Node traces to Contract
- Node traces to Document
- Node traces to Requirement
- Node traces to Standard
- Organisation traces to Contract
- Organisation traces to Document
- Organisation traces to Requirement
- Organisation traces to Standard
- Physical traces to Contract
- Physical traces to Document
- Physical traces to Requirement
- Physical traces to Standard
- Port Connection traces to Contract
- Port Connection traces to Document
- Port Connection traces to Requirement
- Port Connection traces to Standard
- Port traces to Contract
- Port traces to Document
- Port traces to Requirement
- Port traces to Standard
- Project Activity traces to Contract
- Project Activity traces to Document
- Project Activity traces to Requirement
- Project Activity traces to Standard
- Project traces to Contract
- Project traces to Document
- Project traces to Requirement
- Project traces to Standard
- Protocol traces to Contract
- Protocol traces to Document
- Protocol traces to Requirement
- Protocol traces to Standard
- Requirement traces to Contract
- Requirement traces to Document
- Requirement traces to Requirement
- Requirement traces to Standard
- Resource Interaction traces to Contract
- Resource Interaction traces to Document
- Resource Interaction traces to Requirement
- Resource Interaction traces to Standard
- Risk traces to Contract
- Risk traces to Document
- Risk traces to Requirement
- Risk traces to Standard
- Role traces to Contract
- Role traces to Document
- Role traces to Requirement
- Role traces to Standard
- Software traces to Contract
- Software traces to Document
- Software traces to Requirement
- Software traces to Standard
- Standard traces to Contract
- Standard traces to Document
- Standard traces to Requirement
- Standard traces to Standard
- System traces to Contract
- System traces to Document
- System traces to Requirement
- System traces to Standard
- Threat traces to Contract
- Threat traces to Document
- Threat traces to Requirement
- Threat traces to Standard
- Vulnerability traces to Contract
- Vulnerability traces to Document
- Vulnerability traces to Requirement
- Vulnerability traces to Standard
- Zone traces to Contract
- Zone traces to Document
- Zone traces to Requirement
- Zone traces to Standard
Return to the top of the MV-04 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-04 Assurance architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (30 April 2025).
Presentation Methods
The MV-04 Assurance 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
Identification of Claim / Forming Argument
MV-04 Describing Conformance of Software - N-ary (Block Diagram)
Example MV-04 Assurance View describing a claim of conformance of software against a particular standard. This block diagram illustrates the use of a N-ary triple where the object of a triple is another triples, in this case Claim about (Software satisfies Standard)
Identification of Claim / Forming Argument
# Example MV-04 Assurance architecture view - Text - Turtle (RDF)
# Uses reification to describe N-ary triple
# Claim about (Software satisfies Standard)
@prefix trak: <https://purl.org/trak/elements/#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema.rdf#>.
@prefix ad_base_uri: <https://some_uri> .
# describe Standard
ad_base_uri:iso_14882 a trak:Standard;
trak:DCMI_title "Programming Language C++"@en ;
trak:DCMI_identifier "ISO/IEC 14882:2024"@en ;
rdfs:label "This document specifies requirements for implementations of the C++ programming language. The first such requirement is that they implement the language, so this document also defines C++."@en .
# describe Software
ad_base_uri:xml_studio a trak:Software;
trak:name "XML Studio"@en ;
trak:DCMI_identifier "com.whizz_inc.xml_studio.13_123" ;
trak:software_type trak:Application .
# describe conformance Claim
ad_base_uri:conformance_claim_c001 a trak:Claim ;
trak:claim_identifier "C001" ;
trak:name "XML studio fully complies with the ISO/IEC 14482:2024"@en ;
trak:compliance_level_claimed trak:Full .
# define 'Software satisfies Standard' as an identifiable triple
ad_base_uri:Satisfies_Assertion1 a rdf:Statement;
rdf:subject ad_base_uri:xml_studio ;
rdf:predicate trak:satisfies ;
rdf:object ad_base_uri:iso_14882.
# make Claim about Satisfies_Assertion1 triple
ad_base_uri:conformance_claim_c001 trak:about ad_base_uri:Satisfies_Assertion1 .
MV-04 Describing Conformance of Software - N-ary (Turtle/RDF)
Example MV-04 Assurance View describing a claim of conformance of software against a particular standard using text - Turtle (RDF). Illustrates the use of reification where the triple 'Software satisfies Standard' is defined as the object of a triple i.e. - a N-ary triple.
It is also possible using the W3C Turtle-star extension to Turtle to define a 'quoted triple' within << ..>> for example:
ad_base_uri:conformance_claim_c001 trak:about <<ad_base_uri:xml_studio trak:satisfies ad_base_uri:iso_14882 >> .
Verification of Claim / Argument
MV-04 Describing Compliance of TRAK Architecture Framework Against ISO/IEC/IEEE 42010:2011 6.1 e Architecture Frameworks - Consistency
This example illustrates the use of a MV-04 assurance view to describe compliance against requirements supported by arguments and evidence This then enables a Compliance Matrix to be produced.
This particular example describes compliance of TRAK as an architecture framework against ISO/IEC/IEEE 42010:2011 6.1 e wrt consistency with the ISO 42010 conceptual model. Note that the Evidence elements contain the particular piece(s) of textual evidence that support the particular Argument(s).
The requirement structure/hierarchy is described first using a MV-03 Requirements and Standards architecture view.
Produced using a Neo4J graph database (community version) implementation of a TRAK architecture description.
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-04 Assurance 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-04 Assurance architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (30 April 2025).
Comments
The MV-04 Assurance architecture view is the master source (origin) on which you first create the following elements or statements:
The supporting (opposing) parts of an Argument or Evidence by inference also support the Claim or Argument respectively to which the top-most ‘whole’ Argument or Evidence is connected. The part Arguments or part Evidences may also support other Argument or Evidence elements.
A counter-claim is established using 'Claim opposes Claim'.
A counter-argument is established using 'Argument opposes Argument' (and is usually followed by (same) Argument opposes Claim).
When the 'acceptance date' attribute of a Claim, Argument or Evidence element is non-null and valid (not in the future) that element is deemed to have been accepted by the assessor of the claim.
Claims can be made against any element in any TRAK perspective. Claims can be made against a concept, the enterprise and its capabilities and goals, against a system and its ability to realise these capabilities. Claims can also be made against a project, its structure or activities (and thence against the introduction or removal from service of a system). Claims can also be made against standards or against a contract and its requirements.
Applied to the solution perspective this viewpoint supports the creation of a structured safety argument ("safety case"). It can also be used for design verification against the requirements for the design where there is a set of claims that the design meets these requirements. In this sense it could be used to describe how the organisation’s processes meet a set of external normative requirements ('Standards' in TRAK).
Neighbouring Architecture Views
The MV-04 Assurance architecture view content may overlap that of the following neighbouring architecture views:
- CV-01 Concept Need
- CV-03 Concept Item Exchange
- CV-04 Concept Activity to Enterprise Capability Mapping
- CV-05 Concept Activity
- CV-06 Concept Sequence
- EV-01 Enterprise Goal
- EV-02 Capability Hierarchy
- EV-03 Capability Phasing
- MV-01 Architecture Description Dictionary
- MV-02 Architecture Description Design Record
- MV-03 Requirements and Standards
- PrV-01 Procurement Structure
- PrV-02 Procurement Timeline
- PrV-03 Procurement Responsibility
- SV-01 Solution Structure
- SV-02 Solution Resource Interaction
- SV-03 Solution Resource Interaction to Function Mapping
- SV-04 Solution Function
- SV-05 Solution Function to Concept Activity Mapping
- SV-06 Solution Competence
- SV-07 Solution Sequence
- SV-11 Solution Event Causes
- SV-13 Solution Risk
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.