OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel-uc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [wsbpel-uc] Input on scenarios


Attached is the next rev of docs, where I took Sally's doc, and took into
consideration Simpl-eb and WSI use cases.

Here is where I think we stand:

1. We recognize that we need to start at a high level, then work down to
2. We decided to focus on usage scenarios as high level and use cases as
technical. I added another higher level to group usage scenarios, I am
calling these "business flows" such as "replenish stock". There can be many
ways (usage scenarios) to replenish stock.
3. Within a usage scenario we will ultimately want to drill down to use
cases and BPEL. Here, we can take a usage scenario, and vary the
participants to test how invariant the BPEL turns out to be.

What is attached:

1. Guidelines - Our previous consensus for how to proceed
2. Catalogue - A proposed draft of a set of business flows, usage scenarios
and technical use cases. It is is not 100% complete, we should review before
proceeding. I incorporated Sally's template into this doc. Note also that we
can put any business eco-system assumptions into this catalogue, such as
assumed XML schemas, various actors, owned by legal entities, etc.


-----Original Message-----
From: Monica Martin [mailto:monica.martin@sun.com] 
Sent: Sunday, August 10, 2003 4:06 PM
To: wsbpel-uc@lists.oasis-open.org
Cc: Sally St. Amand
Subject: Re: [wsbpel-uc] Input on scenarios

Sally St. Amand wrote:

> Harvey and other UC subgroupies-
> As a follow on to my earlier email I am attaching a template that I 
> propose we discuss at our next subgroup telecon call. Harvey, I did 
> not know if you intended to take additional steps beyond what you have 
> done (& are doing) on the usage scenarios.
> As we discussed, use cases will emanate from the scenarios. Some of 
> which we already have; for example the Simpl EB. If we are going to 
> solicit use cases from a broad audience we will need a template as to 
> what we need.
> I took the template John developed, added in elements from the WS-I 
> submission, the doc Ben sent out earlier, et al and constructed this 
> template.
> First and foremost it needs to be understandable to someone who 
> stumbles on to the BPEL TC website and thinks they have a contribution 
> to make. If the template doesn't meet that test we need to make it so.
> I labeled it as I did because one of the perspectives we need to make 
> sure doesn't get lost is "usage centered design" and testing the spec.
> As I said my focus was on getting a format we all think will do the 
> job of soliciting examples and serving up the examples to the full TC. 
> Based on the work you are doing, a template and processes we have 
> already described, e.g. Voting on Use Cases, we could have a 
> methodology for acting that we can present to the TC? Including once 
> the subgroup agrees on the template, load in an actual (the Simple EB 
> seems prime).
> Also, a thread amongst ourselves to get a document more refined by 
> next Monday's call might save some time on the call.
> Sally
mm1: First, thank you for doing this Sally.  Secondly, on the template 
as provided:

    * Suggest alternate paths or flows not just outcomes. The use case
      may have some different events that impact the outcome. We need to
      document both.
    * May be associated with 0...n issues.
    * May also be associated with other use cases and usage scenarios
      (overlaps likely will occur).
    * Suggest you separate any notes/assumptions and requirements
      section.  Do we perceive the requirements to be only non-functional?


WSBPEL Usage Scenario Guidelines [v04].doc

WSBPEL Usage Scenario Catalogue [v04].doc

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]