My $0.2.... Once we define the scenario and go trough the actually go through design, develop, build, install, run and debug it and manage the steps, could we create a blog about it ? Something like those guys that go on a journey and blog each steps ? I think this might be interesting to people that would work on their own scenarios in their business or for pleasure.
-- Luciano Resende http://people.apache.org/~lresende On 1/17/07, Dan Murphy <[EMAIL PROTECTED]> wrote:
To generate some discussion of how we would like this done (in other words, I'm not too happy with what I did) I wrote down some scenarios based on a possible example. Since I hope these sit above java and so I had a clean sheet I created : http://wiki.apache.org/ws/Tuscany/Scenarios First thing you will notice is that I am a hypocrite as earlier in this thread I said: "avoid a scenario that runs along the lines of "develop a service component" and instead go for a more specific (concrete scenario/) user story of "develop a service component using Java" Second thing is that it doesn't really highlight why SCA or Tuscany... It reads to me like a standard integration scenario, but I believe could illustrate what a person might try first with Tuscany, so I hope it would be something that they can do without having to really think too hard :) Where for example I think we would show value in Tuscany/SCA is a later scenario of composing and or changing (eg. either I want to change the implementation I use or it is deployed somewhere else). This, in my mind, is where Tuscany starts to show value..... Anyhow, I also like Sebastien's suggestion so I'll try now to achieve one of the scenarios and report back :) Cheers, Dan
