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

Forum






Stereotypes. Manage (3 - Average)

RSS
Modified on Monday, 27 October 2008 17:39 by mdriesse Categorized as Uncategorized
An “Manage” type of use case represents the functionality for that manages maintenance for a single item of a business class. This use case contains additional functionality, such as business rules, comparisons, authorization.

Preconditions

-none-

Steps

An “Manage” performs the following basic steps:
  • Start. The system initiates the use case.
  • Get object instance. The system takes the business object provided by the calling use case.
    1. Alternative flow - No object instance available:
      • If an object instance is not provided by the calling use case, the system starts a sub-function use case which can provide an instance of an object. The use case stereotypes Simple Select, Select, Search, Extended Search provide this kind of functionality.
  • Present object instance. The system presents a single object instance of a business class to the user in a form (any type, such as a web page, a Windows form, a Flash form).
    • Alternative flow - No object instance provided::
      1. The called sub-function use case was canceled and did not provide a business object to manage.
      2. Finish. The system finishes the use case.
  • Merge node 1. Re-entry point for alternative flows
  • Maintain object instance. The user maintains the properties of the object instance by changing its property values.
  • Save object instance. The user selects the action Save
    • Alternative flow - Cancel:
      1. The user selects the action Cancel
      2. Finish. The system finishes the use case without persisting the changes to the properties of the object instance.
    • Alternative flow - Remove:
      1. The user selects the action Remove to indicate the object instance must be removed from the system.
      2. Validate removal. The system validates if the object instance can be removed from the system, given the context and the current object state.
      3. Alternative flow - Object removal violates business rules:
        • If the removal of the objects violates against the business rules which apply to the business class in the given context and object state the system presents appropriate message(s) to the user which should be helpful to fix the problem(s).
        • Continue at Merge node 1.
      4. Remove object. The system removes the object instance from the system.
      5. Finish. Finish the use case.
  • Validate object instance. The system validates the changes to the object against the business rules which apply to the business class in the given context and object state.
    • Alternative flow - Changed object violates business rules:
      1. If the changes to the object state violate against the business rules which apply to the business class in the given context and state the system presents appropriate message(s) to the user which should be helpful to fix the problem(s).
      2. Continue at Merge node 1.
  • Save changed object. The systems persists the changed business object.
  • Finish. The system finishes the use case.

Postconditions

  1. A single instance of a business object is maintained by the user
  2. A single instance of a business object is removed by the user
  3. The use case is canceled by the user
These conditions are XOR

Characteristics

An Manage follows the following characteristics:
  • Form. Form to the display the Object panel. Can be any type of form.
  • Object. Panel to display the properties of the business object.

Variations

Extensions to this stereotype can be:
  • List Details. The stereotype use case that contains a list of items from a business class and that manages a single instance selected from this list.
  • Master Detail. The stereotype use case that manages a single item from a business class and a list of items from an associated business class, such as order-orderline.
  • Define. Simular to a Manage use case, but without, selection extension & database access. The calling use case needs to provide a business object to manage.

Estimation (3 - Avarage)

By default, a Manage is estimated at 3. (this is just an example)
  Name Size