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 30 April 2025.
| Perspective | Viewpoint | View ID | Version | Modified |
| Management | MVp-01 | MV-01 | 9 | 2025-04-30 |
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
- examples
- views needed to construct
- consistency rules
- 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 and theory for the allowed content of an architecture view is explained separately.
The allowed MV-01 architecture view content is split into:-
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 is 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
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 MVp-01 Architecture Description Dictionary architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (30 April 2025).
Presentation Methods
The MV-01 Architecture Description Dictionary architecture view may use any of following means to represent the statements (triples):
- Table
- textual representation of triples e.g. Turtle / RDF
Note that a textual presentation is acceptable for any TRAK architecture view.
Examples
# example TRAK MV-01 Architecture Description Dictionary architecture view
# Turtle (RDF) -described vocabularies
@prefix trak: <https://purl.org/trak/elements/#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ad: <http://ad_base_uri#> .
@prefix thirdparty_vocab: <https://doi.org/10.1093/OED/> .
# describe local AD element, no third party reference
ad:ade001 a trak:Software ;
trak:AD_exchange_element_owning_ID "ADE001" ;
trak:name "AutoBot 3000"@en ;
trak:description "Automated and auto-sensing graph data decluttering application."@en .
# describe local AD element, third party equivalent
ad:ade002 a trak:Physical ;
trak:AD_exchange_element_owning_ID "ADE002" ;
trak:name "Bonnet"@en ;
trak:description "A hinged hood covering the engine at the front of a motor vehicle."@en ;
trak:is_equivalent_to <https://doi.org/10.1093/OED/6728972533> .
# describe 3rd party vocabulary elements - URI is identifier
<https://doi.org/10.1093/OED/6728972533> ;
trak:name "Hood"@en .
Turtle (RDF) Example MV-01 Architecture Description Dictionary Architecture View
An example of a Turtle (RDF) description of the definition of local architecture description elements. Note the use of 'is equivalent to' to define the meaning with relationship to an external element described in a published third party ontology description.
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. 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 MVp-01 Architecture Description Dictionary architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (30 April 2025).
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 MVp-01 Architecture Description Dictionary architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (30 April 2025).
Comments
The MV-01 Architecture Description Dictionary architecture view is not the master source (origin) for any node elements.
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
The 3rd party described-element may be a textual description in a vocabulary or dictionary. It may be an element described using OWL or RDF in an ontology description. Typically where a formal Ontology Description Language such as the OWL, RDF, SKOS etc are used to describe an ontology element there will be restricted set of statements that are permitted as specified by the defining standard for the particular ODL. Note that ontology is itself conceptual – the ontology exists whether it is described or not.
The OED defines a vocabulary as:
1.a. A collection or list of words with brief explanations, definitions, or translations of their meanings, either in the form of a stand-alone list or book, or (now more usually) as part of an elementary grammar or reader (reader n. 6), esp. one intended for learners of a foreign language; a wordlist."vocabulary (n.), sense 1.a," December 2024, https://doi.org/10.1093/OED/5059381291Vocabularies are usually arranged either alphabetically or according to subject headings.
In later use vocabulary tends to refer to a list of a restricted set of words compiled for a particular purpose, and so is typically distinguished in meaning from dictionary, although in earlier use the two terms were often used interchangeably (see e.g. quot. 1707). Where such a list is given in a linguistic study, subject-specific text, or in a reader for language learners, glossary is a common alternative term
The OED defines an ontology as:
2. Logic. Chiefly with reference to the work of Stanislaw Leśniewski (1886–1939): a system similar in scope to modern predicate logic, which attempts to interpret quantifiers without assuming that anything exists beyond written expressions."ontology (n.), sense 2," June 2024, https://doi.org/10.1093/OED/175633908
It therefore seems that what is commonly referred to as an 'ontology' is more accurately a 'vocabulary' – which incorporates the description property within its definition.
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..
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.