TRAK Architecture ViewpointsCVp-05 Concept Activity
This page reproduces part of the CVp-05 Concept Activity 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-05 Concept Activity 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-05 | CV-05 | 11 | 2024-07-10 |
Summary
The TRAK CVp-05 Concept Activity architecture viewpoint defines the requirements for the TRAK CV-05 Concept Activity 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-05 Concept Activity 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-05 Concept Activity 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-05 Concept Activity Architecture Viewpoint
The TRAK CVp-05 Concept Activity architecture viewpoint addresses the following concerns:
- What does each node need to do?
Description
Describes what the node ('thing') does. This provides a way of describing the overall concept in functional terms that are free of solution - i.e what it needs to do without the 'how'.
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Concept Activity is quantified by Metric' that form short statements about the thing(s) being described.
'Concept Activity is quantified by Metric' is a Statement or Assertion in a CV-05 Architecture View
The rationale for this is explained separately.
Subject Statements (Triples)
These are statements (triples) that describe the subject of the CV-05 Concept Activity architecture view. Specifically these statements address the concerns for this CVp-05 Concept Activity architecture viewpoint. These form the basis for the well-formedness section of the CVp-05 Concept Activity architecture viewpoint.
There are 4 possible subject statements in total which include 3 metamodel elements ( Concept Activity , Metric and Node ).
Return to the top of the Concept Activity page.
- Concept Activity has part Concept Activity
- Concept Activity is quantified by Metric
- Metric has part Metric
- Node conducts Concept Activity
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..
Optional Statements (Triples)
These optional statements (triples) for the CV-05 Concept Activity 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 ...
'Requirement governs Metric' - an optional statement or assertion for the CV-05 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 42 possible statements which may be used to augment the CV-05 Concept Activity 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 Activity page.
Context
3 additional context statements:
- Concept Activity supports Capability
- Function realises Concept Activity
- Node has part Node
Return to the top of the CV-05 optional statements (triples).
Universal - Applicable Requirements
9 additional context statements:
- Contract governs Concept Activity
- Contract governs Metric
- Contract governs Node
- Requirement governs Concept Activity
- Requirement governs Metric
- Requirement governs Node
- Standard governs Concept Activity
- Standard governs Metric
- Standard governs Node
Return to the top of the CV-05 optional statements (triples).
Universal - Assurance
6 additional context statements:
- Claim about Concept Activity
- Claim about Metric
- Claim about Node
- Concept Activity traces to Argument
- Metric traces to Argument
- Node traces to Argument
Return to the top of the CV-05 optional statements (triples).
Universal - Concern Identified
3 additional context statements:
- Concern about Concept Activity
- Concern about Metric
- Concern about Node
Return to the top of the CV-05 optional statements (triples).
Universal - Requirement Compliance
9 additional context statements:
- Concept Activity satisfies Contract
- Concept Activity satisfies Requirement
- Concept Activity satisfies Standard
- Metric satisfies Contract
- Metric satisfies Requirement
- Metric satisfies Standard
- Node satisfies Contract
- Node satisfies Requirement
- Node satisfies Standard
Return to the top of the CV-05 optional statements (triples).
Universal - Traceability or Reference
12 additional context statements:
- Concept Activity traces to Contract
- Concept Activity traces to Document
- Concept Activity traces to Requirement
- Concept Activity traces to Standard
- Metric traces to Contract
- Metric traces to Document
- Metric traces to Requirement
- Metric 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-05 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-05 Concept Activity definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.
Presentation Methods
The CV-05 Concept Activity architecture view may use any of following means to the statements (triples):
- Block diagram (Node, Concept Activity, Item = block, TRAK relationship = line with direction indicator)
Note that a textual presentation is acceptable for any TRAK architecture view.
Comments
The CV-05 Concept Activity architecture view is the master source (origin) on which you first create the following elements or statements:
- Concept Activity
- Concept Activity is quantified by Metric
If ordering of Concept Activities is a concern use a Concept Sequence View defined by the CVp-06.
Neighbouring Architecture Views
The CV-05 Concept Activity architecture view content may overlap that of the following neighbouring architecture views:
- CV-01 Concept Need
- CV-04 Concept Activity to Capability Mapping
- CV-06 Concept Sequence
- MV-01 Architecture Description Dictionary
- MV-02 Architecture Description Design Record
- MV-03 Requirements and Standards
- MV-04 Assurance
- SV-04 Solution Function
- SV-05 Solution Function to Concept Activity Mapping
- SV-06 Solution Competence
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.