Issue 9345: unclear what Figure 13 on p. 71 represents (bpmn-ftf) Source: CA Inc. (Ms. Donna Burbank, donna.burbank@ca.com donna_burbank@yahoo.com) Nature: Clarification Severity: Minor Summary: I am unclear what Figure 13 on p. 71 represents. The bottom part of the diagram appears to show multiple pools joined together(Employee, Retail, etc.), showing lanes without labels. Is this a single poole or multiple pools? Resolution: Revised Text: Figure 9.10 will be replaced by the following Figure: Actions taken: February 1, 2006: receivrd issue April 19, 2007: closed issue Discussion: Resolution: The FTF agreed that there is a problem that needs fixing, and has proposed a resolution (which may or may not agree with any resolution the issue submitter proposed). Figure 9.10 will be updated to include a Pool Name for the Pool that has Lanes. This will make this figure consistent with the other figures of Pools that are in the specification. Also, the figure will be modified so that entire width of the Processes are not displayed. By reducing the width of the diagram it can be zoomed in enough to make the diagram more legible. End of Annotations:===== m: webmaster@omg.org Date: 01 Feb 2006 12:41:39 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Donna Burbank Company: Embarcadero mailFrom: donna.burbank@embarcadero.com Notification: Yes Specification: BPMN Section: independent subprocess FormalNumber: ? Version: 1.0 RevisionDate: May 3, 2004 Page: 71 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727) Description I am unclear what Figure 13 on p. 71 represents. The bottom part of the diagram appears to show multiple pools joined together(Employee, Retail, etc.), showing lanes without labels. Is this a single poole or multiple pools? To: bpmn-ftf@omg.org Subject: Proposed Solution for Issue 9345 X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005 From: Stephen A White Date: Wed, 10 May 2006 17:40:18 -0700 X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 6.53HF743 | November 3, 2005) at 05/10/2006 18:40:22, Serialize complete at 05/10/2006 18:40:22 The resolution and related information about this Issue can be found here: http://www.bpmn.org/FTF/Issues/Issue%209345.htm If you have any comments, questions, suggested revisions about the current resolution, or an alternative resolution, then reply to this message or speak up at a group meeting. Thanks. To: bpmn-ftf@omg.org Subject: Proposed Resolution for Issue 9354 X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005 From: Stephen A White Date: Wed, 10 May 2006 17:40:25 -0700 X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 6.53HF743 | November 3, 2005) at 05/10/2006 18:40:29, Serialize complete at 05/10/2006 18:40:29 The resolution and related information about this Issue can be found here: http://www.bpmn.org/FTF/Issues/Issue%209354.htm If you have any comments, questions, suggested revisions about the current resolution, or an alternative resolution, then reply to this message or speak up at a group meeting. Thanks. Subject: RE: Proposed Solution for Issue 9345 Date: Thu, 11 May 2006 03:56:23 -0600 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Proposed Solution for Issue 9345 Thread-Index: AcZ0krPc3G2T8MpLTimNqLcdUTZH1QATXGVA From: "Donna Burbank" To: "Stephen A White" , X-OriginalArrivalTime: 11 May 2006 09:56:25.0498 (UTC) FILETIME=[2A6E67A0:01C674E1] There is still a slight inconstancy between the example shown in issue 9345 and the other examples in the spec. Normally, a pool header has a .line break. underneath it, but the lanes do not. In the example, there is a .line break. under the lane names as well. For example .Tap System Coordinator. has a line break (issue 9345 example), but .Distribution. does not (example from existing spec). The text of the spec says .Our examples place [lane] name as a banner on the left side (for horizontal Pools) or at the top (for vertical Pools) on the other side of the line that separates the Pool name, however, this is not a requirement.. But it doesn.t say anything about putting a line separating the lane name from the contents of the lane (on the right for horizontal and on the bottom for vertical). Donna Burbank Director, Enterprise Modeling and Architecture Solutions Embarcadero Technologies phone: (303) 730-7981 x139 cell: (303) 641-2619 -------------------------------------------------------------------------------- From: Stephen A White [mailto:wstephe@us.ibm.com] Sent: Wednesday, May 10, 2006 6:40 PM To: bpmn-ftf@omg.org Subject: Proposed Solution for Issue 9345 The resolution and related information about this Issue can be found here: http://www.bpmn.org/FTF/Issues/Issue%209345.htm If you have any comments, questions, suggested revisions about the current resolution, or an alternative resolution, then reply to this message or speak up at a group meeting. Thanks. -Steve To: bpmn-ftf@omg.org Subject: RE: Proposed Solution for Issue 9345 X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005 From: Stephen A White Date: Thu, 11 May 2006 17:11:34 -0700 X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 6.53HF743 | November 3, 2005) at 05/11/2006 18:11:35, Serialize complete at 05/11/2006 18:11:35 Donna, I updated the figure as you suggested. -Steve "Donna Burbank" 05/11/2006 02:56 AM To Stephen A White/Irvine/IBM@IBMUS, cc Subject RE: Proposed Solution for Issue 9345 There is still a slight inconstancy between the example shown in issue 9345 and the other examples in the spec. Normally, a pool header has a .line break. underneath it, but the lanes do not. In the example, there is a .line break. under the lane names as well. For example .Tap System Coordinator. has a line break (issue 9345 example), but .Distribution. does not (example from existing spec). The text of the spec says .Our examples place [lane] name as a banner on the left side (for horizontal Pools) or at the top (for vertical Pools) on the other side of the line that separates the Pool name, however, this is not a requirement.. But it doesn.t say anything about putting a line separating the lane name from the contents of the lane (on the right for horizontal and on the bottom for vertical). Donna Burbank Director, Enterprise Modeling and Architecture Solutions Embarcadero Technologies phone: (303) 730-7981 x139 cell: (303) 641-2619 -------------------------------------------------------------------------------- From: Stephen A White [mailto:wstephe@us.ibm.com] Sent: Wednesday, May 10, 2006 6:40 PM To: bpmn-ftf@omg.org Subject: Proposed Solution for Issue 9345 The resolution and related information about this Issue can be found here: http://www.bpmn.org/FTF/Issues/Issue%209345.htm If you have any comments, questions, suggested revisions about the current resolution, or an alternative resolution, then reply to this message or speak up at a group meeting. Thanks. -Steve Subject: RE: Proposed Solution for Issue 9345 Date: Fri, 12 May 2006 08:42:18 -0600 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Proposed Solution for Issue 9345 Thread-Index: AcZ1V+Ncnzj/ZdjsRyKjOf2KGB78NwAelXXw From: "Donna Burbank" To: "Stephen A White" , X-OriginalArrivalTime: 12 May 2006 14:42:19.0072 (UTC) FILETIME=[452BD400:01C675D2] Great. Thanks. -------------------------------------------------------------------------------- From: Stephen A White [mailto:wstephe@us.ibm.com] Sent: Thursday, May 11, 2006 6:12 PM To: bpmn-ftf@omg.org Subject: RE: Proposed Solution for Issue 9345 Donna, I updated the figure as you suggested. -Steve "Donna Burbank" 05/11/2006 02:56 AM To Stephen A White/Irvine/IBM@IBMUS, cc Subject RE: Proposed Solution for Issue 9345 There is still a slight inconstancy between the example shown in issue 9345 and the other examples in the spec. Normally, a pool header has a .line break. underneath it, but the lanes do not. In the example, there is a .line break. under the lane names as well. For example .Tap System Coordinator. has a line break (issue 9345 example), but .Distribution. does not (example from existing spec). The text of the spec says .Our examples place [lane] name as a banner on the left side (for horizontal Pools) or at the top (for vertical Pools) on the other side of the line that separates the Pool name, however, this is not a requirement.. But it doesn.t say anything about putting a line separating the lane name from the contents of the lane (on the right for horizontal and on the bottom for vertical). Donna Burbank Director, Enterprise Modeling and Architecture Solutions Embarcadero Technologies phone: (303) 730-7981 x139 cell: (303) 641-2619 -------------------------------------------------------------------------------- From: Stephen A White [mailto:wstephe@us.ibm.com] Sent: Wednesday, May 10, 2006 6:40 PM To: bpmn-ftf@omg.org Subject: Proposed Solution for Issue 9345 The resolution and related information about this Issue can be found here: http://www.bpmn.org/FTF/Issues/Issue%209345.htm If you have any comments, questions, suggested revisions about the current resolution, or an alternative resolution, then reply to this message or speak up at a group meeting. Thanks. -Steve To: bpmn-ftf@omg.org Subject: Proposed Resolution for Issue 9325 X-Mailer: Lotus Notes Release 7.0 HF242 April 21, 2006 From: Stephen A White Date: Wed, 9 Aug 2006 16:25:47 -0700 X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 7.0.1HF269 | June 22, 2006) at 08/09/2006 17:25:49, Serialize complete at 08/09/2006 17:25:49 http://www.bpmn.org/FTF/Issues/Issue%209325.htm Description: Table 8.1: does not explain the difference between the 2 depictions of Associations given (one with an arrow) Suggested Resolution: Resolved: A description of Associations is given in Section 10.1.4. A brief description will be added to the table and a pointer to Section 10.1.4 will be added to the specification (see below). Note: Table 8.1 and 8.2 will be updated to provide pointers for all elements where there is additional information provided in later sections of the specification. Revised Text: Section 8.1, Table 8.2, page 17, third row ("Association"), second column ("Description"), append the paragraph: "An arrowhead on the Association indicates a direction of flow (e.g., data), when appropriate ("Association" on page XX)." More generally... Section 8.1, Table 8.2, page 16, first row ("Event"), second column ("Description"), modify the first sentence: "An event is something that .happens. during the course of a business process ("Events" on page XX)." Note that the page number is dynamic and dependent on the final layout of the specification. Section 8.1, Table 8.2, page 16, second row ("Activity"), second column ("Description"), modify the first sentence: "An activity is a generic term for work that company performs ("Activities" on page XX)." Section 8.1, Table 8.2, page 16, third row ("Gateway"), second column ("Description"), modify the first sentence: "A Gateway is used to control the divergence and convergence of Sequence Flow ("Gateways" on page XX)." Section 8.1, Table 8.2, page 17, first row ("Sequence Flow"), second column ("Description"), modify the first sentence: "A Sequence Flow is used to show the order that activities will be performed in a Process ("Sequence Flow" on page XX)." Section 8.1, Table 8.2, page 17, second row ("Message Flow"), second column ("Description"), modify the first sentence: "A Message Flow is used to show the flow of messages between two participants that are prepared to send and receive them ("Message Flow" on page XX)." Section 8.1, Table 8.2, page 17, fourth row ("Pool"), second column ("Description"), modify the first sentence: "A Pool represents a Participant in a Process ("Pool" on page XX)." Section 8.1, Table 8.2, page 17, fifth row ("Lane"), second column ("Description"), modify the first sentence: "A Lane is a sub-partition within a Pool and will extend the entire length of the Pool, either vertically or horizontally ("Lane" on page XX)." Section 8.1, Table 8.2, page 17, sixth row ("Data Object"), second column ("Description"), modify the first sentence: "... they do provide information about what activities require to be performed and/or what they produce ("Data Object" on page XX)." Section 8.1, Table 8.2, page 17, seventh row ("Group"), second column ("Description"), modify the first sentence: "A grouping of activities that does not affect the Sequence Flow ("Group" on page XX)." Section 8.1, Table 8.2, page 17, last row ("Text Annotation"), second column ("Description"), modify the first sentence: "Text Annotations are a mechanism for a modeler to provide additional information for the reader of a BPMN Diagram ("Text Annotation" on page XX)." Section 8.2, Table 8.3, page 18, first row ("Event"), second column ("Description"), modify the first sentence: "An event is something that .happens. during the course of a business process ("Events" on page XX)." Section 8.2, Table 8.3, page 18, second row ("Flow Dimension"), second column ("Description"), modify the first sentence of the first paragraph: "As the name implies, the Start Event indicates where a particular process will start ("Start" on page XX)." modify the first sentence of the second paragraph: "Intermediate Events occur between a Start Event and an End Event ("Intermediate" on page XX)." modify the first sentence of the third paragraph: "As the name implies, the End Event indicates where a process will end ("End" on page XX)." Section 8.2, Table 8.3, page 19, first row ("Type Dimension"), second column ("Description"), modify the first sentence of the first paragraph: "Start and most Intermediate Events have .Triggers. that define the cause for the event (.Start. on page 35 and .Intermediate. on page XX)." modify the third sentence of the first paragraph: "End Events may define a .Result. that is a consequence of a Sequence Flow ending (.End. on page XX)." Section 8.2, Table 8.3, page 19, second row ("Task"), second column ("Description"), modify the first sentence: "A Task is an atomic activity that is included within a Process (.Task. on page XX)" Section 8.2, Table 8.3, page 19, third row ("Process/Sub-Process"), second column ("Description"), modify the first sentence: "A Sub-Process is a compound activity that is included within a Process (.Sub-Process. on page XX)" Section 8.2, Table 8.3, page 19, fourth row ("Collapsed Sub-Process"), second column ("Description"), modify the first sentence: "A Sub-Process is a compound activity that is included within a Process (.Sub-Process. on page XX)" Section 8.2, Table 8.3, page 19, fifth row ("Expanded Sub-Process"), second column ("Description"), modify the first sentence: "The boundary of the Sub-Process is expanded and the details (a Process) are visible within its boundary (.Sub-Process. on page XX)" Section 8.2, Table 8.3, page 20, first row ("Gateway"), second column ("Description"), modify the first sentence: "A Gateway is used to control the divergence and convergence of multiple Sequence Flow (.Gateways. on page XX)" Section 8.2, Table 8.3, page 20, second row ("Gateway Control Types"), second column ("Description"), modify the second sentence of the first bullet: "Both Data-Based (.Data-Based. on page XX) and Event-Based (.Event-Based. on page XX)" modify the first sentence of the second bullet: "OR -- inclusive decision and merging (.Inclusive Gateways (OR). on page XX)." modify the first sentence of the third bullet: "Complex -- complex conditions and situations (e.g., 3 out of 5; .Complex Gateways. on page XX)." modify the first sentence of the fourth bullet: "AND -- forking and joining (.Parallel Gateways (AND). on page XX)." Section 8.2, Table 8.3, page 20, third row ("Sequence Flow"), second column ("Description"), modify the first sentence: "A Sequence Flow is used to show the order that activities will be performed in a Process (.Sequence Flow. on page XX)" Section 8.2, Table 8.3, page 20, fourth row ("Normal Flow"), second column ("Description"), modify the first sentence: "...and continues through activities via alternative and parallel paths until it ends at an End Event (.Normal Flow. on page XX)" Section 8.2, Table 8.3, page 20, last row ("Uncontrolled Flow"), second column ("Description"), modify the first sentence: "Uncontrolled flow refers to flow that is not affected by any conditions or does not pass through a Gateway (.Gateways. on page XX)" Section 8.2, Table 8.3, page 21, first row ("Conditional Flow"), second column ("Description"), modify the first sentence: "Sequence Flow can have condition expressions that are evaluated at runtime to determine whether or not the flow will be used (.Sequence Flow. on page XX)" Section 8.2, Table 8.3, page 21, second row ("Default Flow"), second column ("Description"), modify the first sentence: "For Data-Based Exclusive Decisions or Inclusive Decisions, one type of flow is the Default condition flow (.Sequence Flow. on page XX)" Section 8.2, Table 8.3, page 21, third row ("Exception Flow"), second column ("Description"), modify the first sentence: "...and is based upon an Intermediate Event that occurs during the performance of the Process (.Exception Flow. on page XX)" Section 8.2, Table 8.3, page 21, fourth row ("Message Flow"), second column ("Description"), modify the first sentence: "A Message Flow is used to show the flow of messages between two entities that are prepared to send and receive them (.Message Flow. on page XX)" Section 8.2, Table 8.3, page 21, last row ("Compensation Association"), second column ("Description"), modify the first sentence: "that is triggered through the failure of a Transaction or a Compensate Event (.Compensation Association. on page XX)" Section 8.2, Table 8.3, page 22, first row ("Data Object"), second column ("Description"), modify the first sentence: "...they do provide information about what activities require to be performed and/or what they produce (.Data Object. on page XX)" Section 8.2, Table 8.3, page 22, second row ("Fork (AND-Split)"), second column ("Description"), modify the first sentence: "BPMN uses the term .fork. to refer to the dividing of a path into two or more parallel paths (also known as an AND-Split; .Forking Flow. on page XX)" Section 8.2, Table 8.3, page 22, third row ("Join (AND-Join)"), second column ("Description"), modify the first sentence: "BPMN uses the term .join. to refer to the combining of two or more parallel paths into one path (also known as an AND-Join or synchronization; .Joining Flow. on page XX)" Section 8.2, Table 8.3, page 22, fourth row ("Decision, Branching Point; (OR-Split)"), second column ("Description"), modify the first sentence: "Decisions are Gateways within a business process where the flow of control can take one or more alternative paths (.Exclusive Gateways (XOR). on page XX)" Section 8.2, Table 8.3, page 22, last row ("Exclusive"), second column ("Description"), modify the first sentence: "An Exclusive Gateway (XOR) restricts the flow such that only one of a set of alternatives may be chosen during runtime (.Exclusive Gateways (XOR). on page XX)" Section 8.2, Table 8.3, page 23, first row ("Data-Based"), second column ("Description"), modify the first sentence: "...where Alternatives are based on conditional expressions contained within the outgoing Sequence Flow (.Data-Based. on page XX)" Section 8.2, Table 8.3, page 23, last row ("Event-Based"), second column ("Description"), modify the first sentence: "...where Alternatives are based on an Event that occurs at that point in the Process (.Event-Based. on page XX)" Section 8.2, Table 8.3, page 24, first row ("Inclusive"), second column ("Description"), modify the first sentence: "...where Alternatives are based on conditional expressions contained within the outgoing Sequence Flow (.Inclusive Gateways (OR). on page XX)" Section 8.2, Table 8.3, page 24, second row ("Merging (OR-Join)"), second column ("Description"), modify the first sentence: "...the exclusive combining of two or more paths into one path (also known as an a OR-Join; .Merging Flow. on page XX)" Section 8.2, Table 8.3, page 24, last row ("Activity Looping"), second column ("Description"), modify the first sentence: "The attributes of Tasks and Sub-Processes will determine if they are repeated or performed once (.Looping. on page XX)" Section 8.2, Table 8.3, page 25, first row ("Sequence Flow Looping"), second column ("Description"), modify the first sentence: "Loops can be created by connecting a Sequence Flow to an .upstream. object (.Looping. on page XX)" Section 8.2, Table 8.3, page 25, second row ("Multiple Instances"), second column ("Description"), modify the first sentence: "The attributes of Tasks and Sub-Processes will determine if they are repeated or performed once (.Looping. on page XX)" Section 8.2, Table 8.3, page 25, third row ("Process Break"), second column ("Description"), modify the first sentence: "A Process Break is a location in the Process that shows where an expected delay will occur within a Process (.Intermediate. on page XX)" Section 8.2, Table 8.3, page 25, fourth row ("Transaction"), second column ("Description"), modify the first sentence: "a special protocol that insures that all parties involved have complete agreement that the activity should be completed or cancelled (.Sub-Process Behavior as a Transaction. on page XX)" Section 8.2, Table 8.3, page 25, last row ("Nested/Embedded Sub-Process"), second column ("Description"), modify the first sentence: "A nested (or embedded) Sub-Process is an activity that shares the same set of data as its parent process (.Embedded Sub-Process. on page XX)" Section 8.2, Table 8.3, page 26, first row ("Group"), second column ("Description"), modify the first sentence: "A grouping of activities that does not affect the Sequence Flow (.Group. on page XX)" Section 8.2, Table 8.3, page 26, second row ("Off-Page Connector"), second column ("Description"), modify the first sentence: "...will show where the Sequence Flow leaves one page and then restarts on the next page (.Sequence Flow Jumping (Off-Page Connectors and Go To Objects). on page XX)" Section 8.2, Table 8.3, page 26, third row ("Association"), second column ("Description"), modify the first sentence: "An Association is used to associate information with Flow Objects (.Association. on page XX)" Section 8.2, Table 8.3, page 26, fourth row ("Text Annotation"), second column ("Description"), modify the first sentence: "Text Annotations are a mechanism for a modeler to provide additional information for the reader of a BPMN Diagram (.Text Annotation. on page XX)" Section 8.2, Table 8.3, page 26, fifth row ("Pool"), second column ("Description"), modify the first sentence: "A Pool represents a Participant in a Process (.Pool. on page XX)" Section 8.2, Table 8.3, page 26, last row ("Lanes"), second column ("Description"), modify the first sentence: "...will extend the entire length of the Pool, either vertically or horizontally (.Lane. on page XX)"