The requirement "For each customer..." implies that a set of activities should be performed for every item in a collection (the list of customers). The standard BPMN notation for this is the Multi-Instance marker on an Activity or Sub-Process. Option C correctly shows a Sub-Process containing the required sequence of activities ("Request Information", "Receive Information", "Update Database") marked with the Multi-Instance symbol (three vertical bars). This indicates that the entire Sub-Process will be instantiated and executed for each customer.

A. This is too abstract. While the loop marker on a single task implies repetition, it doesn't show the required internal sequence of three distinct activities.

B. The standard loop marker indicates repetition based on a condition (e.g., a while loop). The Multi-Instance marker is more specific and appropriate for iterating over a collection.

D. This diagram incorrectly places the loop marker only on the "Update Database" task, implying that only this final step is repeated, not the entire sequence.

1. Object Management Group. (2013). Business Process Model and Notation (BPMN) Version 2.0.2. OMG Document Number formal/2013-12-09.

Section 10.2.6, "Multi-Instance Activity" (p. 179): "A Multi-Instance Activity is an Activity that is executed multiple times... The instances can be executed in parallel or sequentially." This is the formal definition for "for each" semantics.

Figure 10.37 (p. 180) and Figure 10.38 (p. 181) illustrate the markers for parallel and sequential multi-instance activities.

Business Process Re-engineering (BPR) involves the radical redesign of core business processes to achieve dramatic improvements. According to Chang, Information Technology (IT) is the key enabler of BPR because it allows companies to break old rules and constraints imposed by manual or legacy systems. Technologies like shared databases, expert systems, telecommunication networks, and workflow automation enable fundamentally new ways of working, such as parallel processing, decentralized decision-making, and collapsing geographical barriers, which are central to the radical changes BPR aims for.

A. Incremental change is the opposite of BPR's philosophy, which focuses on radical, fundamental redesign rather than small, continuous improvements.

B. Labor specialization is a principle of functional, task-oriented organizations (Adam Smith's model), which BPR often seeks to replace with multi-skilled, process-oriented teams.

D. Strong functional structure creates the "silos" that BPR is designed to break down by focusing on end-to-end, cross-functional processes.

1. Chang, J. F. (2016). Business Process Management Systems: Strategy and Implementation (2nd ed.). CRC Press. In Chapter 2, Section 2.4, "The Role of Information Technology," Chang states, "IT is a key enabler for BPR" (p. 31) and details how different technologies enable process redesign.

2. Hammer, M., & Champy, J. (1993). Reengineering the Corporation: A Manifesto for Business Revolution. HarperBusiness. The authors famously argue that companies must use the power of modern information technology to radically redesign business processes (Chapter 3).

This scenario requires an exception handling mechanism that interrupts the entire process if a time condition is met. Option D correctly models this using an Interrupting Boundary Timer Event attached to a sub-process that encapsulates the entire normal flow (A, B, C, D). If the 3-day timer fires before the sub-process completes, the normal flow is interrupted. The exception flow then proceeds to a "Failure Notification" task and concludes with a Terminate End Event, which immediately ends all activities in the entire process instance.

A. The timer is attached only to task C, meaning it only starts when C starts and would only interrupt task C, not the whole process.

B. This option uses a normal End Event. A normal End Event only concludes the current path, whereas a Terminate End Event is required to stop all parallel flows.

C. An Event Sub-Process is a non-interrupting way to handle events by default and is not the most direct way to model the required interruption of the main flow.

1. Object Management Group. (2013). Business Process Model and Notation (BPMN) Version 2.0.2 (formal/2013-12-09). Section 10.4.4, "Boundary Events," p. 182. "If the isInterrupting attribute is true, the Activity is interrupted."

2. Object Management Group. (2013). Business Process Model and Notation (BPMN) Version 2.0.2 (formal/2013-12-09). Section 10.5.5, "End Event," p. 201. "A Terminate End Event indicates that all activities in the Process SHOULD be immediately ended."

3. Decker, G., & Puhlmann, F. (2007). Extending BPMN for modeling complex choreographies. In Proceedings of the 15th International Conference on Cooperative Information Systems (CoopIS 2007). Lecture Notes in Computer Science, vol 4803. Springer, Berlin, Heidelberg. (This paper discusses advanced event handling, reinforcing the distinct roles of different event types like boundary and terminate events). DOI: https://doi.org/10.1007/978-3-540-76848-718

The depicted ad-hoc Sub-Process (recognisable by its dashed border and absence of sequence flows between contained activities) allows its contained activities to be executed “in any order, or even in parallel,” as determined at runtime. BPMN 2.0 specifies: “The order of execution of the contained activities is undefined” (OMG BPMN 2.0, §10.2.2, p. 174). Therefore activities C and D have no predefined ordering; whichever starts first is implementation-dependent.

A. A predefined sequence putting C before D is not shown.

B. No sequence flow or rule places D before C.

C. Parallel execution is only one possible runtime behaviour; the specification states the order is undefined, not necessarily parallel.

1. OMG BPMN 2.0.2, formal/2013-12-09, §10.2.2 “Ad-Hoc Sub-Process,” p. 174.

2. van der Aalst, W., “Process Mining,” Springer, 2016, §3.4.3, pp. 82-83 (ad-hoc semantics).

Executable modeling is the BPMN level most dependent on vendor tools. While BPMN 2.0 provides a standardized format for executable processes, making a model truly runnable on a specific Business Process Management Suite (BPMS) often requires using vendor-specific extensions, properties, and configurations. These can include technical details for data mapping, script formats, service integrations, and user interface definitions that are not fully standardized across different vendors' process engines. This dependency arises because the standard must be general, while execution requires platform-specific details.

A. Pattern modeling is a design approach, not one of the three standard levels of BPMN modeling detail discussed in the OCEB2 curriculum.

C. Descriptive modeling uses a core subset of BPMN elements that are highly standardized and portable across virtually all modeling tools.

D. Source-code modeling is not a standard term for a BPMN modeling level; BPMN is a graphical notation, not source code.

1. Object Management Group. (2013). Business Process Model and Notation (BPMN) Version 2.0.2. (OMG Document Number: formal/2013-12-09). Section 14, "BPMN Conformance," defines process execution conformance, but acknowledges that aspects like expression languages can vary.

2. Weilkiens, T., Weiss, C., & Grass, A. (2016). OCEB 2 Certification Guide: Business Process Management - Fundamental Level (2nd ed.). Morgan Kaufmann. Chapter 4, Section 4.1, "Three Levels of BPMN Modeling," notes that executable models contain technical details needed for a specific process engine.

3. White, S. A., & Miers, D. (2008). BPMN Modeling and Reference Guide. Future Strategies Inc. Chapter 1, "Introduction," discusses the challenge of model interchange between tools, which is most acute at the executable level due to vendor-specific extensions.