Issue 12178: Section: Happening and Change (bpdm-ftf) Source: NIST (Mr. Conrad Bock, conrad.bock@nist.gov conradb@cme.nist.gov) Nature: Revision Severity: Minor Summary: 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: 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. Revised Text: Actions taken: January 16, 2008: received issue July 18, 2008: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 16 Jan 2008 13:16:41 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Conrad Bock Company: NIST mailFrom: conrad.bock@nist.gov Notification: No Specification: Business Process Definition MetaModel Section: Happening and Change FormalNumber: dtc/07-12-05 Version: RevisionDate: Page: Nature: Revision Severity: Minor HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) Description 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.