Scribd
Upload
34 views

Use Case Model

The document discusses use case modeling and provides examples. It defines use cases as representations of how users interact with a system to perform tasks. Use cases describe high-level functional requirements without revealing internal structure. For a library system, example use cases include issuing, returning, and querying books. Use case diagrams visually depict the use cases and actors through ellipses and stick figures within a system boundary rectangle. Accompanying text elaborates on the diagrams.

Uploaded by

mbatechcs
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
34 views

Use Case Model

The document discusses use case modeling and provides examples. It defines use cases as representations of how users interact with a system to perform tasks. Use cases describe high-level functional requirements without revealing internal structure. For a library system, example use cases include issuing, returning, and querying books. Use case diagrams visually depict the use cases and actors through ellipses and stick figures within a system boundary rectangle. Accompanying text elaborates on the diagrams.

Uploaded by

mbatechcs
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Use Case Model

Prepared By:
Upendra Verma
MPSTME Shirpur Campus
[email protected]

Use Case Model


The use case model for any system consists of
a set of use cases.
Intuitively, use cases represent the different
ways in which a system can be used by the
users.
A simple way to find all the use cases of a
system is to ask the question: What the users
can do using the system?
[email protected]

Thus for the Library Information System


(LIS), the use cases could be:
issue-book
query-book
return-book
create-member
add-book, etc
[email protected]

Use cases correspond to the high-level functional


requirements.
The use cases partition the system behavior into
transactions, such that each transaction performs
some useful action from the users point of view.
To complete each transaction may involve either a
single message or multiple message exchanges
between the user and the system to complete.

[email protected]

Purpose of use cases


The purpose of a use case is to define a piece of
coherent behavior without revealing the internal
structure of the system.
The use cases do not mention any specific
algorithm to be used or the internal data
representation, internal structure of the software,
etc.
A use case typically represents a sequence of
interactions between the user and the system.
These interactions consist of one mainline
sequence.
[email protected]

Representation of use cases


Use cases can be represented by drawing a use
case diagram and writing an accompanying
text elaborating the drawing.
In the use case diagram, each use case is
represented by an ellipse with the name of the
use case written inside the ellipse.
All the ellipses (i.e. use cases) of a system are
enclosed within a rectangle which represents
the system boundary.
[email protected]

The different users of the system are


represented by using the stick person icon.
Each stick person icon is normally referred to
as an actor. An actor is a role played by a user
with respect to the system use.
It is possible that the same user may play the
role of multiple actors. Each actor can
participate in one or more use cases.
[email protected]

The use case model for the Tic-tac-toe


problem is shown in fig.

[email protected]

The use case model for the


Supermarket Prize Scheme

[email protected]

[email protected]

10

You might also like