B04

card_id: B04

input: A description of activities, events, participants, messages, data objects, and control-flow conditions (sequence flow, gateways) for a business process.

operation: Encode the process as a BPMN diagram (Process, Collaboration, or Choreography) using the standard's defined element set and execution semantics. Independently, PM02 operationalizes this by translating BPMN elements into a Petri-net model, enabling static structural analysis (e.g., deadlock/livelock detection) of the same control-flow constructs.

output: A conformant BPMN process/collaboration/choreography model; when passed through PM02's mapping, an equivalent Petri-net model usable for automated semantic-error checking.

scope_conditions: Business processes and inter-participant behavior expressible with BPMN's activity/event/gateway/data vocabulary; PM02's mapping specifically covers tasks, events, gateways, looping/multiple instances, subprocesses, exception handling, and message flow.

failure_conditions: A partial implementation cannot claim conformance to a BPMN conformance class; PM02 finds BPMN's construct mix "makes it possible to create models with semantic errors" and identifies specific specification deficiencies (e.g., ambiguities in multiple start events and exception handling).

predicted_effect: Not asserted as an outcome-improving claim by either source; BPMN is a representational/execution-semantics standard, and PM02's claimed benefit is detectability of semantic errors before runtime, not a general performance effect.

measurement: PM02 measures analysis capability via successful static detection of semantic errors in an implemented tool (Petri Net Markup Language export), tested against real models (Section 5.3 Empirical Evaluation).

implementation_test: Encode a process with the target elements; validate structural/execution conformance against the applicable BPMN conformance class (PM01 Section 2). Independently, run PM02's BPMN-to-Petri-net tool and check for reported semantic errors.

decision_rights: Participants, lanes, and performer/resource assignments are representable within a model; neither source assigns organizational decision authority beyond the model itself.

uncertainty_handling: No epistemic-uncertainty mechanism in either source; both are deterministic structural/semantic formalisms.

verification: BPMN conformance-class checking (PM01 Section 2); Petri-net-based static analysis for deadlocks/livelocks and other structural anomalies (PM02 Sections 3-5).

provenance: PM01 sections 2, 7, 9, 10, 13; PM02 sections 2-5.

implementation_cost: Not quantified; PM02 implies nontrivial tooling effort (a full mapping-and-analysis tool was built) but gives no cost figure.

limitations: PM02 predates BPMN 2.0.2 (targets an earlier BPMN version) though its element mapping is largely a subset of 2.0.2's vocabulary; no controlled study of adoption cost was located.

statement_basis: direct: ["BPMN conformance classes (PM01 Section 2)", "BPMN-to-Petri-net control-flow mapping (PM02 Section 3)", "reported specification deficiencies (PM02 Section 4)"] inference: ["predicted_effect note that neither source claims a performance effect is a curator observation, not a quoted disclaimer"]