Analisis dan Perancangan Sistem Informasi

ISI2G3

Weeks #4 UML and Use Case Diagram

Tim Dosen Analisis dan Perancangan Sistem Informasi

Prodi Sistem Informasi
Fakultas Rekayasa Industri
 Topic Cover

❖ Overview UML
❖ Use Case Diagrams
❖ Use Case Specification
 Learning Objectives
❖ To provide an understanding of UML

❖ Students are able to draw a use case diagrams to depict functional requirements of a system

❖ Students are able to write use case specification for a use case
Overview UML
 What is the UML?
• The Unified Modeling Language is a family of graphical notations, backed by a
single meta-model, that help in describing and designing software systems,
particularly software systems built using the object-oriented style.”
• UML first appeared in 1997
• UML is standardized. Its content is controlled by the Object Management Group
(OMG), a consortium of companies
• The goal of UML is to be a comprehensive modeling language (all things to all
people) that will facilitate communication between all members of the
development effort.
 UML Diagrams
• UML 2 supports 13 different types of diagrams
• Each diagram may be expressed with varying degrees of detail
• Not all diagrams need be used to model a SW system
• The UML does not offer an opinion as to which diagrams would be
most helpful for a particular type of project
 UML Diagrams

Classification of UML diagrams Types

Use Case Diagram
 Use Case Diagrams
Use case diagrams is a technique for capturing the functional
requirements of a system
Use case represent system functionality, the requirements of the
system from the user’s perspective.
 Use Case Diagrams Notation
Use case describe an interaction between
an actor and the system to achieve a goal

Actor is specifies a role played by a user

or any other system that interacts with
the subject.

The relationship between use case

and actors
Type of Actor
 Relationships in use-case diagrams : Include

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).

You can add include relationships to your model to show the following
situations:
• The behavior of the inclusion use case is common to two or more
use cases.
• The result of the behavior that the inclusion use case specifies, not
the behavior itself, is important to the base use case.
 Relationships in use-case diagrams : Extend

• You can use an “extend” relationship to specify that one use case
(extension) extends the behavior of another use case (base)
• The “extend” relationship specifies that the incorporation of the
extension use case is dependent on what happens when the base use
case executes
 Examples case Include and Extend

Include Extend
Example of use case diagram : Helath Clinic System
Use case Specification
 Overview Use Case Specification
• Use case specification is a textual description of the functionality
provided by the system
• Use case specification specifies how a user interacts with a system
and how the system responds to the user actions
• The use case specification is represented in the use case diagram by
an oval, and is what most people think of when they hear the term
use case.
Use Case Specification Template