B04

• Input: Activities, events, decisions, participants, messages, data, exceptions, and termination rules.
• Operation: Encode control flow with typed activities, gateways, events, sequence/message flows, pools/lanes, loops, and exception behavior; optionally bind to execution semantics.
• Output: Inspectable or executable process model.
• Scope conditions: Organizational or computational processes with observable flow.
• Failure conditions: Semantics are used inconsistently; hidden work is omitted; model and execution diverge.
• Predicted effect: Explicit flow models reduce ambiguity and enable conformance checking.
• Measurement: Model agreement, conformance violations, execution success, and defect detection.
• Implementation test: Parse/validate the model and execute representative paths including exceptions.
• Decision rights: Model owner approves; engine enforces executable semantics.
• Uncertainty handling: Alternative paths can be modeled; epistemic uncertainty needs extension.
• Verification: Schema validation, simulation, and conformance.
• Provenance: Optional annotations/version control.
• Implementation cost: Modeling expertise and tooling.
• Limitations: Native focus is process coordination, not epistemic reasoning. Direct: controlling specification. Inference: comparative metrics.