UPDM 2.2 RTF Avatar
  1. OMG Issue

UPDMRTF — System and PhysicalArchitecture are siblings not descendants

  • Key: UPDMRTF-18
  • Legacy Issue Number: 18708
  • Status: open  
  • Source: Thematix Partners LLC ( Lonnie VanZandt)
  • Summary:

    As shown in Figure 8.127 for CapabilityConfiguration to PhysicalArchitecture and Figure 8.130 for PhysicalArchitecture to SystemResource and in Figure 8.178 for System to ResourceArtifact, Figure 8.132 for ResourceArtifact to PhysicalResource, Figure 8.131 for PhysicalResource to SystemResource, one can see that System and PhysicalArchitecture are sibling concepts.

    Now, FieldedCapability has this constraint: "Value for the classifier property must be stereotyped «CapabilityConfiguration» or its specializations." (see Page 172)

    The consequence of this is that a self-contained System cannot be the Classifier of a FieldedCapability. That is, a FieldedCapability cannot be an instance of a System.

    I claim that it is convenient to be able to specify that a FieldedCapability is an instance of a self-contained System. Having to model a separate CapabilityConfiguration to wrap just the System so that one can instantiate a FieldedCapability that is an instance of the System seems onerous.

    The recommended remedy is to allow a System to be a proper CapabilityConfiguration in addition to being a property of a CapabilityConfiguration.

  • Reported: UPDM 2.1 — Mon, 13 May 2013 04:00 GMT
  • Updated: Mon, 27 Mar 2017 00:28 GMT