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: From Use Case sub-group - Linking of Issues and Requirements back touse cases

Am resending to include all the folks who've expressed interest in the issues/requirements process.
I'd like to have a call on the issues/requirements process -  I think the best timing to keep us within reasonable hours for all time zones is 4pm eastern - let me know if you can participate.  
Regards, Diane
IBM  Dynamic e-business Technologies
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123

"Husband, Yin-Leng" <yin-leng.husband@hp.com>

06/18/2003 08:16 AM

        To:        "Husband, Yin-Leng" <yin-leng.husband@hp.com>, "Jeff Mischkinsky" <jeff.mischkinsky@oracle.com>, "Yaron Y. Goland" <ygoland@bea.com>, "Dieter Roller" <ROL@de.ibm.com>, "Furniss, Peter" <Peter.Furniss@choreology.com>
        cc:        Diane Jordan/Raleigh/IBM@IBMUS, <wsbpel-uc@lists.oasis-open.org>, "John Evdemon" <jevdemon@microsoft.com>, "Fletcher, Tony" <Tony.Fletcher@choreology.com>, "Ben Bloch" <ben_b54@hotmail.com>, "Harvey Reed" <hreed@sonicsoftware.com>, "George Brown" <george.w.brown@intel.com>, "Rajesh Manglani" <rmanglani@uc-council.org>, <sazi@bea.com>, <sallystamand@yahoo.com>
        Subject:        From Use Case sub-group - Linking of Issues and Requirements back to use cases

Hi Jeff & the Issues and Requirements sub-group,

Also from the Use Case sub-group telcon, I took an action to liaise with
your group regarding synchronising the process of collecting

In the telcon, I pointed out that the example use case looked more like
a requirement description to me.  The group discussed that the purpose
of collecting use cases is to harvest requirements so our group would be
processing use case submissions and turning them into requirements for
accepted instances.

So we either need to have a common requirements collection process for
both groups, or have only one group handle requirements collection but
formulate how and which group derive requirements from use cases.

There may be an additional need to define what constitues a use case
submission, and what constitues a requirements submission.

Jeff, is it easier for us to have a call to discuss?

Yin Leng

-----Original Message-----
From: Fletcher, Tony [mailto:Tony.Fletcher@choreology.com]
Sent: Wednesday, 18 June 2003 8:33 PM
To: Jeff Mischkinsky; Yaron Y. Goland; Dieter Roller; Furniss, Peter
Cc: Diane Jordan; wsbpel-uc@lists.oasis-open.org; John Evdemon; Ben
Bloch; Harvey Reed; George Brown; Rajesh Manglani; sazi@bea.com;
sallystamand@yahoo.com; Husband, Yin-Leng
Subject: From Use Case sub-group - Linking of Issues and Requirements
back to use cases

Dear Jeff - and others on the WSBPEL Requirements and Issues sub-groups,

Firstly, this message probably has not gone to all the members of the
Requirements and Issues sub-groups - Jeff could you pass on if

Secondly - for information - a Use case sub-group mailing list has now
been set up.  Members of the Use case sub-group should receive this mail
twice, once directly and once via this new list.  If it works we can
just use the list in future for mails to the Use case sub-group.

The WSBPEL Use case sub-group had its first Telecon yesterday under the
chairmanship of John (Evdemon).  I had an action to write this mail to
the Issues and Requirements sub-groups.

I made the point that Use cases may well (/should) give rise to one, or
more, issues and / or requirements (where we understand that an issue is
a potential 'problem' that has been raised that the TC has not yet
resolved whether to tackle and if so how to tackle - resolved issues
will include this determination, whereas a requirement, when agreed, is
something the TC has agreed needs to be addressed somehow in the

Likewise, each issue and requirement should be supported by one, or
more, use cases.

We therefore see a need for linking use cases to issues and
requirements, and vice versa.  We hope you will agree with this.

You should receive other messages from the use case group on the
procedures we currently intend to use.  We would like to correlate these
with your procedures, particularly so we can work out the cross linking
at the appropriate juncture.

Best Regards     Tony
A M Fletcher

Cohesions 1.0 (TM)

Business transaction management software for application coordination

Choreology Ltd., 13 Austin Friars, London EC2N 2JX     UK
Tel: +44 (0) 20 76701787   Fax: +44 (0) 20 7670 1785  Mobile: +44 (0)
7801 948219
tony.fletcher@choreology.com     (Home: amfletcher@iee.org)

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