Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.

• Figures
  • Page 136, Figure 4.14: the example could use an end event after the exclusive or split, so that the otherwise infinite loop is terminated
  • Page 147, Figure 4.25: Figure illustrates "sequential execution without a priori design time knowledge" pattern. It might be misleading that the BPMN semantics of the subprocess is parallel execution of B,C, and D.

• • Page 156, second paragraph: "... determined the not by only ..." should read "... determined not only by ...". Also on this page "remainder" instead of "reminder".
  • Page 163, Figure 4.34: Arrows in the lower part should be directed from the connector to the event nodes, for the XOR connector, the OR connector, and the AND connector.
  • Page 205, Figure 4.76: The CreditInfo input and output parameters of the Accept Credit activity should be "CreditInfo = [Jane, 16000]", not "CreditInfo = [Miller, 15000]"

Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.

• Page 96, Definition 3.4, line 6: "an event ordering" instead of "an event orderings"
• Page 216, first paragraph: The term "completed" is used with the meaning "immediately stopped".
• Page 272, last line: "t1" instead of "t2"

• Figures
  • Page 136, Figure 4.14: the example could use an end event after the exclusive or split, so that the otherwise infinite loop is terminated
  • Page 147, Figure 4.25: Figure illustrates "sequential execution without a priori design time knowledge" pattern. It might be misleading that the BPMN semantics of the subprocess is parallel execution of B,C, and D.

Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.

• • Page 156, second paragraph: "... determined the not by only ..." should read "... determined not only by ...". Also on this page "remainder" instead of "reminder".
  • Page 163, Figure 4.34: Arrows in the lower part should be directed from the connector to the event nodes, for the XOR connector, the OR connector, and the AND connector.
  • Page 205, Figure 4.76: The CreditInfo input and output parameters of the Accept Credit activity should be "CreditInfo = [Jane, 16000]", not "CreditInfo = [Miller, 15000]"

• References
  • Martens (2003c), van der Aalst and Weske (2001b), Mohan (2002b), and Workflow Management Coalition (2005b) are redundant
  • Title in Zaha et al. (2006a) needs to be changed to "Let's Dance: A Language for Service Behavior Modeling"

Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.

• On page X, "Dolf Grünberg" needs to be substituted by "Dolf Grünbauer"
• Page 96, Definition 3.4, line 6: "an event ordering" instead of "an event orderings"
• Page 216, first paragraph: The term "completed" is used with the meaning "immediately stopped".

• Figures
  • Page 136, Figure 4.14: the example could use an end event after the exclusive or split, so that the otherwise infinite loop is terminated
  • Page 147, Figure 4.25: Figure illustrates "sequential execution without a priori design time knowledge" pattern. It might be misleading that the BPMN semantics of the subprocess is parallel execution of B,C, and D.

Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.

• Figures
  • Page 136, Figure 4.14: the example could use an end event after the exclusive or split, so that the otherwise infinite loop is terminated
  • Page 147, Figure 4.25: Figure illustrates "sequential execution without a priori design time knowledge" pattern. It might be misleading that the BPMN semantics of the subprocess is parallel execution of B,C, and D.

• • Page 163, Figure 4.34: Arrows in the lower part should be directed from the connector to the event nodes, for the XOR connector, the OR connector, and the AND connector.
  • Page 205, Figure 4.76: The CreditInfo input and output parameters of the Accept Credit activity should be "CreditInfo = [Jane, 16000]", not "CreditInfo = [Miller, 15000]"
• References

Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.

Errata

• On page X, "Dolf Grünberg" needs to be substituted by "Dolf Grünbauer"
• Page 96, Definition 3.4, line 6: "an event ordering" instead of "an event orderings"

• Figures
  • Page 136, Figure 4.14: the example could use an end event after the exclusive or split, so that the otherwise infinite loop is terminated
  • Page 147, Figure 4.25: Figure illustrates "sequential execution without a priori design time knowledge" pattern. It might be misleading that the BPMN semantics of the subprocess is parallel execution of B,C, and D.

Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.

• Page 96, Definition 3.4, line 6: "an event ordering" instead of "an event orderings"
• Figures
  • Page 136, Figure 4.14: the example could use an end event after the exclusive or split, so that the otherwise infinite loop is terminated

• • Page 163, Figure 4.34: Arrows in the lower part should be directed from the connector to the event nodes, for the XOR connector, the OR connector, and the AND connector.
  • Page 205, Figure 4.76: The CreditInfo input and output parameters of the Accept Credit activity should be "CreditInfo = [Jane, 16000]", not "CreditInfo = [Miller, 15000]"
• References

Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.

• On page X, "Dolf Grünberg" needs to be substituted by "Dolf Grünbauer"
• Page 96, Definition 3.4, line 6: "an event ordering" instead of "an event orderings"
• Figures

• • Page 163, Figure 4.34: Arrows in the lower part should be directed from the connector to the event nodes, for the XOR connector, the OR connector, and the AND connector.
  • Page 205, Figure 4.76: The CreditInfo input and output parameters of the Accept Credit activity should be "CreditInfo = [Jane, 16000]", not "CreditInfo = [Miller, 15000]"
• References

Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.

Errata

• On page X, "Dolf Grünberg" needs to be substituted by "Dolf Grünbauer"

• Figures

• References
  • Martens (2003c), van der Aalst and Weske (2001b), Mohan (2002b), and Workflow Management Coalition (2005b) are redundant
  • Title in Zaha et al. (2006a) needs to be changed to "Let's Dance: A Language for Service Behavior Modeling"

Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.

• References
  • Martens (2003c), van der Aalst and Weske (2001b), Mohan (2002b), and Workflow Management Coalition (2005b) are redundant
  • Title in Zaha et al. (2006a) needs to be changed to "Let's Dance: A Language for Service Behavior Modeling"

Updates

• Recently, a new version of the Business Process Modeling Notation (BPMN 1.1) was published. A document written bei HPI researcher Gero Decker and HPI graduate Torben Schreiter investigates the novel aspects of BPMN 1.1; Torben is now with Inubit AG, a Berlin based company specializing in business process management.