W3C Web Services Choreography working group
Use case summary
28th April 2004
Author Date Description uri
Tony Fletcher 18/3/03 3 scopes not 2: Not actually a use case but useful anyway public-ws-chor/2003Mar/0076.html
REQ Jon Dart 24/3/03 Requirements Summary: Not a usecase but useful anyway public-ws-chor/2003Mar/0167.html
REQ Jon Dart 10/4/03 Requirement for dealing with timeouts/failures public-ws-chor/2003Apr/0129.html
REQ David Burdett 10/4/03 Functional requirement for dealing with timeouts/failures public-ws-chor/2003Apr/0130.html
REQ Steve Ross-Talbot 11/4/03 Possible requirements (compatibility and verfiability). But how do we do it? public-ws-chor/2003Apr/0138.html
REQ Asaf Arkin 22/4/03 Change of patricipants - possible tech req public-ws-chor/2003Apr/0255.html
REQ Tony Fletcher 28/4/03 Requirements public-ws-chor/2003Apr/0280.html
REQ Ricky Ho 28/4/03 Further suggestions to above public-ws-chor/2003Apr/0281.html
REQ Daniel Austin 14/4/03 Working draft of the requirements document WD-ws-chor-requirements-20030414.html
REQ Tony Fletcher 17/4/03 Possible requirement public-ws-chor/2003Apr/0220.html
REQ Martin Chapman 17/4/03 Requirements extracted from previous minutes public-ws-chor/2003Apr/0224.html
REQ Fred Cummins 17/4/03 Additional requirements extracted from previous minutes public-ws-chor/2003Apr/0226.html
Hugo Haas 3/4/03 Usage scenarios and use cases: which is which? public-ws-chor/2003Apr/0038.html
David Burdett 10/4/03 Abstract Bindable Choreographies and dealing with timeouts public-ws-chor/2003Apr/0126.html
Assaf Arkin 10/4/03 Further stuff on timeouts/failures public-ws-chor/2003Apr/0132.html
USE CASE Stephen White 3/4/02 Diagrams in support of Paul Lipton usecase above public-ws-chor/2003Apr/0062.html
USE CASE Assaf Arkin 18/3/03 This use case is interesting since it highlights how one would use Web services technologies like WSDL, WS-Policy, SAML and WS-Choreography even for interactions that are not SOAP enabled. public-ws-chor/2003Mar/0065.html
USE CASE Edwin Khodabakchian 24/3/03 Doctor Patient original defn public-ws-chor/2003Mar/0172.html
USE CASE Stephen White 26/3/03 Doctor Patient diagrams public-ws-chor/2003Mar/0228.html
USE CASE Steve Ross-Talbot 27/3/03 Client Server interaction public-ws-chor/2003Mar/0265.html
USE CASE Paul Lipton 30/3/03 Provisioning and integrating new personnel into the enterprise public-ws-chor/2003Mar/0266.html
USE CASE Stephen White 3/4/03 In response to Paul Lipton's above and Mike Champion's comments (following): "Company A publishes its WSChoreography document so that its suppliers "know" that they can respond to an order for a faux oak desk with something else of comparable price and quality.". Includes diagrams. public-ws-chor/2003Apr/0060.html
USE CASE Updated above but with sub processes public-ws-chor/2003Apr/0062.html
USE CASE Jim Hendler 31/3/03 A couple of scenarios, evidence for implementibility and impact on Chor based for a use case in which services are composed from existing services (without pre-arrangement on the parts of the service suppliers). public-ws-chor/2003Mar/0273.html
USE CASE composition.pdf
USE CASE PlaceOrderChoreography.xml
USE CASE Martin Chapman 1/4/03 A system already exists and a new party comes along and needs to plug into that system. public-ws-chor/2003Apr/0004.html
USE CASE
USE CASE David Burdett 2/4/03 In this choreography one choreography is dependent on another such that the second choreography can only be executed after an instance of the earlier choreography has occurred. public-ws-chor/2003Apr/0005.html
USE CASE Choreography_Dependency_use_case.htm
USE CASE David Burdett 2/4/03 This use case suggests the idea of defining an "Outstanding Activities" choreography instance designed to support recovery after a catastrophic failure. The idea is that the Outstanding Activities choreography could be used after the failure of ANY choreography and is therefore generally applicable and so will benefit from standardization public-ws-chor/2003Apr/0015.html
USE CASE Choreography_Recovery_Use_Case.htm
USE CASE David Burdett 2/4/03 Extensible Composable Choreographies Use Case: identification of different document exchange patterns (i.e. choreographies) that businesses follow when placing an order public-ws-chor/2003Apr/0017.html
USE CASE BusinessTransactions.html
USE CASE Greg Ritzinger 2/4/03 I don't recall if any of the submitted use cases include the notion of an observer, but in some choreography scenarios an observer would be desirable public-ws-chor/2003Apr/0012.html
USE CASE David Burdett 3/4/03 flow associated with the placement of an order style. public-ws-chor/2003Apr/0057.html
USE CASE PlaceOrderChoreography.xml
USE CASE PlaceOrderChoreography.pdf
USE CASE Stephen White 3/4/03 Error handling in the dependencies between choreographies use case. Includes diagrams embedded in submission public-ws-chor/2003Apr/0059.html
USE CASE Monica Martin 4/4/03 Alternative paths based on business rules or requirements. Similar to first case except raises exception issue public-ws-chor/2003Apr/0058.html
USE CASE AlternativePaths_mm1_040103.doc
USE CASE David Burdett 23/10/03 eCommerce example public-ws-chor/2003Mar/0216.html
USE CASE 01-eCommerce_Use_Case.pdf
USE CASE David Burdett 11/4/03 Simple Order placement example for rendering using pi-calculus public-ws-chor/2003Apr/0172.html
USE CASE 12/4/03 Response to above from Asaf Arkin public-ws-chor/2003Apr/0181.html
USE CASE 13/4/03 And further responses public-ws-chor/2003Apr/0184.html
USE CASE 14/4/03 And more public-ws-chor/2003Apr/0189.html
USE CASE 14/4/03 And yet more public-ws-chor/2003Apr/0194.html
USE CASE Monica Martin 22/4/03 Buyer/seller as two BP and as one BP AlternativePaths_mm1_042103.doc