Jump to: navigation, search

Difference between revisions of "Swordfish Documentation: User Stories"

(New page: Under construction! == Eclipse SOA Runtime == {| border="1" cellpadding="3" cellspacing="0" width="100%" |+'''User Stories''' |- style="background:#efefef;" |width="10*" |'''As an''' |...)
 
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
The simple form of user stories is a good starting point for requirements identification and prioritization. <br/>
 +
We have choosen the following form:
  
Under construction!
+
<div style="margin:10px;background-color:#e0e0ff;border:1px solid blue;padding:20px;">
 +
'''In an''' Eclipse SOA ''Role'' <br/>
 +
'''I would like to''' ''do something'' with Swordfish <br/>
 +
'''so''' I provide my ''motivation'' or reasons here <br/>
 +
</div>
  
== Eclipse SOA Runtime ==
+
We have identified user stories for the following roles
  
{| border="1" cellpadding="3" cellspacing="0" width="100%"
+
* [[Swordfish_Documentation:_User_Stories:_Service_Developer | Eclipse Service Developer]]
|+'''User Stories'''
+
* [[Swordfish_Documentation:_User_Stories:_BPEL_Developer | Eclipse BPEL Developer]]
 +
* [[Swordfish_Documentation:_User_Stories:_SOA_Administrator | Eclipse SOA Administrator and Operator]]
 +
* [[Swordfish_Documentation:_User_Stories:_Framework_Developer | Eclipse Swordfish Framework Developer]] (coming soon)
  
|- style="background:#efefef;"
+
See also [[Swordfish_Documentation:_Product_Backlog | Swordfish Product Backlog]]
|width="10*" |'''As an'''
+
-------------------------
|width="10*" |'''I would like to'''
+
Return to [[Swordfish | Swordfish Wiki Home]] <br/>
|width="10*" |'''so that'''
+
Go to [[Swordfish_Documentation | Swordfish Documentation]] <br/>
|width="10*" |link to backlog item(s)
+
Go to [[Swordfish_Documentation:_Sprint_Plan | Swordfish Galileo (Planning)]] <br/>
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''run''' a JAX-WS Service Consumer standalone within Eclipse,
+
|width="10*" | I can test my code immediately
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''run''' a JAX-WS Service Consumer in a Servlet Engine within Eclipse,
+
|width="10*" | I can test my code immediately
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''deploy''' a standalone JAX-WS Service Participant into the running Target Platform outside of Eclipse,
+
|width="10*" | I can test my code immediately without needing to restart the target platform (hot deployment).
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''start''' a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse,
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''run''' a JAX-WS Service Consumer in a JEE Application Server outside of Eclipse,
+
|width="10*" | I can test my code in a distributed environment.
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''start''' a standalone JAX-WS Service Provider in the Target Platform outside of Eclipse,
+
|width="10*" | so that I can test my code in a distributed environment.
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | I would like to  start a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse,
+
|width="10*" | so that I can test my code in a distributed environment.
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
 
+
 
+
As an Eclipse Service Developer
+
I would like to  start a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse,
+
so that I can test my code in a distributed environment.
+
 
+
As an Eclipse Service Developer
+
I would like to start a JAX-WS Service Provider in a JEE Application Server
+
so that I can test my code immediately.
+
 
+
As an Eclipse Service Developer
+
I would like to select the consumer policy dynamically,
+
so that I can invoke service calls with different policies from the same consumer
+
 
+
As an Eclipse Service Developer
+
I would like to reference message schemas from the WSDL,
+
so that I do not need to modify the WSDL when something in the message schemas changes AND I can reuse the same schemas for multiple WSDLs.
+
 
+
As an Eclipse Service Developer
+
I would like to use dynamic policy based Service lookup
+
so that I do not need to implement QOS within the Business participant BUT still can offer different Service Levels for the Same service i.e. different security levels.
+
 
+
As an Eclipse Service Developer
+
I would like to use http and https as transport protocol.
+
so that I can utilize the web infrastructure.
+
 
+
As an Eclipse Service Developer
+
I would like to use jms as transport protocol,
+
so that I can provide a reliable transport.
+
 
+
As an Eclipse Service Developer
+
I would like to be able to use any other transport protocol offered by ServiceMix
+
so that I can integrate easier with legacy Systems.
+
I am aware that restrictions apply regarding policies influencing the wire format.
+
 
+
As an Eclipse Service Developer
+
I would like to utilize message streaming
+
so that I am able to provide high performance applications with low roundtrip times even for larger amounts of data transferred.
+

Latest revision as of 03:04, 3 June 2009

The simple form of user stories is a good starting point for requirements identification and prioritization.
We have choosen the following form:

In an Eclipse SOA Role
I would like to do something with Swordfish
so I provide my motivation or reasons here

We have identified user stories for the following roles

See also Swordfish Product Backlog


Return to Swordfish Wiki Home
Go to Swordfish Documentation
Go to Swordfish Galileo (Planning)