BPEL Template Requirements and Use Case Alex Yiu
BPEL Template Requirements and Use Case Alex Yiu Ashwini Surpur Goran Olsson Martin Chapman Nickolas Kavantzas
Requirements Ÿ BPEL MUST allow the behavior of a participant to be modeled with varying degrees of detail. Ÿ BPEL MUST allow place holders to be inserted by the modeler into the design; including appropriate comments and descriptions such that the business process can be supplied with details or activities for further clarification. Ÿ BPEL MUST allow the modeler to model a process lifecycle without having to know its details. Ÿ BPEL MUST have one schema -- the addition of opaque activities/attributes should make it a non-executable BPEL process; the implementer MUST fill these holes to make it executable. Ÿ BPEL modeler SHOULD be allowed to model the business process as precisely as possible (with minimum ambiguity), while allowing the flexibility to implicitly and explicitly hide certain behavior.
Template Use case for BPEL From High Level to more detailed view, BPEL MUST support varying degrees of abstraction. For example, in this model, the business analyst shows the business workflow model at a very high level. Receive Order Mechanics of operation are unknown opaque Opaque (transformation/ translation/validation) Opaque (Credit check) Validate Order Invoke Inventory Check
Template Use Case for BPEL(cont’d) Receive Order The business workflow model is more concrete but, yet to be completed. opaque Opaque (transformation/ translation/validation) no/unknown Good standing customer? Was previously opaque Acknowledge order Invoke Credit Check no credit Ok? Acknowledge order yes Reject order
Conclusions Ÿ BPEL MUST have one schema, for every usage Ÿ Opaque activity/attribute makes it a nonexecutable BPEL process Ÿ To make it an executable process opaque constructs MUST be replaced or removed
- Slides: 5