Showing posts with label Use case description. Show all posts
Showing posts with label Use case description. Show all posts

Sunday, January 27, 2013

Use case description


A use case description typically uses a template. There are many templates available online or you can make your own.

Each template contains common fields such as:

  • The actors
  • The trigger
  • Relationship details such as includes, extends and generalisations
  • Normal flow of events
  • Alternate of events
  • Exceptional flow of events
  • Assumptions
  • Notes

The use case description informs the use case diagram.

Use cases

A use case represents a single scenario; showing the interactions of users and other systems with a system.

A use case is typically developed as a use case description and a use case diagram.

Actors and Goals
Use cases are derived from the the roles that users play, rather than with users themselves. For this reason, use case users are called 'actors'.

Actor notation

In a use case diagram, the notation for an actor is a stick figure.

Each actor has a goal. This goal is typically the scenario of the use case.

Use case description
A use case description is a text based description of the interactions by the actors. The description comes from requirements analysis activities conducted by the project team - interviews, observation, etc.

Use case diagram - UML
A use case diagram is an illustrative description of the interactions by the actors with the system. The production of the use case diagram is informed by the use case description.

Use case diagram: Login

The system boundary
The blue box is the system with which external actors will interact.

Use case
Each use case is represented as an oval with a verb-noun description. In the Log in use case, some verb-noun descriptions include Enter account details and View Dashboard.


use case notation


The use case represents a process that the actor must interact with to achieve the goal.

Extends
A use case may be extended where an alternate course of action may be conditionally required. In the Log in use case, View dashboard is extended by Update subscription. 


Extends notation


If the subscription requires updating, the Update subscription use case is triggered.

Includes
A use case may include another process by default. In the Log in use case, Update subscription includes Provide payment.

Includes notation

Includes are used where one use case necessarily includes another use case.

Generalisation
Generalisation is shown where there are specialised types of actors or use cases. A specialised actor; such as New Subscriber, can participate in the same use cases as the Subscriber actor.

Generalisation notation : actors
Generalisation notation : use cases
A hollow head arrow is used to show that one actor or use case is a specialisation of a generalisation.

Associations
Associations are shown between actors and use cases using a straight line. It is also possible to show the multiplicity of the association.

See also
"From Goals to Use Cases" ( http://bit.ly/WqI2FF )
"Applying UML And Patterns - Chapter 6: Use Cases" ( http://bit.ly/WqIqUC )
"Alistair.Cockburn.us | Use case fundamentals" ( http://bit.ly/WqVcTb )