Department of Information Systems

Subject: Software Analysis and Design

Object Oriented Analysis and Design

Amna Shifia Nisafani

amna@is.its.ac.id
Pretest Quiz 

1. Sebutkan karakter dari OOAD?

2. Apa perbedaan antara business use case dengan use case?
3. Apa perbedaan antara actor pada Business Usecase Diagram dengan
actor pada Usecase Diagram?
4. Apa perbedaan antara usecase pada Business Usecase Diagram dengan
usecase pada Usecase diagram?
5. Sebutkan dua pertanyaan yang dijawab oleh business usecase diagram
6. True/False: OOAD berfokus pada tataran fungsional bukan konseptual

Page 2
Outline

 What is Object Oriented Analysis and Design

 UML
- Business Use Case
- Use Case

Page 3
What is OOAD

 Characteristics of OOAD:
- use-case driven
- architecture centric
- iterative and incremental

 OO Analysis expresses Requirements and Specs expressed as

Population of interacting objects of a system

as opposed to
The traditional data or functional views.

Page 4
OOAD VS SAD (1)

OOAD SAD

Catalog Librarian Library

System

Record Add Report

Book Library Loans Resource Fines

Page 5
OOAD VS SAD (2)

• Structured Analysis
• Divide and Conquer
• At the function level

• Object-Oriented Analysis
• Partition
• At the level of concepts (objects)

Page 6
OOAD VS SAD (3)

Structured Object Oriented

Methodology SDLC Iterative/Incremental
Focus Process Objects
Risk High Low
Reuse Low High
Maturity Mature and Emerging (1997)
widespread
Suitable for Well-defined projects Risky large projects
with stable user with changing user
requirements requirements

Page 7
OOAD VS SAD (4)
Phase Structured Object Oriented
Analysis Structuring Requirement Engineering
Requirements • Use Case Model (find Uses Cases,
• DFDs Flow of Events, Activity Diagram)
• Structured English • Object Model
• Decision Table / Tree • Find Classes & class relations
• ER Analysis • Object Interaction: Sequence &
collaboration Diagram, State
Machine Diagram,
• Object to ER Mapping
Design • DB design (DB • Physical DB design
normalization) • Design elements
• GUI Design (forms & • Design system Architecture
reports) • Design classes: Checking The
Model, Combine Classes, Splitting
Classes, Eliminate Classes
• Design components
• GUI design

Page 8
From Analysis to Implementation

Analysis Design Construction

Investigation of Logical Solution Code
the problem

Representation in an Logical Software Objects Domain Concept

OO Programming Language Ex: Book (Concept)

Public Class Book { Book

Private String Title;
Public void Display(); Attribute: Title
}
Method: Display()

Page 9
Unified Modeling Language

 A notational system aimed at modeling systems using object

oriented concepts.

Page 10
Business Use Case Diagram (1)

 Used to represent the functionality provided by an

organization as a whole.
- They answer the questions "What does the business do?"
and "Why are we building the system?"
 Used extensively during business modeling activities :
- to set the context for the system, and
- to form a foundation for creating the use cases.

Page 11
Business Use Case Diagram (2)

 Do not differentiate between manual and automated

processes

Page 12
 Business Use Case Diagram (3)

 Shows the interactions between business use cases and

business actors.

Business
Workers:
Workers within a
business

business actors:
Business use cases : the anyone or anything
processes that a business outside the business
performs that interacts with the
business

Page 13
 Use Case

 show the interactions between use cases and actors

 focus on just the automated processes

Use cases: system

functionality, the
requirements of the
system from the
user's perspective

Actors: the people or systems

that provide or receive
information from the system
Page 14
STUDI KASUS

Page 15
Postest

1. True/False: hubungan antara business usecase dengan usecase adalah

1 to 1
2. Sebutkan dan jelaskan secara singkat komponen dari business usecase
diagram
3. True/False: Actor pada usecase diagram tidak selalu menggambarkan
orang yang terlibat dalam sistem
4. Sebutkan tiga perbedaan SAD dengan OOAD

Page 16
Next Agenda

 Materi: Object Oriented Analysis and Design [1:19-45] [3:12-26]

- Activity Diagram
- Statechart Diagram
- Robustness Diagram
- Sequence Diagram
- Collaboration Diagram
- Class Diagram
 Referensi:
- Barclay K and Savage J. 2004. Object-Oriented Design with UML and
Java, Burlington: Elsevier Butterworth-Heinemann.gs
- Boggs Wendy and Boggs Micheal. 2002. Michael Boggs. Mastering
UML with Rational Rose. Alameda: Sybex.
 Pretest dan Postest

Page 17