[a Concern ] Compliance of an Architecture Description with TRAK does not (may not) Automatically Provide Full Compliance for an Architecture Description Against ISO/IEC/IEEE 42010:2011. ()
Created: 06/08/2014 19:33:38
Modified: 29/08/2015 15:48:39
Author: Nic Plum
Keywords:
Object Identifier: {BB46B507-5472-4ee3-AF8A-84711D5DE9CA}
Advanced:
There are some requirements for architecture descriptions in ISO/IEC/IEEE 42010:2011 which are not automatically met in full by complying with TRAK. <br/>
Element
«Role» User of TRAK
Role «has»
Details:
 
«Role» Builder of a TRAK Architecture Description
Role «has»
Details:
 
«Job» Chief Architect of TRAK
Job «has»
Details:
 
«Role» Reviewer of a TRAK Architecture Description
Role «has»
Details:
 
Tag Value
AD exchange element owning ID Not Specified
Details:
AD exchange element owning organisation Eclectica Systems Ltd.
Details:
AD exchange element recipient ID Not Specified
Details:
AD exchange element recipient element name Not Specified
Details:
concern ID 2047
Details:
concern scope Architecture Framework
Details:
concern status Open
Details:
element author Nic Plum
Details:
pm codeword NONE
Details:
pm commercial NONE
Details:
pm descriptor NONE
Details:
pm marking NOT PROTECTIVELY MARKED
Details:
pm marking owner NONE
Details:
pm national caveat NONE
Details:
priority Not Specified
Details:
Object Type Connection Direction Notes
«Architecture View» MV-02 Findings - Complicated Chains of References / Traces e.g. 5.7.3 Correspondence Rules Architecture View Dependency From  
An architecture description shall record any known inconsistencies across its architecture models and its views. NOTE While consistent architecture descriptions are to be preferred, it is sometimes infeasible or impractical to resolve all inconsistencies Requirement Dependency To  
«Architecture View» MV-02 Task Findings - 5.8 Architecture Rationale Architecture View Dependency From  
«Architecture View» MV-02 Task Findings - 5.7 Architecture Relations Architecture View Dependency From  
«Architecture View» MV-02 Task Findings - 7 Architecture Viewpoints Architecture View Dependency From  
«Architecture View» MV-02 Task Findings - 5.2 Architecture Description Architecture View Dependency From  
«Architecture View» MV-02 Task Findings - 5.3 Identification of Stakeholders & Concerns Architecture View Dependency From  
«Document» TRAK. Compliance Matrix. Conformance Assessment - ISO/IEC/IEEE 42010:2011 Document Abstraction To  
«Architecture View» MV-02 Task Findings - 5.2 Architecture Description Architecture View Dependency From  
An architecture description shall identify the concerns considered fundamental to the architecture of the system-of-interest. Requirement Dependency To  
«Architecture View» MV-02 Task Findings - 6.1 Architecture Frameworks Architecture View Dependency From  
«Architecture View» MV-02 The Requirement for an Architecture Framework Consistency with the Conceptual Model in 4.2 Architecture View Dependency From  
«Architecture View» MV-02 Task Findings - 5.8 Architecture Rationale Architecture View Dependency From  
«Architecture Description» TRAK.. Architecture Description - Summary. Conformance Assessment - ISO/IEC/IEEE 42010:2011 Architecture Description Dependency From  
«Claim» A TRAK-Conforming Architecture Description may fail to identify any known inconsistencies. Claim Dependency To  
«Architecture View» MV-02 Findings - Relating to the Use of TRAK Architecture View Dependency From  
The following concerns shall be considered and when applicable, identified in the architecture description: - the purposes of the system;... Requirement Dependency To  
«Architecture View» MV-02 Findings - ISO/IEC/IEEE 42010 Conceptual Model / Figures Architecture View Dependency From  
«Architecture View» MV-02 Findings - Complicated Chains of References / Traces e.g. 5.7.3 Correspondence Rules Architecture View Dependency From  
«Architecture View» MV-04 ISO 42010 Architecture Description Reqts Not Automatically Complied with Architecture View Dependency From  
«Architecture View» MV-02 Task Findings - TRAK Content Architecture View Dependency From  
«Architecture View» MV-02 Ability to Use a Metamodel as a Model Kind Needs to be Stated Generally in ISO/IEC/IEEE 42010:2011 Architecture View Dependency From  
«Architecture View» MV-02 Task Findings - 5.3 Identification of Stakeholders & Concerns Architecture View Dependency From  
«Architecture View» MV-02 Architecture Task - Scope - TRAK-Conforming Architecture Description Architecture View Dependency From  
When recording decisions, the following should be considered:- the decision is uniquely identified; - the decision is stated; - the decision is linked to the system concerns to which it pertains; - the owner of the decision is identified; .... Requirement Dependency To  
«Architecture View» MV-02 Findings - 5.6 Architecture Models Architecture View Dependency From