View TRAK:MVp-01 Architecture Description Dictionary Viewpoint
Title
MVp-01 - Architecture Description Dictionary Viewpoint
Version
6
Date
8th December 2017
Overview
The MVp-01 - Architecture Description Dictionary Viewpoint is part of the Management Perspective and one of the 24 TRAK Architecture Viewpoints.
The MVp-01 Architecture Description Dictionary Viewpoint provides a way of defining the architecture elements used in an architecture description so that it can be understood. It is also therefore an aid to portability, exchange and re-use.
It is the specification for the TRAK::MV-01 Architecture Description Dictionary architecture view.
Stakeholders Addressed
- Owner of Architecture Task
- User of Architecture Task
- Developer of Enterprise
- Maintainer of Enterprise
- Owner of Enterprise
- Owner of Concept
- User of Concept
- Developer of Concept
- Owner of Solution
- User of Solution
- Maintainer of Solution
- Developer of Solution
- Operator of Solution
- Trainer of Solution
- Acquirer of Solution
- Disposer of Solution
Full size:File:mvp01StakeholderConcern.pdf
Note that the potential set of stakeholders for this view is large because it not only involves the enterprise, concept and solution but the architecture task and lay readers of the architecture description (users of the architecture task).
Covered by TRAK IPR and licenses
Concerns Addressed
Is the architecture portable? Can it be understood in the way it was intended to be?
Covered by TRAK IPR and licenses
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.
Covered by TRAK IPR and licenses
Declared Tuples
Not applicable.
Covered by TRAK IPR and licenses
Optional Tuples
Universal:
- Architecture Description Element satisfies Contract
- Architecture Description Element satisfies Requirement
- Architecture Description Element satisfies Standard
- Architecture Description Element traces to Argument
- Architecture Description Element traces to Document
- Claim about Architecture Description Element
- Concern about Architecture Description Element
- Contract governs Architecture Description Element
- Document traces to Architecture Description Element
- Requirement traces to Architecture Description Element
- Requirement governs Architecture Description Element
- Standard governs Architecture Description Element
Covered by TRAK IPR and licenses
If any of these optional metamodel elements are added then the appropriate TRAK Master Architecture View must be provided.
Well-Formedness
A MV-01 view shall contain:
- every element used in the architecture description
- each element must have a unique means of identification (otherwise the description/definition can’t be tied to the element)
- a description or definition for every architecture description element
Covered by TRAK IPR and licenses
Presentation
- table
MV-01 Architecture Description Dictionary View - Table or Matrix Form Architecture Description Element Identifier Name Description / Definition #1 mmmm mmdn sjiijw iwhoi ioih #2 nnnnn kkbs gz siuygi osihoih
Covered by TRAK IPR and licenses
Views Needed to Construct
- the set of all the views within the AD (since the TRAK Bye Laws require every architecture tuple within the AD to appear on a view.
Covered by TRAK IPR and licenses
Consistency Rules
Configuration History
The TRAK Viewpoints project on Sourceforge (https://sf.net/p/trakviewpoints) maintains a version-controlled repository. The change record is at https://trakviewpoints.svn.sourceforge.net/viewvc/trakviewpoints/trunk/?view=log
Comments
Easiest method of production is often a database query if the architecture modelling tool supports this. It does, however, assume that the architect has provide a description or definition for each architecture element!
Covered by TRAK IPR and licenses
References
- TRAK Enterprise Architecture Framework Viewpoints. https://sf.net/p/trakviewpoints
Other Frameworks
See also:
- DNDAF::CV-2 Integrated Data Dictionary Subview
- DODAF::AV-2 Integrated Dictionary Model
- MODAF::AV-2 Integrated Dictionary View
- NAF::NAV-2 Integrated Dictionary Subview
Category:Framework -> Viewpoint
Category:Framework -> Specification
Category:Management
Category:Architecture Perspective -> Management