-
Key: UPDM-702
-
Legacy Issue Number: 13750
-
Status: closed
-
Source: Model Futures Ltd. ( Ian Bailey)
-
Summary:
Summary Fig45 - NodeChild. This is quite hard to understand, but seems to imply that a KnownResource can be part of a NodeÂ…which it can't. This must be fixed.
Diagram OV
Document Issue UPDM (OMG Beta) Jan 2009Source Ian BaileyModel Futuresian@modelfutures.com
Resolution Limit KnownResource to only be owned by a LogicalArchitecture.This seems very limiting and doesn't support DoDAF - which seems to allow OperationalRoles (the equivalent of KnownResources) inside Nodes. Either KnownResource should be removed altogether, or they should be allowed to be owned by Nodes. Since it's required for DoDAF and seems to be quite an important concept, we will leave it as it is.To support this decision, we'll add some text to KnownResource to make it clear that in MODAF you should limit these to only being owned by LogicalArchitectures (though we should also raise an issue on MODAF to change this too).
-
Reported: UPDM 1.0b1 — Mon, 16 Mar 2009 04:00 GMT
-
Disposition: Resolved — UPDM 1.0
-
Disposition Summary:
Limit KnownResource to only be owned by a LogicalArchitecture.
This seems very limiting and doesn't support DoDAF - which seems to allow OperationalRoles (the equivalent of KnownResources) inside Nodes.
Either KnownResource should be removed altogether, or they should be allowed to be owned by Nodes. Since it's required for DoDAF and seems to be quite an important concept, we will leave it as it is.
To support this decision, we'll add some text to KnownResource to make it clear that in MODAF you should limit these to only being owned by LogicalArchitectures (though we should also raise an issue on MODAF to change this too).
Checked in MODAF 1.2 and it seems as though Known Resource can only be owned by Logical ArchitectureDocumentation updated
-
Updated: Fri, 6 Mar 2015 20:59 GMT