Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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 12: | Line 12: | ||
* [[Swordfish_Documentation:_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]] | * [[Swordfish_Documentation:_User_Stories:_BPEL_Developer | Eclipse BPEL Developer]] | ||
| − | * [[Swordfish_Documentation:_User_Stories:_SOA_Administrator | Eclipse SOA Administrator]] | + | * [[Swordfish_Documentation:_User_Stories:_SOA_Administrator | Eclipse SOA Administrator and Operator]] |
* [[Swordfish_Documentation:_User_Stories:_Framework_Developer | Eclipse Swordfish Framework Developer]] (coming soon) | * [[Swordfish_Documentation:_User_Stories:_Framework_Developer | Eclipse Swordfish Framework Developer]] (coming soon) | ||
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
- Eclipse Service Developer
- Eclipse BPEL Developer
- Eclipse SOA Administrator and Operator
- 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)