Engineered capability extends both endeavor and capability and is a base class for issue, feature, and release. I.e. it is something that might be required by issues to start working on them and that something takes time, effort, and money to complete.

For example an issue “Build XYZ visualization” for module B may require “Visualizations” feature of product A.

Engineered capability can be aligned to aims. E.g. release 1.2.0 may be aligned to meet goals of a particular persona or annual or quarterly objective of an organization.




Engineered capability can be planned for zero or more releases.

Type Release
Cardinality 0..*
Changeable true
Derived false
Opposite capabilities