-
Key: UPDM-679
-
Legacy Issue Number: 13726
-
Status: closed
-
Source: Model Futures Ltd. ( Ian Bailey)
-
Summary:
Fig15 - Inheritance Problem. In Fig 15, MilestoneSequence is shown as a subclass of Project Sequence. This makes no sense, especially with the attribute redeclarations which would force a given MilestoneSequence to also relate two projects.
AcV
UPDM (OMG Beta) Jan 2009
Ian BaileyModel Futuresian@modelfutures.comIf we leave the inheritance between Project and ProjectMilestone in (as per MODAF) then they both can be linked up with ProjectSequences anyway. The current implementation was seen as a tightening of the constraints. However, this is a little confusing so we will remove the inheritance between Project/ProjectMilestone and ProjectSequence/MilestoneSequence.
-
Reported: UPDM 1.0b1 — Mon, 16 Mar 2009 04:00 GMT
-
Disposition: Resolved — UPDM 1.0
-
Disposition Summary:
If we leave the inheritance between Project and ProjectMilestone in (as per MODAF) then they both can be linked up with ProjectSequences anyway. The current implementation was seen as a tightening of the constraints.
However, this is a little confusing so we will remove the inheritance between Project/ProjectMilestone and ProjectSequence/MilestoneSequence. -
Updated: Fri, 6 Mar 2015 20:59 GMT