View TRAK:Concept Perspective
The TRAK Concept Perspective covers the logical view of what is needed.
It covers the connection of nodes, for example a service control centre, to other nodes with no recognition of how this might be realised either by organisation or technology.
It also implies no particular part of a life cycle - it covers everything from concept to disposal (‘lust to dust’!).
The Concept Perspective is often used for describing or defining the user requirements for the system of interest. Having a description of the concept does not imply that there are any solutions.
The TRAK Concept Perspective has the following 5 viewpoints (each specifying one view):
- CVp-01 Concept Need Viewpoint
- CVp-03 Concept Item Exchange Viewpoint
- CVp-04 Concept Activity to Capability Mapping Viewpoint
- CVp-05 Concept Activity Viewpoint
- CVp-06 Concept Sequence Viewpoint
The architectural description in the TRAK Concept Perspective is usually a response to the capabilities that are required by the Enterprise and described in the TRAK Enterprise Perspective.
Any logical problem described in the TRAK Concept Perspective may have 0 or more solutions described in the TRAK Solution Perspective.
Other Frameworks
- DNDAF::Operational View (OV)
- DODAF::Operational Viewpoint
- MODAF::Operational Viewpoint
- NAF::NATO Operational View (NOV)
References
Category:Framework -> Perspective