BACM11 — Abstract Process missing from Diagram 7.3.7.3 and following text

This diagram represents the capabilities that would be required to carry out a means or initiative. Often, these capabilities are not a part of the organization and must be added, e.g. by contract. The issue is that abstract process should be included because it represents a perspective that abstractly represents the operations of the business that is distinct from the capability perspective but at the same level of abstraction.

Add uses_0 and uses_1 indicating use of AbstractOperatingModel concepts by Means and Initiative

Remove the require_0 and require_1 class associations from the model.
Remove the implements_3 class association from the model.
Delete all classes from the diagram.
Delete the StrategyNeeds diagram (7.3.7.3).
In the Strategy diagram (7.3.7.2):
rename impacts_0 and impacts_1 as baseline_4 and baseline_5 respectively.
add uses_0 <<class>> association from Means to AbstractOperatingModel
add uses_1 <<class>> association from Initiative to AbstractOperatingModel

The result of these changes is that the execution dependence of Means and Initiatives on concepts of the AbstractOperatingModel is represented by the uses_0 and uses_1 associations. Consequently, the StrategyNeeds diagram (7.3.7.3) is redundant and is deleted from the model.

The renaming of impacts_0 and impacts_1 creates a uniform interpretation of baseline WRT Ends and Change such that the Ends and Change describe desired changes to the AbstractOperatingModel and AbstractValueModel elements targeted by baseline.

Note that the same AbstractOperatingModel concept may be targeted by both baseline and uses, meaning that the concept is used by the Means/Initiative and must be changed to be successfully used.