-
Key: UPDM-224
-
Legacy Issue Number: 11755
-
Status: open
-
Source: International Business Machines ( Mr. Fred Mervine)
-
Summary:
8.4.32.6 OrganizationalResource Constraints
Project has zero or more - not 1 or more.
[1] Asserts that there is at least one Project owned by this OrganizationalResource. self.projects.getAppliedStereotype('UPDM::Project')->notEmpty()[1] Asserts that there is zero or more Projects owned by this OrganizationalResource.
Self.projects -> notEmpty() implies
self.projects.getAppliedStereotype('UPDM::Project')->notEmpty()[3] Asserts that there is an association between the OperationalNode and a SystemsNode that houses the OperationalNodes. self.getAllAttributes()
>asOrderedSet()>select(association- >notEmpty()).association->any (getAppliedStereotype('UPDM::SystemsNodeElements')> notEmpty())>notEmpty()[3] Asserts that there is an association between the OrganizationalResource and a SystemsNode that requires this resource.
self.getAllAttributes()>asOrderedSet()>select(association- >notEmpty()).association->any (getAppliedStereotype('UPDM::SystemsNodeElements')> notEmpty())>notEmpty()[3] should be deleted, this association is not a required resource.
8.4.32.7 OrganizationalResource Semantics
Use the DeployedToSystemsNode SystemsNodeElements association to indicate deployment of OrganizationalResource to a SystemsNode.
Use the OperationalCapabilityRoleResource association to indicate an OrganizationalRole played by the OrganizationalResource.
Use the OrganizationalResourceCapabilityConfiguration association to indicate inclusion in a CapabilityConfiguration
Use the DeployedToSystemsNode association to indicate deployment of OrganizationalResource to a SystemsNode.
Use the DeployedToSystemsNode association to indicate deployment of OrganizationalResource to a SystemsNode. -
Reported: UPDM 1.0b1 — Wed, 5 Dec 2007 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:59 GMT