TRAK Architecture ViewpointsCVp-01 Concept Need
This page reproduces part of the CVp-01 Concept Need 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-01 Concept Need architecture viewpoint is one of 24 architecture viewpoints defined in TRAK00001. TRAK. Architecture Framework. Viewpoints - current release is dated 10 July 2024.
| Perspective | Viewpoint | View ID | Version | Modified |
| Concept | CVp-01 | CV-01 | 11 | 2019-08-20 |
Summary
The TRAK CVp-01 Concept Need architecture viewpoint defines the requirements for the TRAK CV-01 Concept Need 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-01 Concept Need 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 CVp-01 Concept Need 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-01 Concept Need Architecture Viewpoint
The TRAK CVp-01 Concept Need architecture viewpoint addresses the following concerns:
- What are the concept needs?
Description
Describes the concept in terms of the set of abstract things or 'stuff' (nodes) and how they depend on each other by way of conceptual structure and need. The CV-01 provides a way to describe that 'A needs B' at a high level that is free from any idea of solution. The response to a need is an exchange of one or more items which is defined by the CVp-03.
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Need for Node' that form short statements about the thing(s) being described.
'Need for Node' is a Statement or Assertion in a CV-01 Architecture View
The rationale and theory for the allowed content of an architecture view is explained separately.
Subject Statements (Triples)
These are statements (triples) that describe the subject of the CV-01 Concept Need architecture view. Specifically these statements address the concerns for this CVp-01 Concept Need architecture viewpoint. These form the basis for the well-formedness section of the CVp-01 Concept Need architecture viewpoint.
There are 3 possible subject statements in total which include 2 metamodel elements ( Need and Node ).
Return to the top of the Concept Need page.
- Need for Node
- Node has Need
- Node has part Node
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..
Optional Statements (Triples)
These optional statements (triples) for the CV-01 Concept Need 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 ...
'Node satisfies Standard' - an optional statement or assertion for the CV-01 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 32 possible statements which may be used to augment the CV-01 Concept Need architecture view, split into 6 groups:
- Context - Realisation by Solution
- Universal - Applicable Requirements
- Universal - Assurance
- Universal - Concern Identified
- Universal - Requirement Compliance
- Universal - Traceability or Reference
Return to the top of the Concept Need page.
Context - Realisation by Solution
6 additional context statements:
- Job realises Node
- Organisation realises Node
- Physical realises Node
- Role realises Node
- Software realises Node
- System realises Node
Return to the top of the CV-01 optional statements (triples).
Universal - Applicable Requirements
6 additional context statements:
- Contract governs Need
- Contract governs Node
- Requirement governs Need
- Requirement governs Node
- Standard governs Need
- Standard governs Node
Return to the top of the CV-01 optional statements (triples).
Universal - Assurance
4 additional context statements:
- Claim about Need
- Claim about Node
- Need traces to Argument
- Node traces to Argument
Return to the top of the CV-01 optional statements (triples).
Universal - Concern Identified
2 additional context statements:
- Concern about Need
- Concern about Node
Return to the top of the CV-01 optional statements (triples).
Universal - Requirement Compliance
6 additional context statements:
- 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-01 optional statements (triples).
Universal - Traceability or Reference
8 additional context statements:
- 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-01 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 CVp-01 Concept Need architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (10 July 2024).
Presentation Methods
The CV-01 Concept Need architecture view may use any of following means to the statements (triples):
- block diagram (Node = block, Need = line with text label and direction indicator)
- matrix (if only showing need relationships)
- N-squared diagram (Nodes on diagonal, intersections marked to represent direction of Need)
Note that a textual presentation is acceptable for any TRAK architecture view.
Examples
Example CV-01 Concept Need Architecture View - The TRAK Ecosphere
A UML example of a TRAK CV-01 Concept Need architecture view describing the concepts involved with the definition and use of the TRAK architecture framework.
Produced using (Sparx Systems Enterprise Architect UML modelling tool in conjunction with the MDG for TRAK plugin (https://sf.net/p/mdgfortrak.)
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. A Concept Activity described using a CV-05 architecture view needs a Node described in a CV-01 architecture view. 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 CVp-01 Concept Need architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (10 July 2024).
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 CVp-01 Concept Need architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (10 July 2024).
Comments
The CV-01 Concept Need 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-01 Concept Need architecture view content may overlap that of the following neighbouring architecture views:
- CV-03 Concept Item Exchange
- CV-05 Concept Activity
- MV-01 Architecture Description Dictionary
- MV-02 Architecture Description Design Record
- MV-03 Requirements and Standards
- MV-04 Assurance
- SV-01 Solution Structure
- SV-02 Solution Resource Interaction
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.