BPDMF2 — Section: Happening and Change

Constraints on part disjointness. Constraints on part disjointness should be expressed in OCL. For example, abort and finish can't both have values on the same M0 execution.

Resolution:
The constraint could be expressed with disjointness between M1 event classes, but Abstraction does not support disjointness, and UML disjointness requires an M1 Behavior Event supertype.
Use OCL constraints on the M1 event parts.

Revised Text:
Revised Instance Revised Text
Behavior Occurrence Section 6.5.2.47 (Instance: Universal Behavior, renamed to Behavior Occurrence in resolution to Issue 12205) of document DCT/07-12-01, add subsection Constraints, with the following:[1] Normal End and Abnormal End cannot have values at the same time. not (self.Normal End->notEmpty() and self.Abnormal End->notEmpty())[2] Failure and Success cannot have values at the same time. not (self.Failure->notEmpty() and self.Success->notEmpty())[3] Abort and Error cannot have values at the same time. not (self.Abort->notEmpty() and self.Error->notEmpty())
Course Occurrence In the new section on 'Course Occurrence add subsection Constraints, with the following:[1] Start and End event parts cannot have the same values. not self.Start = self.End

Resolution Status:
Resolved.