-
Key: UPDM-213
-
Legacy Issue Number: 11744
-
Status: open
-
Source: International Business Machines ( Mr. Fred Mervine)
-
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() -
Reported: UPDM 1.0b1 — Wed, 5 Dec 2007 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:59 GMT