-
Key: BACM11-74
-
Status: open
-
Source: Thematix Partners LLC ( Mr. James Rhyne)
-
Summary:
The current draft provides OutcomeRelation as a template for the model level definition of relations between outcomes. Recent work on entry and exit criteria for value streams as well as capability and process flows has informally used logical relationships that instance/specialie OutcomeRelation and effectively define an Outcome that is the logical union or other Outcomes. The issue is whether the metamodel should define a set of specifically logical relations. For example include, exclude, include complement could be used to create an Outcome by conjunctive composition where the semantics of the Outcome is the union of all facts from included Outcomes, no facts from excluded Outcomes (i.e.not known whether these are true or false), complement facts from included complement Outcomes. This is just an example; specific proposal to be worked out.
-
Reported: BACM 1.0b2 — Mon, 19 Aug 2024 16:46 GMT
-
Updated: Mon, 26 Aug 2024 20:24 GMT
BACM11 — Consider adding logical relations for combining Outcomes
- Key: BACM11-74
- OMG Task Force: Business Architecture Core Metamodel (BACM) 1.1 RTF