OBJECT ORIENTED ANALYSIS

(Unified Modeling Language)

UML
Use Case Diagram

Rana Talaat Muhammad

 Expected Outcomes
• To explain on Use Case Diagram and how to model system
functionality

System Analysis & Design - Rana Talaat Muhammad 2

 SDLC Object Oriented
Object oriented software development life cycle model namely Unified Process or Rational
Unified Process (RUP). The model was proposed by Booch, Jacobson and Rumbaugh.
It is an iterative process to add or update the components based on feedbacks from the
previous iteration.
RUP has four major phases:
1. Inception
2. Elaboration
3. Construction
4. Transition

System Analysis & Design - Rana Talaat Muhammad 3

 SDLC Object Oriented
One of the artefact during Inception phase is Primary Use Case Diagram.
In this phase, communication with customers takes place to get
requirements.
Use Case Diagram captures the functional requirements of the system.

System Analysis & Design - Rana Talaat Muhammad 4

 Use Case Diagram is used to model a system, the most
important aspect is to capture the dynamic behaviour. Dynamic
behaviour means the behaviour of the system when it is
Use Case Diagram
running/operating.
Now as we have to discuss that the use case diagram is
dynamic in nature, there should be some internal or external
factors for making the interaction.
The diagram is used to model the system/subsystem of an
application. A single use case diagram captures a particular
functionality of a system.
Therefore, to model the entire system, a number of use case
diagrams are used. Therefore, the project’s business value
must be cleared
System Analysis & Design - Rana Talaat Muhammad 5
 Purpose of Use Case Diagrams
The purpose of use case diagram is to capture the dynamic aspect of a
system.
However, this definition is too generic to describe the purpose, as
other four diagrams (activity, sequence, collaboration, and Statechart)
also have the same purpose. We will look into some specific purpose,
which will distinguish it from other four diagrams
Use case diagrams are used to gather the requirements of a system
including internal and external effects. These requirements are mostly
design requirements.

System Analysis & Design - Rana Talaat Muhammad 6

 Purpose of Use Case Diagrams
Hence, when a system is analysed to gather its functionalities, use cases are
prepared and actors are identified. When the initial task is complete, use case
diagrams are modelled to present the outside view.
Use Case Diagram is used to gain better understanding the functionality of the
system at a very high level. In brief, the purposes of use case diagrams can be said
to be as follows:
 Used to gather the requirements of a system.
 Used to get an outside view of a system.
 Identify the external and internal factors influencing the system.
 Show the interaction among the requirements are actors.

System Analysis & Design - Rana Talaat Muhammad 7

 How to Draw UCD

www.lucidchart.com

System Analysis & Design - Rana Talaat Muhammad 8

 System
Components of UCD is whatever you’re developing
An actor is going to be someone
Website Actor or something that uses our
system to achieve a goal

Software Use Case

Application Relationships

any number of other things

which show how actors and use

cases interact with each other.
Use Cases are elements that really start
to describe what the system does.

System Analysis & Design - Rana Talaat Muhammad 9

 Include

Base Use Included Use

Case Case

Every time the base use case is executed, the included use case is executed too.

System Analysis & Design - Rana Talaat Muhammad 10

 Include

Base Use Included Use

Case Case

The base use case requires an included use case in order to be complete

System Analysis & Design - Rana Talaat Muhammad 11

 Include

Base Use <<Include>> Included Use

Case Case

System Analysis & Design - Rana Talaat Muhammad 12

 Extend

Base Use Extend Use

Case Case

When the base use case is executed, the extend use case some times, but not
every time –may be executed– (Optional)

System Analysis & Design - Rana Talaat Muhammad 13

 Extend

Base Use Extend Use

Case Case

The Extend use case will only happen when a set of criteria are met

System Analysis & Design - Rana Talaat Muhammad 14

 Extend

Base Use <<Extend>> Extend Use

Case Case

System Analysis & Design - Rana Talaat Muhammad 15

 Must happens every time

Close Eyes
l ude>>
c
<<In

Sneeze
Example

<<Ext
end>>
Put Hand on
Nose & Say
Elhamdullah

Might happen some times

System Analysis & Design - Rana Talaat Muhammad 16

 Generalization relationship:

Pay by Visa

Pay Fees

Pay Cash

System Analysis & Design - Rana Talaat Muhammad 17

 Generalization relationship:

Deposit
Money
Perform
Money
Transaction
Withdraw
Money

System Analysis & Design - Rana Talaat Muhammad 18

 Generalization relationship:

Search by
Author

Search Book

Search by
Book name

System Analysis & Design - Rana Talaat Muhammad 19

Generalization relationship

User

Staff Student
System Analysis & Design - Rana Talaat Muhammad 20
Use Case Relationships Generalization
Compared
Base use case could be 
abstract use case (incomplete) or
concrete (complete).
Specialized use case is required,
not optional, if base use case is
abstract.
No explicit location to use
specialization.
No explicit condition to use
specialization.
System Analysis & Design - Rana Talaat Muhammad
Extend Include
Base use case is complete
Base use case is incomplete (
(concrete) by itself, defined
abstract use case).
independently.
Extending use case is optional, Included use case required, not
supplementary. optional.
Has at least one explicit extension No explicit inclusion location but
location. is included at some location.
Could have optional extension No explicit inclusion condition.
condition.
21
Banking App

22
System Analysis & Design - Rana Talaat Muhammad
 Sign Up Free
www.lucidchart.com/

Use Case
Activity

tmh.rana@gmail.com Diagram

System Analysis & Design - Rana Talaat Muhammad 23

 References
• J.A Hoffer, J.F. George, and J.S. Valacich, "Modern Systems Analysis and
Design", 7/E, Addison-Wesley, 2014
• Kenneth E. Kendall, Julie E. Kendall.,“Systems Analysis and Design ”,
Pearson, 2014
• D. Jeya Mala and S. Geeta, "Object Oriented Analysis & Design Using UML",
McGrawHill, 2013
• Alan Dennis, Barbara Haley Wixom, David Tegarden, "Systems Analysis and
Design With UML : An Object-Oriented Approach ", John Wiley, 2010
• Klaus Pohl, "Requirement Engineering Fundamentals", Santa Barbara, CA :
Rocky Nook, 2011

System Analysis & Design - Rana Talaat Muhammad 24

System Analysis & Design - Rana Talaat Muhammad 25
System Analysis & Design - Rana Talaat Muhammad 26