TRAK Architecture ViewpointsCVp-03 Concept Item Exchange
This page reproduces part of the CVp-03 Concept Item Exchange 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-03 Concept Item Exchange 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-03 | CV-03 | 8 | 2017-12-08 |
Summary
The TRAK CVp-03 Concept Item Exchange architecture viewpoint defines the requirements for the TRAK CV-03 Concept Item Exchange 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-03 Concept Item Exchange 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-03 Concept Item Exchange 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-03 Concept Item Exchange Architecture Viewpoint
The TRAK CVp-03 Concept Item Exchange architecture viewpoint addresses the following concerns:
- Have the items exchanged by concept nodes been identified?
- What is required to satisfy the concept needs?
Description
Describes what is exchanged to meet the solution-free needs identified. It responds to the needs identified in the CVp-01.
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Node has Need' that form short statements about the thing(s) being described.
'Node has Need' is a Statement or Assertion in a CV-03 Architecture View
The rationale for this is explained separately.
Subject Statements (Triples)
These are statements (triples) that describe the subject of the CV-03 Concept Item Exchange architecture view. Specifically these statements address the concerns for this CVp-03 Concept Item Exchange architecture viewpoint. These form the basis for the well-formedness section of the CVp-03 Concept Item Exchange architecture viewpoint.
There are 6 possible subject statements in total which include 4 metamodel elements ( Item , Item Exchange , Need and Node ).
Return to the top of the Concept Item Exchange page.
- Item Exchange carries Item
- Item Exchange from Node
- Item Exchange to Node
- Item has part Item
- Need requires Item Exchange
- Node has Need
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..
Optional Statements (Triples)
These optional statements (triples) for the CV-03 Concept Item Exchange 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 ...
'Concern about Need' - an optional statement or assertion for the CV-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 55 possible statements which may be used to augment the CV-03 Concept Item Exchange architecture view, split into 6 groups:
- Context - Concept Structure
- Universal - Applicable Requirements
- Universal - Assurance
- Universal - Concern Identified
- Universal - Requirement Compliance
- Universal - Traceability or Reference
Return to the top of the Concept Item Exchange page.
Context - Concept Structure
3 additional context statements:
- Need for Node
- Node has Need
- Node has part Node
Return to the top of the CV-03 optional statements (triples).
Universal - Applicable Requirements
12 additional context statements:
- Contract governs Item
- Contract governs Item Exchange
- Contract governs Need
- Contract governs Node
- Requirement governs Item
- Requirement governs Item Exchange
- Requirement governs Need
- Requirement governs Node
- Standard governs Item
- Standard governs Item Exchange
- Standard governs Need
- Standard governs Node
Return to the top of the CV-03 optional statements (triples).
Universal - Assurance
8 additional context statements:
- Claim about Item
- Claim about Item Exchange
- Claim about Need
- Claim about Node
- Item Exchange traces to Argument
- Item traces to Argument
- Need traces to Argument
- Node traces to Argument
Return to the top of the CV-03 optional statements (triples).
Universal - Concern Identified
4 additional context statements:
- Concern about Item
- Concern about Item Exchange
- Concern about Need
- Concern about Node
Return to the top of the CV-03 optional statements (triples).
Universal - Requirement Compliance
12 additional context statements:
- Item Exchange satisfies Contract
- Item Exchange satisfies Requirement
- Item Exchange satisfies Standard
- Item satisfies Contract
- Item satisfies Requirement
- Item satisfies Standard
- Need satisfies Contract
- Need satisfies Requirement
- Need satisfies Standard
- Node satisfies Contract
- Node satisfies Requirement
- Node satisfies Standard
Return to the top of the CV-03 optional statements (triples).
Universal - Traceability or Reference
16 additional context statements:
- 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
- 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
Return to the top of the CV-03 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-03 Concept Item Exchange definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.
Presentation Methods
The CV-03 Concept Item Exchange architecture view may use any of following means to the statements (triples):
- Block diagram (Node = block, Item Exchange = line with direction indicator, Item = text label, Need = line with direction indicator). The item exchanges are typed e.g. ‘IE1=Energy, IE2=Data’. If this cannot be attached to the resource interaction(s) on a Block Diagram an accompanying list of typed item exchanges would be needed.
- Matrix
- N-squared diagram (Nodes on diagonal, intersections marked with Item(s) to represent direction of Item Exchanges and Items being exchanged )
Note that a textual presentation is acceptable for any TRAK architecture view.
Comments
The CV-03 Concept Item Exchange architecture view is the master source (origin) on which you first create the following elements or statements:
A Node (see TRAK Metamodel document) is a solution-free "thing" and provides a way of very coarsely describing a concept.
Although solution-free if there are real world restrictions or "givens" that the concept has to work with these may be represented as a single thing. No detail or technology!
Neighbouring Architecture Views
The CV-03 Concept Item Exchange architecture view content may overlap that of the following neighbouring architecture views:
- CV-01 Concept Need
- CV-06 Concept Sequence
- MV-01 Architecture Description Dictionary
- 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..