BACM11 — Consider adding CapabilitySpecialization to the metamodel

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.

The requirement to support variability can be met in other ways

Capabilities can be associated with CapabilityBehaviors and CapabilityImplementation. Both of these elements can be specialized to account for variations in the behavior and the structure of a capability. A variant CapabilityImplementation can implements_5 a variant CapabilityBehavior, tying the behavior variation and the implementation variations together to create the equivalent to a capability variation.