BACM — Review uses of "owns" and "aggregates" for consistency

The "owns" association denotes strict composition at the model instance level. Business architecture methodology disallows non-strict composition for capabilities and value stream stages and value streams, but makes no statement about other cases. Business architecture methodology also disallows specialization of capabilities, value stream stages and value streams. The metamodel needs a "does it make sense" review to determine if "owns", "agggregates" and "generalizes" are properly expressed in the model.

Revision to generally allow generalizes, owns and aggregates between BusinessElements

The EA metamodel is revised to allow generalizes, aggregates and owns associations between BusinessElement concrete subtypes, subject to the constraint that the participating instances must be of the same concrete type. This is enforced by a set of OCL 2 constraints associated with the BusinessElement.
In addition, OCL 2 constraints on Capability disallow generalizes and aggregates links between Capability instances.
In addition, OCL 2 constraints on ValueStream disallow generalizes, owns, or aggregates links between ValueStream instances.
In addition, OCL 2 constraints on ValueStreamStage disallow generalizes and aggregates links between ValueStreamStage instances.
In addition, OCL 2 constraints on CustomerJourney disallow generalizes, aggregates or owns links between instances of CustomerJourney.
In addition, OCL 2 constraints on CustomerJourneyStage disallow generalizes and aggregates links between instances of CustomerJourneyStage.