The WS BPEL Use Cases

1
The WS BPEL Use Cases

• Overview

2
Overview

• Goals
• Rationale
• Definition
• Need to Reuse
• Artifacts
• Organization

3
Goals

• Validate
• BPEL solves real world problems
• Illustrate
• Identify and help to resolve BPEL language
  issues

4
Rationale

• BPEL use cases need to demonstrate using BPEL
  (creating BPEL files), but must also
• Have a context that is sensible and grounded in
  real-life business patterns, and understandable
  by business analysts
• BPEL use cases need to be able to be approached
  from the technical perspective, as well as from
  the business perspective

5
Definition

• A BPEL use case exercises BPEL as a language with
  BPEL files
• Abstract BPEL
• Executable BPEL
• A BPEL use case explains the exercise with meta
  information
• Business process model (diagram)
• Prose to make the diagram more understandable
• A BPEL use case is associated with a context that
  is based on business instances from established
  work of reputable organizations, such as

6
Need to Reuse

• Create a context of business instances that can
  be reused for various BPEL use cases
• Fictional yet concrete instances of businesses
• departments, customers, partners
• Where the business instances
• interact via business patterns
• own and operate web services
• Own the web services
• wrapped legacy systems, app servers etc.

7
Artifacts

• BPEL Use Case
• Abstract BPEL
• Executable BPEL
• Meta Info
• Web Services Context
• Service Descriptions
• WSDL
• XSD
• Business Instances Context
• Business Instances
• Business Flows
• Business Pattern Standard (or equiv)

8
Organization

• Use Case Catalog
• BPEL Use cases
• Web Services Context
• Business Instances Context
• Use Case Spreadsheet
• Classify use cases complete
• Identify use cases needed