UAF 1.2 RTF Avatar
  1. OMG Issue

UAF12 — CapabilityDependency: meaning of the two types of metaclasses need clarification

  • Key: UAF12-25
  • Status: closed  
  • Source: Airbus Group ( Dominique Ernadote)
  • Summary:

    Capability Dependency History:
    NAF 3.0 ==> Capability Dependency btw Capability Composition,
    NAF 3.1 ==> Move of the dependencies to the Capability metaclasses,
    UAF DMM 1.0 p20 ==> Direct link btw Capability (not part element),
    UAF DMM 1.1 p36 ==> Dependencies btw both Capabilty and CapabilityRole.
    Seems to be new compared to UAF 1.0 : only 1 link btw Capability, and no CapabilityRole metaclass.
    Definition of Capability seems now the definition of CapabilityRole.

    How CapabilityDependency and CapabilityRoleDependency are related to each other?
    Is the second one a refinement of the 1st one?
    Is there any pattern like this where both whole (Capability) and part (CapavbilityRole) are both having a similar relation?

  • Reported: UAF 1.1 — Mon, 9 Dec 2019 23:24 GMT
  • Disposition: Closed; No Change — UAF 1.2
  • Disposition Summary:

    This is how it is defined in UAF since its first release

    Capability Dependency can be drawn between types, which means that Capabilities are always dependent or between Roles, which means that Capabilities may only be dependent in the specific context. Let's say a specific EnterprisePhase. How one relates to another if both are applicable in the model is a subject to the modelling approach. UAF specification is not defining any constraints.

  • Updated: Thu, 31 Mar 2022 19:31 GMT