UPDM — Fig15 - Project whole and part and ownedMilestones

Summary Fig15 - Project whole and part and ownedMilestones. A whole-part relationship is shown on Project, but this doesn't seem to be stereotyped as one of the constraints used in the documentation. Does this mean it just becomes a tagged value ? Same goes for ownedMilestones ? Suggest that (at least for the whole-part) whatever UML structure is used for instances is used - that way projects structures can also be presented as instance composite diagrams (not sure what the correct UML term for this is, but you know what I mean - instances shown within instances to represent structure). This would help with producing more UML compliant AV-1s.
Diagram AcV
Document Issue UPDM (OMG Beta) Jan 2009

Priority High
Source Ian BaileyModel Futuresian@modelfutures.com

Resolution: specifies the whole/part relationship between Project and ProjectMilestone (i.e. there should be one Association between them).Whole/part relationships don't exist for ActualProjects, as UML doesn't have support for Instances composed (the structured is supposed to be defined by the instantiated class model). There is also no such thing as an Instance Composite Diagram in UML - though it's an idea that various people have had.FURTHER DISCUSSION REQUIRED WITH IAN

[UPDM_00204] specifies the whole/part relationship between Project and ProjectMilestone (i.e. there should be one Association between them).
Whole/part relationships don't exist for ActualProjects, as UML doesn't have support for Instances composed (the structured is supposed to be defined by the instantiated class model). There is also no such thing as an Instance Composite Diagram in UML - though it's an idea that various people have had.
The sample problem has been updated to show decomposition of projects.