Issue 18738: MapsToCapability relationship is too Restrictive, and ActivityPartOfCapability is redundant (updm-2-0-rtf)
Source: MITRE (Dr. Fatma Dandashi, dandashi(at)mitre.org)
Nature: Enhancement
Severity: Significant
Summary: There is a constraint stated in Figure A.30 of the dtc/12-12-17 specification such that in MODAF (and therefore NAF), the MapsToCapability relationship is precluded from using OperationalActivities and is prescribed to only use StandardOperationalActivities.
This has resulted in defining another relationship in the spec called ActivityPartOfCapability for DODAF, that creeps into MODAF and NAF in vendor implementations, to allow one to associate an activity with a capability for the purposes of generating traceability diagrams and for generating NPV-2: Program to Capability Mapping (through Activity is part of project, and Activity is part of Capability). There is no need for both and it is redundant and a possible source of model inconsistencies to request the architect to define both MapsToCapability and another called ActivityPartOfCapability. Further, the MODAF constraint to use only StandardOperationalActivities when mapping to capabilities for the purposes of (MODAF policy?) can be accommodated in another manner.

Resolution: 
Revised Text: 
Actions taken:
May 29, 2013: received issue
Discussion: 

End of Annotations:=====
ssue 18738:
Name: Fatma Dandashi
Employer: Mitre Corp.
mailFrom: dandashi@mitre.org
Terms_Agreement: I agree
Specification: UPDM Profile
Section:  
FormalNumber: dtc/12-12-17
Version:  2.1
Doc_Year: 2012
Doc_Month:  December
Doc_Day:  17
Page: 218
Title: MapsToCapability relationship is too Restrictive, and ActivityPartOfCapability is redundant
Nature:   Enhancement
Severity: Significant
CODE: 
B1:   Report Issue
Remote Name:  
Remote User:
Time: 

Description:
There is a constraint stated in Figure A.30 of the dtc/12-12-17 specification such that in MODAF (and therefore NAF), the MapsToCapability relationship is precluded from using OperationalActivities and is prescribed to only use StandardOperationalActivities.
This has resulted in defining another relationship in the spec called ActivityPartOfCapability for DODAF, that creeps into MODAF and NAF in vendor implementations, to allow one to associate an activity with a capability for the purposes of generating traceability diagrams and for generating NPV-2: Program to Capability Mapping (through Activity is part of project, and Activity is part of Capability). There is no need for both and it is redundant and a possible source of model inconsistencies to request the architect to define both MapsToCapability and another called ActivityPartOfCapability. Further, the MODAF constraint to use only StandardOperationalActivities when mapping to capabilities for the purposes of (MODAF policy?) can be accommodated in another manner.