Module 42

Objectives & Module 42: Software Engineering

Outline

Use Case
UML - Use Case Diagrams
Diagrams

Actors

Use-Cases
Specification of
Intructors: Abir Das and Sourangshu Bhattacharya
Use-Cases
Department of Computer Science and Engineering
Relationships
among
Indian Institute of Technology, Kharagpur
Use-Cases
Include
{abir, sourangshu}@cse.iitkgp.ac.in
Extend
Generalization

Use-Cases: Slides taken from NPTEL course on Object-Oriented Analysis & Design
RECAP
by Prof. Partha Pratim Das
Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 1

 Module Objectives

Module 42
• Understanding Use Case Diagrams
Objectives &
Outline

Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 2

 Module Outline

Module 42
• Use Case Diagrams
Objectives &
• Actors
Outline
• Use Cases
Use Case
Diagrams ◦ Specification of Use-Cases
Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 3

 What are Use case Diagrams

Module 42

• The integration of business knowledge with the development

specification is a requirement
Objectives &
Outline
• The development organization knows the specifications for
Use Case
Diagrams
developing a module, but does not know who will interact with
these modules and for what purpose
Actors

Use-Cases • Use Case Diagrams depicts the human interaction with the
Specification of
Use-Cases system to give the context of who uses, which part of the system
Relationships and for what purpose
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 4

 Components of Use case Diagrams

Module 42
The use case diagram is composed of
• Actors
Objectives &
Outline
• Use cases and their specifications
Use Case
Diagrams • Relationships between Use cases
Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 5

 Actor

Module 42

• Actors are entities that interface with the system

Objectives & • They can be people or other systems
Outline

Use Case
• Actors are depicted as stylized stick figures
Diagrams

Actors
• This stick figures are used as stereotypes to depict many models
at the same time labeled with guillemets <<>>
Use-Cases
Specification of
Use-Cases • The roles the actors play in the system is important, not their real
Relationships world identity
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 6

 Actor

Module 42
Actors can be classified as
• human: e.g. novice/trained user; system administrator
Objectives &
Outline
• non-human: e.g., fax, e-mail
Use Case
Diagrams • primary: ultimate user of the system
Actors
• secondary: ensures the correct functionality of the system
Use-Cases
Specification of
Use-Cases • active: initiates use cases
Relationships
among • passive: corresponding use case is initiated by the system
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 7

 Actor

Module 42
How can Actors be identified?
• Who uses the essential use cases?
Objectives &
Outline
• Who needs system support in order to fulfill the daily tasks?
Use Case
Diagrams • Who is responsible for system administration?
Actors
• What are the external devices/software systems the system has to
Use-Cases
Specification of communicate with?
Use-Cases

Relationships • Who is interested in the results of the system?

among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 8

 LMS: List of all Identified Nouns:
RECAP (Module 17)
Module 42 Company Attendance Leave Employees
Contributors Lead Executive Manager
Leave Rules Days Year Name
Objectives & Type of Leave Period Absence Holiday
Outline PL CL EL DL
Use Case SL ML LWP UL
Diagrams Pre-approval Month Service Quarter
Actors Medical Parenthood Disciplinary Administration
Use-Cases
Certificate Certificate Action Function
Specification of Daily Personal Calender Batch Task
Use-Cases
Attendance Details Year
Relationships Account Balance Designation SysAdmin
among
Use-Cases
Parent Salary Week List
Include Privilege Right Login ID Leave Status
Extend Employee Code
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 9

 Actors in LMS

Module 42

• In the LMS, the human actors are Manager, Lead and Executive.
Objectives & • The non human actors is the printer
Outline

Use Case
• A Secondary actor is the SysAdmin
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 10

 Use Cases

Module 42

• Use cases represent what the actors want your system to do for
them
Objectives &
Outline
• Each use case is a complete course of events to be executed in
Use Case
Diagrams
the system from a user’s perspective
Actors • Use cases can contain short descriptions course of events in the
Use-Cases system from a user’s perspective
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 11

 LMS: List of all Identified Verbs:
RECAP (Module 18)
Module 42 Wants Manage Work Report
Approve Regret Credit Join
Prorate Cross En-cash Paid
Objectives & Allow Send Need Become
Outline Enjoy Avail Proceeding Employ
Use Case Consider Deduct Provide Request
Diagrams Cancel Check Export Revoke
Actors Debit Adjust Perform Hire
Use-Cases
Fire Generate Leave Can be
Specification of En-cashment Availed
Use-Cases
Can be Can’t be Can’t be Can’t be
Relationships Clubbed Availed Carried forward Clubbed
among
Use-Cases
Can’t be Accumulated Proposed for Join Back
Include Continued Up
Extend Doesn’t Draw Can be Revoked Leave Credited
Generalization

Use-Cases: Many extracted verbs are in derived forms – so we extract the unique stems
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 12

 Use Cases in LMS

Module 42

• Shown below are important use cases executed by actors of Leave

Management System. Request Leave, Daily Attendance are use
Objectives &
Outline cases, that is, functionality which the all the three human actors
Use Case
need from the system. Similarly approve leave use case executed
Diagrams by only Lead and Manager
Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 13

 Specification of Use Case

Module 42 • A use case can be specified in the following manner. Depicted

below for Request Leave.
Objectives & ◦ Use Case Name: Request Leave
Outline ◦ Use Case Purpose: The Executive, Lead and Manager, all of
Use Case
Diagrams
them uses this functionality to request for leaves in the system.
◦ Use Case Pre-condition: User has login id and password to
Actors
enter the system
Use-Cases
Specification of
◦ Use Case Post-condition: A new leave request is entered in
Use-Cases
the system for the user
Relationships
among ◦ Failure Conditions: User does not have valid credentials to
Use-Cases enter the system, the user do not have sufficient leave balance
Include
Extend ◦ Actors: Lead, Executive, Manager
Generalization
◦ Optimistic Flow:
Use-Cases:
RECAP
▷ The Executive, Lead and Manager checks for the leave balance.
▷ If leave balances are available, leave request added.
Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 14

 Relationships among Use-Cases

Module 42 • Use-Cases share various kinds of relationships

• A relationship between two Use-Cases is basically a dependency
Objectives &
between the two Use-Cases
Outline
• Defining the relationship between two Use-Cases is the decision of
Use Case
Diagrams the modeler of the use case diagram
Actors
• We discuss the following three relationships among Use-Cases
Use-Cases
Specification of
Use-Cases
◦ <<include>>
Relationships
◦ <<extend>>
among ◦ Generalization
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 15

 Relationship among Use-Cases: <<include>>

Module 42 • The <<includes>> relationship involves one Use-Case including

the behavior of another Use-Case in its sequence of events and
actions
Objectives &
Outline
• Thus, the includes relationship explores the issue of reuse by
Use Case
Diagrams
factoring out the commonality across Use-Cases
Actors • <<includes>> relationship:
Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP
◦ the behavior of B is included into A
Identify Actors
◦ the included use case B is necessary to ensure the
Identify
functionality of the base use case A
Use-Cases

Identify CS20202: Software Engineering 16

 Relationship among Use-Cases: <<include>>

Module 42 • In a calendar, if an appointment is inserted by Insert

Appointment, the participants will be notified of appointment by
included Use-Case Notify Participants
Objectives &
Outline
• The included Use-Case Notify Participants is necessary to ensure
Use Case
Diagrams
the functionality of the base Use-Case Insert Appointment
Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization
• The Use-Case Notify Participants may be included in other
Use-Cases: Use-Cases – for example, in Cancel Appointment
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 17

 <<include>> in LMS

Module 42 • Validate Leave Use-Case is included in the Use-Case Request

Leave
Objectives & • The include Use-Cases Validate Leave is necessary to complete
Outline
the functionality of the base Request Leave
Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include • The Use-Case Validate Leave will be included in Approve Leave
Extend
Generalization
too – and so on
Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 18

 Relationship among Use-Cases: <<extend>>

Module 42 • The <<extend>> relationship among the Use-Cases is used to

show optional system behavior

Objectives &
• An optional system behavior is extended only under certain
Outline conditions, known as Extension Points
Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 19

 Relationship among Use-Cases: <<extend>>
• <<extend>> relationship:
Module 42

Objectives &
Outline

Use Case
Diagrams

Actors ◦ the behavior of B may be incorporated into A

Use-Cases
◦ the extending Use-Case B may be (but need not be) activated by the base
Specification of
Use-Case A
Use-Cases ◦ extension points specify the location where the extending Use-Cases
Relationships extends the base Use-Case
among ◦ the condition under which the extending Use-Case is incorporated has to
Use-Cases
be specified
Include
Extend ◦ more than one extension point can be specified for each Use-Case
Generalization ◦ the names of extension points have to be unique
Use-Cases: ◦ the names of extension points need not be equal with the names of the
RECAP extending Use-Cases
Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 20

 Relationship among Use-Cases: <<extend>>

Module 42 • In a savings bank account, bonus is provided only if the deposited

fund is above 20,000 or the depositor is above the age of 60 years
Objectives & • The behavior of Calculate Bonus may be incorporated into
Outline
Deposited Fund amount
Use Case
Diagrams • At extension point: Age above 60 years, Deposit > 20,000
Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 21

 <<extend>> in LMS

Module 42 • The behavior of Check Report may be incorporated into Approve

Leave
Objectives & • The extending Use-Case may be (but need not be) activated by
Outline
the base Use-Case Approve Leave at extension points: Medical
Use Case
Diagrams
Leave, Maternity Leave
Actors • Extending Use-Case (Check Report) extends the base Use-Case
Use-Cases (Approve Leave)
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 22

 Relationship among Use-Cases:
Generalization – Concept of Hierarchy
Module 42
• Generalization works the same way with Use-Cases as it does with classes
• The child Use-Case inherits the behavior and meaning of the parent Use-Case
• Generalization helps us to depict the hierarchy present between Use-Cases
Objectives & • Generalization relationship:
Outline

Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases ◦ Similar to the generalization relationship between classes
Include
◦ B inherits the behavior of A and is allowed to override and extend it
Extend
Generalization
◦ B inherits all relationships of A
Use-Cases:
◦ Modeling of abstract Use-Cases is also possible (abstract)
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 23

 Relationship among Use-Cases:
Generalization – Concept of Hierarchy
Module 42 • Authentication by Fingerprint Use-Case will inherit the base
Use-Case Authentication, to include the basic algorithm, but it
adds on features like finger print matching
Objectives &
Outline

Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 24

 Generalization in LMS

Module 42 • In LMS, Export Manager Leave Use-Case inherits the behavior of

the parent Use-Case Export Executive Leave, that is, it contains
the list of leaves but along with it, it contains additional work
Objectives &
Outline responsibilities of each of the executives. Hence a specialized
Use Case Use-Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 25

 Generalization among Actors

Module 42 • There can be generalization among actors, which can be captured

in the use case diagrams

Objectives &
• Generalization among actors, specify that use cases executed by
Outline the base actor is inherited by the derived actor
Use Case
Diagrams • The derived actor can execute extra use cases
Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 26

 Use-Cases Example:
RECAP (Module 24)
Module 42

Objectives &
Outline

Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify Source: UML 2.5 Diagrams Overview: http://www.uml-diagrams.org/uml-25-diagrams.html (10-Aug-16)

Use-Cases

Identify CS20202: Software Engineering 27

 Use-Cases Example:
RECAP (Module 24)
Module 42

Objectives &
Outline

Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors
Source: UML 2.5 Diagrams Overview: http://www.uml-diagrams.org/uml-25-diagrams.html (10-Aug-16)
Identify
Use-Cases

Identify CS20202: Software Engineering 28

 Identify Actors

Module 42
Identify Actors for LMS

Objectives &
Outline

Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 29

 List of all Identified Nouns:
RECAP (Module 17)
Module 42 Company Attendance Leave Employees
Contributors Lead Executive Manager
Leave Rules Days Year Name
Objectives & Type of Leave Period Absence Holiday
Outline PL CL EL DL
Use Case SL ML LWP UL
Diagrams Pre-approval Month Service Quarter
Actors Medical Parenthood Disciplinary Administration
Use-Cases
Certificate Certificate Action Function
Specification of Daily Personal Calender Batch Task
Use-Cases
Attendance Details Year
Relationships Account Balance Designation SysAdmin
among
Use-Cases
Parent Salary Week List
Include Privilege Right Login ID Leave Status
Extend Employee Code
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 30

 Actors are Nouns

Module 42
• Reading through the specification of the Leave Management System, we
identity the actors
• Actors are the nouns in the specifications
Objectives &
◦ Executive
Outline ◦ Lead
Use Case
◦ Manager
Diagrams ◦ Printer
Actors • Now based on people or things, we identify the human actors and
non-human actors
Use-Cases
Specification of ◦ Human
Use-Cases
▷ Executive
Relationships
among
▷ Lead
Use-Cases ▷ Manager
Include ◦ Non-Human
Extend
Generalization ▷ Printer
Use-Cases: ◦ Secondary
RECAP ▷ SysAdmin
Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 31

 Actors in LMS

Module 42

Objectives &
Outline

Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 32

 Identify Use-Cases

Module 42
Identify Use-Cases for LMS

Objectives &
Outline

Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 33

 List of all Identified Verbs (Stem Only):
RECAP (Module 18)
Module 42 Wants Manage Work Report
Approve Regret Credit Join
Prorate Cross En-cash Pay
Objectives & Allow Send Need Become
Outline Enjoy Avail Proceed Employ
Use Case Consider Deduct Provide Request
Diagrams Cancel Check Export Revoke
Actors Debit Adjust Perform Hire
Use-Cases
Fire Generate Club Carry forward
Specification of Continue Accumulate Propose Join Back
Use-Cases
Draw
Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 34

 Use-Cases are Verbs

Module 42 • Reading through the specification, we identify several verbs which

are behaviors, that is, Use-Cases of the system

Objectives &
◦ Daily Attendance
Outline ◦ Request Leave
Use Case ◦ Cancel Leave
Diagrams
◦ Avail Leave
Actors
◦ Export Leave
Use-Cases
Specification of
◦ Approve Leave
Use-Cases ◦ Revoke Leave
Relationships
among
◦ Export Exec Leave
Use-Cases ◦ Check Medical Report
Include
Extend
◦ Adjust
Generalization ◦ Debit
Use-Cases: ◦ Credit
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 35

 Identify Relationships

Module 42
Identify Relationships for LMS

Objectives &
Outline

Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 36

 Includes

Module 42 • Some verbs will have auxiliaries, that is, related tasks, required to
complete its action

Objectives &
• Like Request Leave will include the verb Check Leave. Hence an
Outline includes definition is identified
Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 37

 Extend

Module 42 • Some verb will incorporate another verb at some conditions, that
is, extension points

Objectives &
• In case of Medical or Maternity Leaves, the verb Approve Leave
Outline will be extended by the action Check Medical Report
Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 38

 Generalization among Use-Cases

Module 42 • There can be hierarchy among Use-Cases, that is, one of the
Use-Cases inherits the behavior of another Use-Case, along with
some extra behaviors
Objectives &
Outline • We see Export Exec Leave has the same behavior like Export
Use Case Leave (will be executed by all actors), along with some special
Diagrams
actions for the Lead and Manager, as only they will be executing
Actors
the Use-Case Export Exec Leave
Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 39

 Generalization among Actors

Module 42 • There can be hierarchy among the actors, that is, nouns.
• That is the base actor will execute some use cases, and the
Objectives &
specialized actors, will execute extra Use-Cases
Outline
• Lead is an Executive, Manager is a Lead – means that
Use Case
Diagrams
◦ Lead executes all the use cases executed by an Executive
Actors
along with some additional use cases (Revoke Leave, Approve
Use-Cases Leave)
Specification of
Use-Cases ◦ Similarly, Manager executes all the Use-Cases executed by a
Relationships Lead along with some additional Use-Cases (Adjust Leave,
among
Use-Cases Credit Leave)
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 40

 Use-Case Diagram: Leave Management System

Module 42

Objectives &
Outline

Use Case
Diagrams

Actors

Use-Cases
Specification of
Use-Cases

Relationships
among
Use-Cases
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify Not all use cases are shown in details

Use-Cases

Identify CS20202: Software Engineering 41

 Module Summary

Module 42
• Use case diagrams help to integrate business knowledge
with the development specification
Objectives &
Outline • Use Case diagram is used to model the various behaviors
Use Case
Diagrams
(usecases) of a system, and the external elements using and
Actors
executing them (actors)
Use-Cases • Relationships among Use-Cases are classified and discussed
Specification of
Use-Cases
• Relationships among Use-Cases are identified for LMS
Relationships
among
Use-Cases
• Illustrated Use-Case diagrams for LMS
Include
Extend
Generalization

Use-Cases:
RECAP

Identify Actors

Identify
Use-Cases

Identify CS20202: Software Engineering 42