View TRAK:CVp-04 Concept Activity to Capability Mapping Viewpoint
Title
CVp-04 - Concept Activity to Capability Mapping Viewpoint
Version
5
Date
3rd February 2011
Overview
The CVp-04 Concept Activity to Capability Mapping Viewpoint is part of the TRAK Concept Perspective and one of the 21 TRAK Architecture Viewpoints.
It provides a trace from the Concept Activity to the Enterprise capability(ies) supported by that concept activit(ies).
Stakeholders Addressed
- Owner of Enterprise
- Maintainer of Enterprise
- Developer of Enterprise
- Builder of Enterprise
- Developer of Concept
- Owner of Concept
Concerns Addressed
How/are concept activities sufficient to deliver capability?
Covered by TRAK IPR and licenses
Description
Describes how the concept activities relate to the enterprise capabilities needed.
This enables the following problems to be identified:
- capabilities required by an enterprise that aren’t supported by any concept activity. This might lead to nothing being developed to deliver the capability.
- concept activities that aren’t needed.
Covered by TRAK IPR and licenses
Mandatory Metamodel Tuples
The following tuples are mandatory:
- Node conducts Concept Activity
- Concept Activity supports Capability
- Enterprise requires Capability
Optional Metamodel Tuples
Context - Rationale:
Enterprise Goal requires Capability Universal:
- Concern about Architecture Description Element
- Document traces to Architecture Description Element
- Requirement traces to Architecture Description Element
- Standard governs Architecture Description Element
If any of these optional metamodel elements are added then the appropriate TRAK Master Architecture View must be provided.
Covered by TRAK IPR and licenses
Well-Formedness
A CV-04 view shall contain:
- at least one Node (the subject of the view)
- every Node must be connected to at least one Concept Activity
- at least one Enterprise
- every Enterprise must be connected to at least one Capability
- every Concept Activity must be connected to at least one Capability, if not then a Concern *
- every Capability must be connected to at least one Concept Activity, if not then a Concern *
* Note: The purpose of the viewpoint is to identify unmapped capabilities and unmatched concept activities. Unmapped items are to be flagged by connecting to a Concern identifying this concern and reported on in the MV-02. As items are mapped on this view they are disconnected from the Concern.
Covered by TRAK IPR and licenses
Presentation
- Table or Matrix (row/column headings = Node, Concept Activity, Capability, Enterprise, Description)
- Block diagram (Node, Concept Activity, Enterprise, Capability = block, TRAK relationship = line with direction indicator)
Table/matrix form:
CV-04 Concept Activity to Capability Mapping -Table or Matrix Form Node Concept Activity Capability Enterprise Description #N99 CA03 (missing) (missing) Concern - is this concept activity needed? #N99 CA05 C06 E45 mmm sss jj #N99 CA013 C06 E45 mmm sss jj #N99 CA05 C21 E45 mmm sss jj (missing) (missing) C27 E45 Concern - no concept activity identified to support this capability.
Note: The 1 unmapped Concept Activity and 1 unmapped Capability are identified by (missing)
and each flagged by a Concern.
Block diagram form:
Full size:File:CVp-04 examplePresentation blocks.gif
Note: Any unmapped concept activity or capability as far as the subject pair (particular Node and Enterprise) being described represents a concern.
Covered by TRAK IPR and licenses
Examples
Views Needed to Construct
Covered by TRAK IPR and licenses
Consistency Rules
- Node must appear in CV-01 (specified by CVp-01 Concept Need Viewpoint)
- Concept Activity must appear in CV-05 (specified by CVp-05 Concept Activity Viewpoint)
- any Standard must appear on MV-03 (specified by MVp-03 Requirements & Standards Viewpoint)
Covered by TRAK IPR and licenses
Configuration History
The TRAK Viewpoints project on Sourceforge (trakviewpoints.sourceforge.net) maintains a version-controlled repository. The change record is at http://trakviewpoints.svn.sourceforge.net/viewvc/trakviewpoints/trunk/?view=log
Comments
As a mapping view, the CV-04 is not a master architecture view.
Other Frameworks
- DNDAF has views that describe the enterprise and capabilities and therefore no need for this mapping view
- DODAF::CV-6 Capability to Operational Activities Mapping Model
- MODAF::StV-6 Operational Activity to Capability Mapping View
- NAF::NCV-6 Capability to Operational Activities Mapping Subview
Comments
References
- TRAK Enterprise Architecture Framework Viewpoints. http://trakviewpoints.sourceforge.net
Category:Framework -> Viewpoint
Category:Framework -> Specification
Category:Operational
Clip to Evernote
Bookmark this on Delicious
