Issue 14745: Section 14.2.2 Activity (semantics): (bpmn2-rtf) Source: Department of Veterans Affairs (Dr. Stephen White, steve.white(at)bookzurman.com) Nature: Enhancement Severity: Critical Summary: Beta 1: Section 14.2.2 Activity (semantics): The state of a Data Object should be considered as a Performance Constrainst for an Activity Changing from the Ready to Active state ##Source: IBM (Stephen A. White, wstephe@us.ibm.com) ##Original Issue: http://www.osoa.org/jira/browse/BPMN-411 ##Original Info: (Severity: Critical - Nature: Enhancement) The state of a Data Object should be considered as a Performance Constrainst for an Activity Changing from the Ready to Active state. If a Data Object is not in the state defined as an input (e.g., "Approved"), then the InputSet should not yet be considered "available." Resolution: - This is potentially a minor feature that would be suitable for an RTF. There are alternative methods for resolving this issue and the FTF did not come up with an agreement. Some resolutions would be out of scope for an RTF, but others would not. Thus, it should be deferred for further discussion by an RTF to determine it can be resolved or closed. Disposition: Deferred Revised Text: Actions taken: November 20, 2009: received issue Discussion: Comments: From: ings_osoa created: Tue, 10 Mar 2009 10:35:26 -0500 (CDT) SAP believes that modeling of Data Object states is out of scope of BPMN 2.0. This is required if we want to introduce the state of Data Objects as a performance constraint. Steve still thinks this is an interesting issue but he agrees to defer it as it will not be resolvable in the available time. From: conrad.bock created: Tue, 10 Mar 2009 10:40:43 -0500 (CDT) The spec already supports Data Object state, see Figure 10-46 (DataObject class diagram) in 0.9.7. From: conrad.bock created: Tue, 10 Mar 2009 10:43:31 -0500 (CDT) P.S. Since the specfalready supports Data Object state, it would be good to include it in the execution semantics. The execution semantics description is very incomplete anyway and is critical to complete, see <a href="http://www.osoa.org/jira/browse/BPMN-415">http://www.osoa.org/jira/browse/BPMN-415</a>. I added a link. From: hvo created: Mon, 16 Mar 2009 09:54:09 -0500 (CDT) My state of knowledge is also that data object state is out of scope. It can be specified but it does not affect semantics. Data object state was never considered a "performance constraint" in in sense of Sect 13 so far. From: hvo created: Wed, 18 Mar 2009 11:49:42 -0500 (CDT) Steve, Conrad and me suggest to defer this issue. End of Annotations:===== s is issue # 14745 [OMG 14745] Beta 1: Section 14.2.2 Activity (semantics): The state of a Data Object should be considered as a Performance Constrainst for an Activity Changing from the Ready to Active state ##Source: IBM (Stephen A. White, wstephe@us.ibm.com) ##Original Issue: http://www.osoa.org/jira/browse/BPMN-411 ##Original Info: (Severity: Critical - Nature: Enhancement) The state of a Data Object should be considered as a Performance Constrainst for an Activity Changing from the Ready to Active state. If a Data Object is not in the state defined as an input (e.g., "Approved"), then the InputSet should not yet be considered "available." Comments: From: ings_osoa created: Tue, 10 Mar 2009 10:35:26 -0500 (CDT) SAP believes that modeling of Data Object states is out of scope of BPMN 2.0. This is required if we want to introduce the state of Data Objects as a performance constraint. Steve still thinks this is an interesting issue but he agrees to defer it as it will not be resolvable in the available time. From: conrad.bock created: Tue, 10 Mar 2009 10:40:43 -0500 (CDT) The spec already supports Data Object state, see Figure 10-46 (DataObject class diagram) in 0.9.7. From: conrad.bock created: Tue, 10 Mar 2009 10:43:31 -0500 (CDT) P.S. Since the specfalready supports Data Object state, it would be good to include it in the execution semantics. The execution semantics description is very incomplete anyway and is critical to complete, see http://www.osoa.org/jira/browse/BPMN-415. I added a link. From: hvo created: Mon, 16 Mar 2009 09:54:09 -0500 (CDT) My state of knowledge is also that data object state is out of scope. It can be specified but it does not affect semantics. Data object state was never considered a "performance constraint" in in sense of Sect 13 so far. From: hvo created: Wed, 18 Mar 2009 11:49:42 -0500 (CDT) Steve, Conrad and me suggest to defer this issue.