Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Swordfish Documentation: User Stories"
Line 13: | Line 13: | ||
* [[Swordfish_Documentation:_User_Stories:_BPEL_Developer | Eclipse BPEL Developer]] | * [[Swordfish_Documentation:_User_Stories:_BPEL_Developer | Eclipse BPEL Developer]] | ||
* [[Swordfish_Documentation:_User_Stories:_SOA_Administrator | Eclipse SOA Administrator]] (coming soon) | * [[Swordfish_Documentation:_User_Stories:_SOA_Administrator | Eclipse SOA Administrator]] (coming soon) | ||
+ | * [[Swordfish_Documentation:_User_Stories:_Framework_Developer | Eclipse Swordfish Framework Developer]] (coming soon) | ||
See also [[Swordfish_Documentation:_Product_Backlog | Swordfish Product Backlog]] | See also [[Swordfish_Documentation:_Product_Backlog | Swordfish Product Backlog]] |
Revision as of 12:26, 27 March 2009
The simple form of user stories is a good starting point for requirements identification and prioritization.
We have choosen the following form:
As an Eclipse SOA Role
I would like to do something with Swordfish
so that I provide my motivation or reason here
We have identified user stories for the following roles
- Eclipse Service Developer
- Eclipse BPEL Developer
- Eclipse SOA Administrator (coming soon)
- Eclipse Swordfish Framework Developer (coming soon)
See also Swordfish Product Backlog
Return to Swordfish Wiki Home
Go to Swordfish Documentation
Go to Swordfish Galileo (Planning)