BACM11 — Resolve ordering semantics for Outcome connections

The BACM uses Outcomes to connect AbstractCapabilities, AbstractProcesses and (with BACM11-22) ValueStreamStages. These Outcomes may imply ordering relationships between these activity meta-concepts. In addition, architects often want to define high level processes and workflows to associate with ValueStreams. Should the BACM define an ordering semantic and provide guidance on how to use it? What would the ordering semantic look like.

Define value stream stage dependency

Define value stream stage dependency based on a dependency relationship defined by an outcome that is the exit criteria of one stage being the input criteria for a different stage. Extend this relationship transitively to include the entire value stream as dependency completeness.
Note that this resolution adds no new classes or associations to the metamodel. It provides an interpretation of the existing metamodel that facilitates model analysis and provides methodology for checking the validity of value streams.