Skip to content
quaat edited this page Nov 22, 2012 · 1 revision

The proposed template for defining Use Cases

1. Name	                                Name of the Use Case
2. Scope	                        The system under design
3. Primary Actor	                Calls the system to deliver its services
4. Stakeholders and Interests	        Who cares about this use case? What do they want out of it?
5. Precondition	                        What must be true on start?
6. Successful operation/completion	The state of the world if goal succeeds
7. Unsuccessful execution	        Consequence if the system fails to deliver
8. Main Success Scenario	        A typical, unconditional happy path scenario of success
9. Special requirements	                Related non-functional requirements
10. Technology & Data Variations List   Varying I/O methods and data formats
11. Misc	                        Open issues, other comments

Clone this wiki locally