RE: More use cases

 
David, if the order submission process and the order status query process are part of the same larger choreography, then  the dependency issue disappears.
 
With separate choreographies for the two processes, the state connecting the two choreographies has to be maintained outside of the choreography.
 
The question now is - whether the choreography language should support references to such external state (perhaps in the form of a language to specify preconditions, post conditions, etc).
 
The alternative may be to simply require that the related choreographies should always be defined under a larger umbrella choreography, such that the dependency state management naturally falls within the scope of choreography.
 
Some of the above may sound like jumping into the solution. However, I am trying to understand myself whether the use case is within our scope at all.

Sanjay Patil 
Distinguished Engineer 
sanjay.patil@iona.com 
------------------------------------------------------- 
IONA Technologies 
2350 Mission College Blvd. Suite 650 
Santa Clara, CA 95054 
Tel: (408) 350 9619 
Fax: (408) 350 9501 
------------------------------------------------------- 
Making Software Work Together TM 

-----Original Message-----
From: Burdett, David [mailto:david.burdett@commerceone.com]
Sent: Tuesday, April 01, 2003 1:08 PM
To: WS Choreography (E-mail)
Subject: More use cases



Martin sending out a use case reminded me of another use case involving dependencies between choreographies that I want to provide.

David 
<<Choreography Dependency use case.htm>> 

Director, Product Management, Web Services 
Commerce One 
4440 Rosewood Drive, Pleasanton, CA 94588, USA 
Tel/VMail: +1 (925) 520 4422; Cell: +1 (925) 216 7704 
mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com