Issue 11744: 8.4.22:OperationalNode (updm-ftf)
Source: International Business Machines (Mr. Fred Mervine, fred(at)mervine.us)
Nature: Uncategorized Issue
Severity: 
Summary: CapabilityRequirement_rule 
The constraint documentation is: 
[4] Asserts that this Node is required for delivery of an Operational Capability.
The OCL for the constraint is:

self.getAllAttributes()->asOrderedSet()->select(association->notEmpty()).association->any (getAppliedStereotype('UPDM::OperationalNodeCapability')-> notEmpty())->notEmpty()

There is no stereotype in UPDM called OperationalNodeCapability. I think it should be OperationalNodeCapabilityRequirement.
And if so, does the textual description make sense?
Resolution: 
Revised Text:[4] Asserts that this Node is required for delivery of a CapabilityRequirement.

self.getAllAttributes()->asOrderedSet()->select(association->notEmpty()).association->any (getAppliedStereotype('UPDM::OperationalNodeCapabilityRequirement)-> notEmpty())->notEmpty()

Resolution: 
Revised Text: 
Actions taken:
December 5, 2007: received issue
Discussion: 

End of Annotations:=====
s is issue # 11744

8.4.22:OperationalNode

CapabilityRequirement_rule 
The constraint documentation is: 
[4] Asserts that this Node is required for delivery of an Operational Capability.
The OCL for the constraint is:

self.getAllAttributes()->asOrderedSet()->select(association->notEmpty()).association->any (getAppliedStereotype('UPDM::OperationalNodeCapability')-> notEmpty())->notEmpty()

There is no stereotype in UPDM called OperationalNodeCapability. I think it should be OperationalNodeCapabilityRequirement.
And if so, does the textual description make sense?
Resolution: 
Revised Text:[4] Asserts that this Node is required for delivery of a CapabilityRequirement.

self.getAllAttributes()->asOrderedSet()->select(association->notEmpty()).association->any (getAppliedStereotype('UPDM::OperationalNodeCapabilityRequirement)-> notEmpty())->notEmpty()