BACM12 — Need outcome to represent state during execution of value stream stages, and abstract capabilities.

In prototyping the Guild transportation reference model, it became apparent that the 1.1 metamodel does not support the notion of outcomes associated with the execution of value stream stages or abstract capabilities. For example, safety and comfort of the traveler are outcomes that have high value in the value proposition, They are continuously associated with the enroute stage of the value stream and are not appropriately characterized as exit-criteria, which are outcomes associated with the ending of the stage.
Such outcomes should be associated with capabilities such as conveyor operations to indicate that the outcome is in force throughout the exeuction of the capability.

Add statecharts-like metamodel elements

The proposal creates a new subtype of Outcome, named Region, that is associated to AbstractCapability, AbstractProcess, or ValueStreamStage by a reified relation named "during". Region aggregates AbstractCapabilities, AbstractProcesses, ValueStreamStages and Outcomes. An implementing tool must also aggregate needs/produces, inputs/outputs, or entry/exit criteria that relate the aggregated elements. The result should create in each Region, a network that describes behaviors in terms of Outcomes linked by AbstractCapabilities, AbstractProcesses or ValueStreamStages. For completeness, the Outcomes needed and produced by the AbstractCapability, AbstractProcess, or ValueStreamStage, whose behavior is being described by "during" related Regions, should also be part of the network in some of these Regions. Regions may be decomposed and the child Regions are presumed to behave independently unless they create Outcomes that are consumed in another region; such a creation/cunsumption relation implies a point of synchronization between the Regions.
The effect of these changes is to allow a lightweight statecharts model to be used to describe behaviors.