Issue 18845: Why does a user need to build an SOV-3? (updm-2-0-rtf)
Source: MITRE (Dr. Fatma Dandashi, dandashi(at)mitre.org)
Nature: 
Severity: 
Summary: Why does a user need to build an SOV-3? The relationship from services to capabilities should be transitive. Once a user establishes traceability from operational activity to capability and from ServiceFunction to Operational Activity, then there is already a trace from owning service (service that owns that ServiceFunction) to a capability and SOV should b au-populated. Further, a service(Interface) should map to a node and not to an OperationalActivity or to SystemFunction.  This change is to be discussed with respective requirements representatives. 


Resolution: 
Revised Text: 
Actions taken:
July 31, 2013: received issue
Discussion: 

End of Annotations:=====
s is issue # 18845   From: "Dandashi, Fatma" <dandashi@mitre.org>

Why does a user need to build an SOV-3? 

Why does a user need to build an SOV-3? The relationship from services to capabilities should be transitive. Once a user establishes traceability from operational activity to capability and from ServiceFunction to Operational Activity, then there is already a trace from owning service (service that owns that ServiceFunction) to a capability and SOV should b au-populated. Further, a service(Interface) should map to a node and not to an OperationalActivity or to SystemFunction.  This change is to be discussed with respective requirements representatives.