Re: [wsbpel] RE: Requirements and Scope Documents?

[Ron Ten-Hove <Ronald.Ten-Hove@Sun.COM>]

Title:

John,

    I for one would like to see the author's requirements list. A lot of
e-mail has been expended trying to reverse-engineer this very thing. Fundamental
issues like "is it an execution language or a modelling language" might be
answered by a look at the original requirements the authors were addressing.

Cheers,
-Ron

John Evdemon wrote:
> [Copying the WSBPEL TC mailing list...]
>
> Sid,
>
> Why are these documents needed?  What purpose will they serve?
>
> Since we are revising an established specification I'm not sure why a
> requirements document is needed.  The charter also defines our scope in
> fairly simple terms.  
>
> Can someone clarify the need for requirements and scope documents?
>
> Thanks!
>
> JohnE
>
>
>
> > -----Original Message-----
> > From: saskary@nuperus.com [mailto:saskary@nuperus.com]
> > Sent: Tuesday, June 24, 2003 1:38 PM
> > To: Diane Jordan
> > Cc: Yaron Y. Goland; James Bryce Clark; John Evdemon
> > Subject:
> >
> > Diane,
> > As for the agenda for tomorrow, could you please add the motion for a
> > requirements and scope document ( as per use case and reqs joint conf
> > call)?
> >
> > Thanks,
> >
> > Sid.
> >   
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wsbpel-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wsbpel-help@lists.oasis-open.org