MEHRAN UNIVERSITY OF ENGINEERING AND TECHNOLOGY

S.Z.A.B CAMPUS KHAIRPUR MIR’S,

Department of Software Engineering
5th Semester 3rd Year

Software Construction and Development

Practical No. 2
To become familiar with Use case diagrams
Student’s Roll no: _______________ Points Scored: __________________________

Date of Conduct: ________________ Teacher’s Signature: ___________________

LAB DATA ANALYSIS ABILITY TO

SUBJECT CALCULATION OBSERVATION/
PERFORMANCE KNOWLEDGE
AND CONDUCT PRESENTATION
AND CODING RESULTS
SCORE
INDICATOR INTERPRETATION EXPERIMENT

▪ OBJECTIVES: Upon successful completion of this practical, the students will be able to:
✓ Understand the basics of UML diagrams
✓ Understand and learn use case diagrams.
✓ Create use case diagrams

UML (Unified Modeling Language)

The Unified Modeling Language (UML®) is a standard visual modeling language intended to be
used for

• modeling business and similar processes,

• analysis, design, and implementation of software-based systems

UML is a common language for business analysts, software architects and developers used to
describe, specify, design, and document existing or new business processes, structure, and behavior
of artifacts of software systems.

UML is a standard modeling language, not a software development process. UML 1.4.2 Specification
explained that process:

✓ Provides guidance as to the order of a team’s activities,

✓ Specifies what artifacts should be developed,
✓ Directs the tasks of individual developers and the team as a whole, and
✓ Offers criteria for monitoring and measuring a project’s products and activities.
 UML Diagrams

✓ UML is linked with object-oriented design and analysis. UML makes the use of elements and
forms associations between them to form diagrams.
✓ Some UML diagrams try to analyze and depict the structure of a system or process, whereas other
describes the behavior of the system, its actors, and its building components.
✓ Diagrams in UML can be broadly classified as:
1. Structural Diagrams – Capture static aspects or structure of a system. Structural Diagrams
include: Component Diagrams, Object Diagrams, Class Diagrams and Deployment Diagrams.
2. Behavior Diagrams – Capture dynamic aspects or behavior of the system. Behavior
diagrams include: Use Case Diagrams, State Diagrams, Activity Diagrams and Interaction
Diagrams.

Use Case Diagrams

In the Unified Modeling Language (UML), a use case diagram can summarize the details of your
system's users (also known as actors) and their interactions with the system. To build one, you'll
use a set of specialized symbols and connectors. An effective use case diagram can help your team
discuss and represent:

✓ Scenarios in which your system or application interacts with people, organizations, or

external systems
✓ Goals that your system or application helps those entities (known as actors) achieve
✓ The scope of your system

The purpose of a use case diagram

• 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.
• Shows the interaction among the requirements and actors.

Use case diagrams benefits to users

✓ Give context to the requirements.

✓ Are easy to write and understand.
✓ Facilitate agreement with customer regarding the required behavior of the system.
✓ A way to verify all requirements are captured.
✓ A planning instrument.

Basic Use Case Diagram Symbols and Notations

• System / System Boundary

Draw your system's boundaries using a rectangle that contains use cases. Place actors outside the
system's boundaries.

• Use Case

A use case represents a function or an action within the system. It’s drawn as an oval and
named with the function.

• Relationship/Association

Illustrate relationships between an actor and a use case with a simple line also known as
association.
• For example, for modeling a clinic system, the use cases will be "Make appointment" and
"Perform medical tests". Here patients and doctors’ relationship or association is made using
a line.

Relationships between the use cases:

➢ Extend
➢ Include
➢ Generalization

• Include Relationship

In UML modeling, an include relationship is a relationship in which one use case (the base use case)
includes the functionality of another use case (the inclusion use case). It supports the reuse of
functionality in a use-case model.

• Extend Relationship

You can use an extend relationship to specify that one use case (extension) extends the behavior of
another use case (base). This type of relationship reveals details about a system or application that
are typically hidden in a use case.
• Generalization

Generalization relationships are used in class, component, deployment, and use-case diagrams to
indicate that the child receives all the attributes, operations, and relationships that are defined in
the parent.

Steps To Create Use Case Diagram in StarUML

• Select use case diagram that comes under model and add diagram.

• Select use case diagram that comes under model and add diagram. Here example use case is
created for ATM System so name it as ATM system

• Select actors’ using drag from side panel and drop on main window screen.

Note: Actors should be placed outside the system boundary.

• Create all possible use cases for ATM System.

Add Relations among actors and users and among use cases.
 Lab Tasks

1. Draw use case diagram given in lab manual.

2. Create use case diagram for your proposed System.

Conclusion:
Have you become familiar with basic concepts of UML Diagrams? What concepts did you gain
from this practical about use case Diagrams? Comment

______________________________________________________________________________________________________
______________________________________________________________________________________________________
______________________________________________________________________________________________________
______________________________________________________________________________________________________
______________________________________________________________________________________________________
______________________________________________________________________________________________________
__________________________________________________________________________________________________

The End