View TRAK:Architecture Description
Version & Date
5th September 2015
Configuration History
See change record for the TRAK metamodel at https://trakmetamodel.svn.sourceforge.net/viewvc/trakmetamodel/trunk/?view=log
Definition
One of the elements within the the TRAK metamodel and part of the Management Perspective.
IEE1471/ ISO/IEC 42010: An architectural description is a model of the architecture; its purpose is to answer all identified stakeholders questions about all identified architecture-related concerns for the system of interest;
The collection of architecture products that describes a system of interest.
Covered by TRAK IPR and licenses
Tests For
Tests Against
Attributes
- approval authority
- architect
- assumptions
- constraints
- decisions
- purpose
- recommendations
- summary of findings
- tools used
- views
Inherited attributes:
Covered by TRAK IPR and licenses
Implementation of TRAK Attribute Names and Values
The implementation of TRAK attributes in a tool is controlled by ‘TRAK. Implementation. Architecture Description Elements’ with respect to the case, spelling of attributes and format of values. See References section below.
Relationships
Architecture Description participates in the following relationships:
- Architecture Description has part Architecture View
- Architecture Description has part Architecture Description Tuple
- Architecture Description is a Architecture Product
- Architecture Description is a Document
Inherited relationships:
+ from Document
- Document has part Architecture Description
- Architecture Description issued by Organisation
- Document traces to Architecture Description
- Architecture Description has part Document
+ from Architecture Description Element:
- Claim about Architecture Description
- Concern about Architecture Description
- Contract
governs Architecture Description - Requirement governs Architecture Description
- Standard governs Architecture Description
- Architecture Description satisfies Contract
- Architecture Description satisfies Requirement
- Architecture Description satisfies Standard
- Architecture Description traces to Argument
- Architecture Description traces to Document
- Architecture Description traces to Requirement
Covered by TRAK IPR and licenses
Configuration History
See change record for the TRAK metamodel at https://trakmetamodel.svn.sourceforge.net/viewvc/trakmetamodel/trunk/?view=log
Master Architecture View
Any Architecture Description used within an architecture description(!!) of the system-of-interest must appear on a MV-02 Architecture Description Design Record View for the architecture description.
The MV-02 is the Master Architecture View for Architecture Description.
Covered by TRAK IPR and licenses
Comments
The purists will not like it (self-references / infinite recursion) but it provides a useful means for describing the scope/results for an architectural task using the MV-02 Architecture Design Record.
Covered by TRAK IPR and licenses
Other Frameworks
References
- TRAK. Implementation. Architecture Description Elements https://sf.net/projects/trak/files/Implement TRAK/
- TRAK Enterprise Architecture Framework Metamodel. https://sf.net/p/trakmetamodel
Category:Metamodel -> Stereotype