Wiki
This website is a wiki. If you like and use our processes, techniques and tools, please add your experience and best practices. Just register and share.


Contents


User


Smart


Community

















Stereotypes. Select (2)

RSS
Modified on Monday, 24 November 2008 21:43 by rwolff Categorized as Uncategorized
A Select type of use case represents the functionality for selecting a single item from a list of business objects from one class, with some added functionality, such as filtering on one or more property values of the class. For example, selecting a service contract from all service contracts with the status 'Pending'.
The name use cases marked with this stereotype would be like 'Select ' where the noun is a singular. This will match with the post condition of the happy flow. An example use case name is 'Select Person'. In an Multi Select the noun would be a plural: 'Select Persons'

Robert de Wolff


Preconditions

-none-

Steps

A Select performs the following basic steps.
  • Start. The system initiates the use case.
  • Show filter criteria. The system presents the form with the filter criteria.
  • Enter filter values. The user enters the values for the filter criteria.
  • Get items. The system gets the items for which the filter criteria apply.
  • Show items. The system presents the form (any type, such as a web page, a Windows form, a Flash form) and shows the filter criteria and values and the list of items for which these values apply.
  • Select item. The user selects a single item from the list.
    • Alternative flow - Cancel:
      1. The user selects the action Cancel.
      2. Finish. The system finishes the use case without passing back an item.
    • Alternative flow - New:
      1. The user selects the action New.
      2. Finish. The system finishes the use case by passing back a new item with default property values.
  • Finish. The system finishes the use case by passing back the selected item.
    ===Postconditions===
  • A single item of the results list is selected.
  • The use case is canceled by the user
    These conditions are XOR
    ===Characteristics===
    A Select follows the following characteristics:
  • Form. Form to the display the Filter and List panels. Can be any type of form.
  • Filter. Panel to display the filter criteria.
  • List. Panel to display the List of items to select from.
    ===Variations===
    Extensions to this stereotype can be:
  • Search. Ask 'How many items could be shown?'. When it's possible that more than 10 items are shown often a 'Search' stereotype is identified.
  • Multi Select. Being able to select more than just a single item from the list, e.g. selecting the regions an account manager works in. Add 1 to the complexity.
    ===Estimation (2 - Moderate)===
    By default, a Select is estimated at 2. If multiple items need to be selected choose 3.