TRAK Architecture ViewpointsMVp-01 Architecture Description Dictionary
This page reproduces part of the MVp-01 Architecture Description Dictionary 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-01 Architecture Description Dictionary 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 |
| Management | MVp-01 | MV-01 | 7 | 2023-08-25 |
Summary
The TRAK MVp-01 Architecture Description Dictionary architecture viewpoint defines the requirements for the TRAK MV-01 Architecture Description Dictionary 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-01 Architecture Description Dictionary 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 MVp-01 Architecture Description Dictionary 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-01 Architecture Description Dictionary Architecture Viewpoint
The TRAK MVp-01 Architecture Description Dictionary architecture viewpoint addresses the following concerns:
- Can the architecture description be understood in the way it was intended to be?
- Is the architecture description portable?
Description
Defines each element used in the architecture description.This is used to explain to others what each element is intended to represent and is necessary in preserving the meaning. It is also necessary if an element is to be reused correctly and consistently.
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Architecture Description Element is a Architecture Description Element' that form short statements about the thing(s) being described.
'Architecture Description Element is a Architecture Description Element' is a Statement or Assertion in a MV-01 Architecture View
The rationale for this is explained separately.
Subject Statements (Triples)
These are statements (triples) that describe the subject of the MV-01 Architecture Description Dictionary architecture view. Specifically these statements address the concerns for this MVp-01 Architecture Description Dictionary architecture viewpoint. These form the basis for the well-formedness section of the MVp-01 Architecture Description Dictionary architecture viewpoint.
These involve every metamodel element and may be added as content on any other architecture view. This is why the MV-01 Architecture Description Dictionary architecture view is part of the Management Perspective.
There are 2 possible subject statements in total which include 1 metamodel elements ( Architecture Description Element ).
Return to the top of the Architecture Description Dictionary page.
- Architecture Description Element equivalent to Architecture Description Element
- Architecture Description Element is a Architecture Description Element
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 MVp-01 Architecture Description Dictionary definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.
Presentation Methods
The MV-01 Architecture Description Dictionary architecture view may use any of following means to the statements (triples):
- Table
Note that a textual presentation is acceptable for any TRAK architecture view.
Comments
The MV-01 Architecture Description Dictionary architecture view is the master source (origin) on which you first create the following elements or statements:
- Architecture Description Element equivalent to Architecture Description Element
- Architecture Description Element is a Architecture Description Element
Easiest method of production is often a database query if the architecture modelling tool supports this. It does, however, assume that the architect has provided a description or definition for each architecture description element!
Neighbouring Architecture Views
The MV-01 Architecture Description Dictionary architecture view content may overlap that of the following neighbouring architecture views:
- CV-01 Concept Need
- CV-03 Concept Item Exchange
- CV-05 Concept Activity
- EV-01 Enterprise Goal
- EV-02 Capability Hierarchy
- MV-02 Architecture Description Design Record
- MV-03 Requirements and Standards
- MV-04 Assurance
- PrV-01 Procurement Structure
- PrV-02 Procurement Timeline
- SV-01 Solution Structure
- SV-02 Solution Resource Interaction
- SV-04 Solution Function
- SV-06 Solution Competence
- 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..