TRAK
Enterprise Architecture ViewpointsWhat is an Architecture Viewpoint?
In accordance with ISO/IEC/IEEE 42010, the International Standard for Architecture Description a viewpoint is a specification for the construction and interpretation of an architecture view and specifies:-
- the stakeholder concerns that the view is intended to address - this helps prevent spaghetti where there are so many different elements and relationships that it isn't onbvious what the purpose of the view actually is
- the notation and types of model used
- consistency rules within the architecture description as a whole (because any element may appear in many other views)
In the formal language of the standard an architecture viewpoint is a work product establishing the conventions for the construction, interpretation and use of architecture views to frame specific system concerns
.ISO/IEC/IEEE 42010:2011
Important - Terminology: This is a precise and defined use of the term (architecture) 'viewpoint' - it does not therefore refer to a collection of views or a perspective from which the architecture description is viewed. An architecture viewpoint is something the meets the requirements of ISO/IEC/IEEE 42010.
An architecture viewpoint is a specification - it does not represent a direction from which one is viewing the system of interest. Similarly an architecture view should conform with its governing architecture viewpoint - an architecture view is not an instance of the architecture viewpoint nor a schema or template.
Further information on ISO/IEC/IEEE 42010 is available at:-
- iso-architecture.org - Conceptual Model of Architecture Description
- Wikipedia - ISO/IEC 42010
TRAK Architecture Viewpoint Structure
Each TRAK Viewpoint has a standardised structure which is designed to meet the requirements of ISO/IEC/IEEE 42010.
The conformance of TRAK as an architecture framework and any TRAK-conforming architecture description against ISO/IEC/IEEE 42010:2011 is described using a TRAK architecture description (which uses MVp-02 Architecture Description Design Record, MVp-03 Requirements and Standards and MVp-04 Assurance TRAK architecture views).
Each TRAK architecture viewpoint has the following sections:
- architecture viewpoint configuration
- date created
- date modified
- version
- description
- stakeholders, stakeholder concerns and anti-concerns
- subject tuples
- Statements that directly describe the subject and the concerns framed by the architecture viewpoint. The subject matter is determined by the architecture viewpoint concerns. Architecture view content is specified using triples.
- optional tuples
- Additional statements that me be used to add additional context (but which isn't the direct subject of the architecture view). Architecture view content is specified using triples.
- well-formedness criteria
- The minimum acceptable architecture view content - formed from the subject statements.
- presentation methods
- Acceptable methods of presenting the architecture view content.
- views needed to construct
- A statement or tuple has usually to be first created on an originating architecture view before it can then be used in other architecture views. This creates dependencies in terms of the order of creating architecture views.
- consistency rules
- Rules designed to improve / maintain consistency across the architecture description. These may also include consistency of logic or temporal consistency e.g. can't characterise an interface that hasn't yet been identified, can't assert that a claim is proven unless there is both supporting arguments and supporting claims.
- comments
Architecture Viewpoint List
The TRAK architecture viewpoints are listed separately. A summary of all of the concerns framed by the architecture viewpoints is also provided separately. Each of these summary pages provides the links to each of the architecture viewpoint definitions.