BACM 1.1b1 RTF Avatar
  1. OMG Issue

BACM11 — Consider adding CapabilitySpecialization to the metamodel

  • Key: BACM11-63
  • Status: open  
  • Source: Thematix Partners LLC ( Mr. James Rhyne)
  • Summary:

    Capabilities are not allowed to be specialized because architects tended to misuse specialization when creating capability maps by decomposing capabilities. The problem occurs when specializing and then decomposing, resulting in different decomposition hierarchies for each specialization and duplication of capabilities.
    UAF and VDML both have a concept of capability that is more like a capability specialization than a capability because it recognizes that capabilities may be variants. The BACM does not have a single concept that aligns with the concept of capability in UAF and VDML. Instead, the BACM splits this concept into CapabilityBehavior and CapabilityImplementation.

  • Reported: BACM 1.0b2 — Thu, 18 Jul 2024 21:20 GMT
  • Updated: Thu, 18 Jul 2024 21:30 GMT