Dan Murphy wrote:
Thanks for the pointer Ray,
It looks like a great start... Do you (all) think we should assume SCA is
being used/ the desired solution ?
The scenarios would, I hope, show how SCA helps solve a problem,
though they
could be useful to see if/where SCA has gaps and where Tuscany can
provide
value beyond being a pure SCA implementation.
I was thinking : Technology independent scenario -> to how/if SCA &
Tuscany
supports it -> example(s) of how to do it
This could help identify any SCA/Tuscany gap and help give Tuscany
developers an indication of the complexity of performing a task /
solving a
problem. For example, if we discover that to perform a scenario using
Tuscany required 39 steps and multiple decision points it might be a good
area for simplification (or failing that tools).
However, if the consensus is that SCA is the starting then I'm happy
to go
along with this. WDYT ?
Cheers,
Dan
On 16/01/07, Raymond Feng <[EMAIL PROTECTED]> wrote:
+1.
I think it would be useful to define a set of SOA scenarios that
Tusany is
developed to support. Overtime, these senarios can be implemented using
Tuscany and become part of the integration suite. We can use them as one
way
to measure the functional completeness for Tuscany.
FYI: There are some initial efforts documented at the following wiki
page:
http://wiki.apache.org/ws/Tuscany/TuscanyJava/Scenarios
Thanks,
Raymond
----- Original Message -----
From: "Dan Murphy" <[EMAIL PROTECTED]>
To: "Tuscany Developers" <[email protected]>; "Tuscany Users"
<[email protected]>
Sent: Monday, January 15, 2007 4:39 AM
Subject: SOA Scenarios
> Hi,
> There have been a number of postings about scenarios. For example:
>
> - In July
> http://www.mail-archive.com/[email protected]/msg04490.html
> about JSF using Tuscany
> - In Nov
>
http://www.mail-archive.com/[email protected]/msg00319.htmlas
> part of the what next for C++
> - More recently
>
http://www.mail-archive.com/[email protected]/msg00416.htmland
> -
http://www.mail-archive.com/[email protected]/msg12818.html
>
> Would it be useful to document and maintain a set of scenarios that
> Tuscany
> does/will support?
>
> These could be used to validate and help guide what get developed,
rather
> than relying "what next ?" postings (more permentant record). It could
> also
> be used to help identify complexity and completeness. Lastley it might
> also
> make it clearer to differenticate Tuscany from similar projects.
Perhaps
a
> way to kick off would be to start gathering some user stories (rather
than
> more abstract scenarios)
>
> WDYT ?
>
> Cheers,
> Dan
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I think it would be very valuable to pick a not too complex scenario in
the eBusiness or Web 2.0 category for example and actually go through
the steps to design, develop, build, install, run and debug it, manage
it. You will probably find holes, user experience pain points and
possible improvements. Documenting this and reporting the problems you
find as JIRA issues will be very valuable IMO and will help the Tuscany
community define a clear roadmap for the project.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
