1 / 5

Requirements

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.

gyan
Download Presentation

Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BPEL Template Requirements and Use CaseAlex YiuAshwini SurpurGoran OlssonMartin ChapmanNickolas Kavantzas

  2. 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.

  3. Template Use case for BPEL Receive Order Mechanics of operation are unknown Opaque (transformation/ translation/validation) opaque Opaque (Credit check) opaque 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. Validate Order Invoke Inventory Check

  4. Template Use Case for BPEL(cont’d) Receive Order The business workflow model is more concrete but, yet to be completed. Opaque (transformation/ translation/validation) opaque Good standing customer? yes no/unknown Acknowledge order Invoke Credit Check Was previously opaque no credit Ok? Reject order Acknowledge order

  5. Conclusions • BPEL MUST have one schema, for every usage • Opaque activity/attribute makes it a non- executable BPEL process • To make it an executable process opaque constructs MUST be replaced or removed

More Related