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.