TRAK Architecture ViewpointsCVp-06 Concept Sequence
This page reproduces part of the CVp-06 Concept Sequence 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 CVp-06 Concept Sequence architecture viewpoint is one of 24 architecture viewpoints defined in TRAK00001. TRAK. Architecture Framework. Viewpoints - current release is dated 2024_07_10.
| Perspective | Viewpoint | View ID | Version | Modified |
| Concept | CVp-06 | CV-06 | 8 | 2017-12-08 |
Summary
The TRAK CVp-06 Concept Sequence architecture viewpoint defines the requirements for the TRAK CV-06 Concept Sequence 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 CVp-06 Concept Sequence architecture viewpoint content is summarised under the following sections:
- stakeholder concerns
- description
- allowed content
- well-formedness criteria
- presentation methods
- comments
The TRAK Architecture Viewpoints specification provides are complete definition not only of the CVp-06 Concept Sequence 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 CVp-06 Concept Sequence Architecture Viewpoint
The TRAK CVp-06 Concept Sequence architecture viewpoint addresses the following concerns:
- How are concept activities ordered?
- Is the concept activity order important?
Description
Describes the order in which logical events or concept activities occur.
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Item has part Item' that form short statements about the thing(s) being described.
'Item has part Item' is a Statement or Assertion in a CV-06 Architecture View
The rationale for this is explained separately.
Subject Statements (Triples)
These are statements (triples) that describe the subject of the CV-06 Concept Sequence architecture view. Specifically these statements address the concerns for this CVp-06 Concept Sequence architecture viewpoint. These form the basis for the well-formedness section of the CVp-06 Concept Sequence architecture viewpoint.
There are 9 possible subject statements in total which include 4 metamodel elements ( Concept Activity , Item , Item Exchange and Node ).
The subject statements are split into 2 groups:
Return to the top of the Concept Sequence page.
Exchange Sequence
5 possible subject statements:
- Concept Activity precedes Concept Activity
- Concept Activity triggers Item
- Item has part Item
- Item triggers Concept Activity
- Node conducts Concept Activity
Functional Sequence
4 possible subject statements:
- Item Exchange carries Item
- Item Exchange from Node
- Item Exchange to Node
- Item has part Item
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..
Optional Statements (Triples)
These optional statements (triples) for the CV-06 Concept Sequence 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 ...
'Concept Activity satisfies Standard' - an optional statement or assertion for the CV-06 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 53 possible statements which may be used to augment the CV-06 Concept Sequence architecture view, split into 6 groups:
- Context
- Universal - Applicable Requirements
- Universal - Assurance
- Universal - Concern Identified
- Universal - Requirement Compliance
- Universal - Traceability or Reference
Return to the top of the Concept Sequence page.
Context
1 additional context statements:
- Concept Activity has part Concept Activity
Return to the top of the CV-06 optional statements (triples).
Universal - Applicable Requirements
12 additional context statements:
- Contract governs Concept Activity
- Contract governs Item
- Contract governs Item Exchange
- Contract governs Node
- Requirement governs Concept Activity
- Requirement governs Item
- Requirement governs Item Exchange
- Requirement governs Node
- Standard governs Concept Activity
- Standard governs Item
- Standard governs Item Exchange
- Standard governs Node
Return to the top of the CV-06 optional statements (triples).
Universal - Assurance
8 additional context statements:
- Claim about Concept Activity
- Claim about Item
- Claim about Item Exchange
- Claim about Node
- Concept Activity traces to Argument
- Item Exchange traces to Argument
- Item traces to Argument
- Node traces to Argument
Return to the top of the CV-06 optional statements (triples).
Universal - Concern Identified
4 additional context statements:
- Concern about Concept Activity
- Concern about Item
- Concern about Item Exchange
- Concern about Node
Return to the top of the CV-06 optional statements (triples).
Universal - Requirement Compliance
12 additional context statements:
- Concept Activity satisfies Contract
- Concept Activity satisfies Requirement
- Concept Activity satisfies Standard
- Item Exchange satisfies Contract
- Item Exchange satisfies Requirement
- Item Exchange satisfies Standard
- Item satisfies Contract
- Item satisfies Requirement
- Item satisfies Standard
- Node satisfies Contract
- Node satisfies Requirement
- Node satisfies Standard
Return to the top of the CV-06 optional statements (triples).
Universal - Traceability or Reference
16 additional context statements:
- Concept Activity traces to Contract
- Concept Activity traces to Document
- Concept Activity traces to Requirement
- Concept Activity 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
- Node traces to Contract
- Node traces to Document
- Node traces to Requirement
- Node traces to Standard
Return to the top of the CV-06 optional statements (triples).
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..
Well-Formedness Criteria
Well-formedness criteria define the minimum acceptable view content based on the subject statements (triples). These criteria are not yet represented within the model of TRAK. Please refer to the CVp-06 Concept Sequence definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.
Presentation Methods
The CV-06 Concept Sequence architecture view may use any of following means to the statements (triples):
- activity diagram
- collaboration diagram
- sequence diagram
Note that a textual presentation is acceptable for any TRAK architecture view.
Comments
Neighbouring Architecture Views
The CV-06 Concept Sequence architecture view content may overlap that of the following neighbouring architecture views:
- CV-03 Concept Item Exchange
- CV-05 Concept Activity
- MV-02 Architecture Description Design Record
- MV-03 Requirements and Standards
- MV-04 Assurance
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.