Use Case

Requirements/Comments

UC-001
  1. Composition (parallel and sequence)

UC-002

No different to UC-001

UC-003

Base for new UC-001

UC-004

2.    Failure to comply exception MAY be generated by a choreography instance.  (this might have been in UC-011).

3.    Conditional paths

4.    Nesting and composition

5.    Sequence

6.    Termination of a choreography

UC-005

7.    A CDL shall support the description of application exceptions

  1. A CDL shall support the description of WSDl faults.

UC-006
  1. A CDL shall facilitate the demarcation of observable transactional behaviour.

UC-007

None (that is no language features could be gleaned from this use case)

UC-008

Base for new UC-002

UC-009

10. There MUST be no control statements in the CDL (i.e. IF, WHILE, ... etc)

11. There MUST be a mechanism for adding annotation or comments to a choreography description.

12. A CDL must support the description of a multi-party global model.

  1. A CDL must facilitate hierarchical decomposition to enable choreography descriptions to reference each other and to support some notion of abstraction to make descriptions easier to understand.

UC-010

14. There should be a binding mechanism to enable a choreography to bind to differing QoS as applied to messaging and to differing correlation mechanisms.

  1. A CDL should be able to participate in the generation of a CPL (usage rather than requirement).

UC-011

16. A CDL should be able to be used to generate suitable test message for a CPL or such-like (usage not a requirement)

17. Static verification through bi-simulation (V2)