[a Concern ] TRAK deliberately doesn't require an architecture description to do this. ()
Created: 21/02/2014 08:21:48
Modified: 19/08/2015 16:24:09
Author: Nic Plum
Keywords:
Object Identifier: {5E4EFF91-6507-4a51-B008-C6D46CE819A6}
Advanced:
TRAK doesn't require an architecture description to consider and identify the specific concerns specified in 5.3 of ISO/IEC/IEEE 42010:2011:-<br/><i>- the purposes of the system;</i><br/><i>- the suitability of the architecture for achieving the system</i><br/><i><br/></i>They may be considered but it depends on the architect and purpose of the architecture description task.<br/>
Element
«Role» Builder of a TRAK Architecture Description
Role «has»
Details:
 
«Job» Chief Architect of TRAK
Job «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 1759
Details:
concern scope Architecture
Details:
concern status Open
Details:
element author Nic Plum
Details:
opened date 21/02/2014
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:
raised by organisation TRAK
Details:
Object Type Connection Direction Notes
«Document» TRAK. Compliance Matrix. Conformance Assessment - ISO/IEC/IEEE 42010:2011 Document Abstraction To  
The following concerns shall be considered and when applicable, identified in the architecture description: - the purposes of the system;... Requirement Dependency To