Source: Cognitive Medical Systems ( Thomas Beale)
It is not clear why a BKPMN package would need 'Effect' elements - are they meant to document post-conditions of the execution of a BPMN plan? If so, they should be built into the plan definition, not into the containing package. A containing package could have more than one plan...
Description says: An Effect is some change to the environment or data that may occur when the behaviors of BPM+ Knowledge Package is performed. The bold part implies that a change in pretty much anything can be an 'effect'. Possibly something like 'change to a state variable within the case (entity or system) on which a workflow is executing' might be better.
Attributes like eventRef, impactKindRef etc would seem to be replicating what are likely to be goals or post-conditions stated within BPMN or CMMN plans contained within a BKPMN package. Is this the intention? If multiple plans are grouped together in one BKPMN package, is the set of events/milestones, impacts etc obtained by summing all such elements from the constituent plans?
Reported: BKPMN 1.0a1 — Sun, 24 Apr 2022 15:58 GMT
Updated: Mon, 25 Apr 2022 13:33 GMT
BKPMN — Effect semantics unclear
- Key: BKPMN-7
- OMG Task Force: BPM+ Knowledge Package Model and Notation (BKPMN) 1.0 FTF