Jump to: navigation, search

Difference between revisions of "Swordfish Documentation: User Stories"

 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Under construction!
+
The simple form of user stories is a good starting point for requirements identification and prioritization. <br/>
 +
We have choosen the following form:
 +
 
 +
<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>
  
 
We have identified user stories for the following roles
 
We have identified user stories for the following roles
  
[[Swordfish:_User_Stories:_Service_Developer | Eclipse Service Developer]]
+
* [[Swordfish_Documentation:_User_Stories:_Service_Developer | Eclipse Service Developer]]
 
+
* [[Swordfish_Documentation:_User_Stories:_BPEL_Developer | Eclipse BPEL Developer]]
See also [[Swordfish_Documentation:_Product_Backlog | Swordfish Product Backlog]]
+
* [[Swordfish_Documentation:_User_Stories:_SOA_Administrator | Eclipse SOA Administrator and Operator]]
 
+
* [[Swordfish_Documentation:_User_Stories:_Framework_Developer | Eclipse Swordfish Framework Developer]] (coming soon)
{| border="1" cellpadding="3" cellspacing="0" width="100%"
+
|+'''User Stories'''
+
 
+
|- style="background:#efefef;"
+
|width="10*" |'''As an'''
+
|width="10*" |'''I would like to'''
+
|width="10*" |'''so that'''
+
|width="10*" |link to backlog item(s)
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''run''' a JAX-WS Service Participant standalone within Eclipse,
+
|width="10*" | I can test my code immediately
+
|width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]]
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''use the http and https transport protocols''',
+
|width="10*" | I can communicate over the web.
+
|width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]]
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''use jms as transport protocol''',
+
|width="10*" | I can provide a reliable transport.
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''use dynamic policy based Service lookup'''
+
|width="10*" | I can utilize QOS with different service levels for the Same service i.e. different security levels.
+
|width="10*" | [[Swordfish_Documentation:_Registry_Feature | Service Registry Feature]]
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''use http and https as transport protocol''',
+
|width="10*" | I can communicate over the Web.
+
|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*" | '''select the consumer policy''' dynamically,
+
|width="10*" | I can invoke service calls with different policies from the same consumer
+
|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*" | I can test my code in a distributed environment.
+
|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*" | I can test my code in a distributed environment.
+
|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*" | I can test my code in a distributed environment.
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''reference message schemas from the WSDL''',
+
|width="10*" | 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.
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''utilize message streaming''',
+
|width="10*" | I can provide high performance applications with low roundtrip times even for larger amounts of data transferred.
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''start''' a JAX-WS Service Provider in a JEE Application Server
+
|width="10*" | I can test my code in a distributed JEE environment.
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" | '''use any other transport protocol offered by ServiceMix''',
+
|width="10*" | I can integrate easier with legacy Systems. (I am aware that restrictions apply regarding policies influencing the wire format.)
+
|width="10*" | TBD
+
|-
+
|width="10*" | Eclipse Service Developer
+
|width="10*" |
+
|width="10*" |
+
|width="10*" | TBD
+
|-
+
  
== ==
 
 
See also [[Swordfish_Documentation:_Product_Backlog | Swordfish Product Backlog]]
 
See also [[Swordfish_Documentation:_Product_Backlog | Swordfish Product Backlog]]
 
-------------------------
 
-------------------------
Return to [[Swordfish | Swordfish Wiki Home]]
+
Return to [[Swordfish | Swordfish Wiki Home]] <br/>
Go to [[Swordfish_Documentation | Swordfish Documentation]]
+
Go to [[Swordfish_Documentation | Swordfish Documentation]] <br/>
Go to [[Swordfish_Documentation:_Sprint_Plan | Swordfish Galileo (Planning)]]
+
Go to [[Swordfish_Documentation:_Sprint_Plan | Swordfish Galileo (Planning)]] <br/>

Latest revision as of 04: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)