A
Simple Select type of use case represents the functionality of selecting a single instance from a limited list of items, such as selecting a type of contract (if there is a limited number of contract types), or a "provincie" in the Netherlands (of which there are 12). In general, if the instance can be selected from a form without heavy scrolling through the items, and without heavy querying (using all kinds of joins or unions to represent the data) it is considered a
Simple Select.
Preconditions
-none-
Steps
A
Simple Select performs the following basic steps.
- Start. The system initiates the use case.
- Get items. The system gets the items to represents in the list on the form.
- Show items. The system presents the form (any type, such as a web page, a Windows form, a Flash form) and show the list of items.
- Select item. The user selects a single item from the list.
- Alternative flow - Cancel:
- The user selects the action Cancel
- Finish. The system finishes the use case without passing back an item.
- Finish. The system finishes the use case by passing back the selected item to the calling use case.
Postconditions
- A single instance of a business object is returned
- The use case is canceled by the user
These conditions are XOR
Characteristics
A
Simple Select follows the following characteristics:
- Form. Form to the display the List panel. Can be any type of form.
- List. Panel to display the List of items to select from.
Variations
Extensions to this stereotype can be:
- Simple Multi Select. Being able to select more than just a single item from a limited list, e.g. selecting the regions an account manager works in. Add 1 to the complexity.
- Select. Use this stereotype if it is functionally required that the user can create a new instance of the class of objects show in the list.
Estimation (1 - Piece of cake)
By default, a
Simple Select is estimated at
1. If joins are inevitable or multiple items need to be selected choose
2.