Legacy Issue Number: 15804
Source: agnos.ai UK Ltd ( Pete Rivett)
This came up in the MIWG testing (though that was for UML 2.2)
There seem to be several cases where the specification has defaults that are not represented in the XMI.
Examples of this are as follows:
ActivityEdge::guard : ValueSpecification [1..1] = true
ActivityEdge::weight : ValueSpecification [1..1] = 1
ObjectNode::upperBound : ValueSpecification [1..1] = *
They all seem to be ValueSpecifications so I’m sure there are others.
BTW these are all listed under Attributes of the metaclass whereas they are in fact modeled as Associations with ValueSpecification. So should they not be placed into the Associations section? Something to look at for 2.5 I guess.
Reported: UML 2.3 — Mon, 1 Nov 2010 04:00 GMT
Disposition: Resolved — UML 2.4
This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
Disposition: Closed - No Change
Updated: Fri, 6 Mar 2015 20:58 GMT