WS BPEL Use Case Definition

1
WS BPEL Use Case Definition

• 06 October 2003

2
OASIS WS BPEL TC

• Our charter is to produce a normative language
  specification
• WS BPEL 1.0

3
Use Case

• Use Cases use what we produce for the purpose
  of
• Illustrating / finding problems
• Validate usefulness in real world
• If we produced radios, our use cases would
  involve descriptions of turning knobs
• For us, our knobs are our language constructs
• Sequence
• Pick
• etc

4
What is a use case then?

• For us then, literally a use case is a usage of
  the BPEL spec
• BPEL is a language, so a usage is an instance of
  a BPEL file
• This is admittedly rather terse, so

5
A BPEL use case needs more

• A BPEL use case (BPEL file) by definition has
  dependencies that draw the real world into it
• BPEL orchestrates web services (WSDL)
• WSDL needs a relation to web services and
  business entities to become truly understandable
• The business entities and their business flow
  should be something out of a well known and
  understood business standard

6
Thus, we need the full catalog

• Standards
• Business entities / roles
• Services
• WSDL
• BPEL

7
So when we use the phrase use case

• We could either mean
• Strictly usage of BPEL, knowing that BPEL is
  terse and we need the full stack of artifacts to
  be complete, OR
• The full stack, which includes a mandatory BPEL
  file