Use Case- depicts a set of activities performed to produce some output result.

Each use case describes how an external user triggers an event to which the
system must repond.

TRIGGER EVENT
THE SYSTEM RESPONDS
PERFORMS ACTIONS BASED ON
THE USE CASE
RETURNS TO THE WAITING STATE

*There can be small process or complex systems.

*the use case describes what the system will do from the users perspective.
Therefore, it is critical to involve the user in the creation of the use case so
that the user understands the interactions planned for the new system.
The user helps to ensure that no essential steps or tasks are omitted from the
use case and that rare, special circumstances are included
Creation of use cases is often done as a part of interview sessions with users
and as a part of JAD sessions.

ELEMENTS OF A USE CASE

Basic Information:

Name-simple yet descriptive

Number-sequential number for reference
Description- use cases purpose
Priority
Actor/User Role- the person, another
software system, or a hardware device
that interacts with the system to achieve
a useful goal
Trigger- event that causes the se case to
begin
-maybe external or temporal
trigger

Preconditions- defines the state the system needs to be in before each use
case begin.

Normal Course- description of the major steps that are performed to execute
the response to the event, the inputs used for the steps, and the outputs produced
by the steps.
-include a column in which the information that flows in or out of
the steps is recorded.

Alternative Courses- the steps followed for alternative paths through the
use case are outlined. Alternative courses are included to depict branches in logic
that also will lead to a successful conclusion of the use case.

Postconditions- define the final products of this use case; serve to define the
preconditions for the next use case in the series.

Exceptions- describe any error conditions or exceptions that may occur as the
use case steps are performed. These are not normal branches in decision logic, but
are unusual occurrences or errors that could potentially be encountered and will
lead to an unsuccessful result

Summary Inputs and Outputs- final section of the use case

summarizes the set of major inputs and outputs to the steps of the use case. Each

of the major inputs and outputs to the use case are listed, along with its source or
destination.

Additional Use Case Issues Some organizations may include additional

sections on their use case forms. If appropriate, it may be helpful to include sections
devoted to:
Frequency of use Business rules Special requirements Assumptions Notes
and issues

Alternative Use Case Formats

Fully dressed use cases are especially valuable when:
User representatives are not closely engaged with the development team
throughout the project.
The application is complex and has a high risk associated with system failures.
Comprehensive test cases will be based on the user requirements.
Collaborating remote teams need a detailed, shared understanding of the user
requirements.

The project team may also decide that a more

acceptable.

casual use case format is

Use Cases and the Functional

Requirements

Use cases do explain the users interaction with the system, but they omit a
lot of details that are necessary to know before the system can be developed.
only convey the users point of view. Behind the scenes processing details are
probably not included in the use case.
Transforming the users view into the developers view by creating functional
requirements is one of the important contributions that the systems analyst
makes to the development project

USE CASES AND TESTING

giving the testing/quality assurance personnel an early understanding of

the system under development.
the testing personnel can readily identify elements of the tests they will
want to perform when the system enters testing.
When it comes time to actually perform the tests, the testing personnel
are well prepared and not forced to develop and perform the tests in a
rush.
the quality assurance personnel often are able to make helpful
suggestions about the system and it is valuable to gain this feedback
early in the development process.