RE: [tamie] uc3, with second variant

["Jacques R. Durand" <JDurand@us.fujitsu.com>]

Dale:

 

Trying to clarify the events (and associated conditions) that govern the transitions:

 

In terms of events, which event (s) do you see associated with Cancellation?

E.g. if Buyer cancels, will there be always a "cancellation" message? (or another type of event?)

 

Also, the transition from Cancellation10 to Failure10: what would this AnyProtocolFailure event be ? (isn't "cancellation" a final state?)

 

Thanks,

Jacques

 

 

 

---

From: Moberg Dale [mailto:dmoberg@axway.com]
Sent: Monday, April 13, 2009 3:53 PM
To: tamie@lists.oasis-open.org
Subject: [tamie] uc3, with second variant

Uc3 is a sample of business processes derived from those processes enabled by UBL 2.0 messages for Purchase Order Management. I have consulted Stephen Green’s paths of supported processes, and think that Cancellation could (by bilateral agreement) be used by the buyer after Acceptance (and probably with some time limit that I have not put into the model yet.)

 

Here is a simplified graphic that can assist in discussion if uc3 makes it on to the agenda for tomorrow.

 

The ebBP and intermediate LTS xml file are still being worked on to add support for ebBP PreConditions and other similar ebBP elements to the transition “labels”.  So the label on the edge between start10 and Cancellation10 should be “Accept” (and not simply “true”) which would then mean that the state can be entered only when the PO request’s response has been Accepted. This process model provides some “slightly constrained” indeterminism to challenge the Event Testing/Monitoring Scripts that are to be generated off the models.