Uml Tutorial Home
- What is UML?
- What are Use Cases?
- Why Use Cases?
- Use Case
- What does a Use Case Diagram look like?
- Use Case Description
- Use Case Relationships
- Guidelines for creating Use Cases
- Class Diagram
- Example Class Diagram
- Identifying Attributes
- Tips for Creating Class diagrams
- Further Resources
- Members (2220)
- Member Articles ( 1 )
- Discussion (3)
- Q & A ( 1 )
- - Ask Question
- - Questions
- - Unanswered Questions
There are several types of templates out there for describing Use Cases. It is important not to go overboard and also essential to agree on one and get on with the task at hand.
A Use Case will normally have a narrative description of the flow of events that a user will follow in order to complete a process.
Name: use case name
Brief Description / Goal: what is to be achieved
Flow of events for <name> use case
Preconditions: what the situation must be before the use case can take place
Main Flow: the basic successful flow of events
Sub Flow (if applicable): subordinate flows
Alternative flows: variations in business conditions
Trigger: the event that causes the use case to happen (usually by an actor)
Example Main Flow
Customer requests to place an order
Customer selects product,quantity
System provides availability and price
Customer agrees to proceed
Customer selects delivery time
Customer provides payment details
System places order and allocates order number
System displays order number