UAF11 — Capabilty generalization should be Use Case

Capability is currently a specialization of a SysML Block, but should be a specialization of a SysML Use Case — because the definition of a UAF Capability and a SysML Use Case both describe "what" can be achieved.

Note1: Currently NOTHING in UAF is mapped to a SysML Use Case — and as a result, a core metamodel element in SysML cannot be mapped to UAF models.

Note2: Combining different SysML metaclasses (eg: Use Cases and Blocks) in the UAFP, creates difficulties in numbering elements in a UAF model — when using tools where automatic numbering is managed at the metaclass level.

Capability cannot be made a “SysML Use Case”.

Use-Case in UML is a BehavioredClassifier.
Capabilities are “non-behavioral concepts”. They are “operational qualities” (emerging properties) belong to the “requirement side” of architecture description. Hence Capability cannot be made a “SysML Use Case”.