Sei sulla pagina 1di 16

Practical Guide

Object Oriented Analysis and Design

   
Agenda

● Structured Program
● Object Concepts
● Practical guide in OOAD
● Illustration

   
Structured Program

● Based on Input-Process-Output
(http://www.excelsoftware.com/dfd.gif)

   
Object Concepts

“A way of thinking to organize software as a


collection of discrete objects that incorporate both
data structure and behavior”
(http://romisatriawahono.net/publications/2000/romi-ooad.pdf)

   
OO vs. DFD

● Object:
– encapsulates process and data
● DFD:
– deals only in process
– data were analyzed in ERD
● These two concepts arise to handle
decomposing complexity in software
development

   
Simple steps …

● Determines requirement of a software being


develop (hint: use case diagram)
● From use case: determines object involved in
that use case (hint: collaboration diagram,
sequence diagram)
● From collaboration: completing classes (hint:
class diagram)

   
Simple steps ...

● That three simple steps represent


– static structure (class or package diagram),
– dynamic behavior (collaboration, sequence,
state transition, or activity diagram),
– functionality (use case diagram)

   
Illustration

Berikut adalah sebagian dari kebutuhan perangkat lunak “Buku


alamat eletronik sederhana”
● Dapat melakukan operasi add, delete, edit, search
● Memiliki atribut: nama, alamat (kantor & rumah), telepon
(kantor, rumah, mobile[ ])
● Menghapus nama dari daftar akan menghapus semua atribut
dari nama tsb
● Setiap entry harus memiliki atribut nama dan minimal satu
atribut lainya. Kurangnya persyaratan ini membuat mekanisme
penyimpanan data tidak dapat dilakukan

   
Requirement

Requirement Use Case


Menambah entry Tambah entry, Akses database
Menghapus entry Hapus entry, Akses database
Memodifikasi entry Edit entry, Akses database
Mencari entry berdasarkan key tertentu Tampilkan entry, Akses database

● Completed with use case and actor description


– Analog to data dictionary

   
Use case example

● Use case: Tambah entry

   
Use case scenario

Actor Response
1. User melakukan klik di menu Add
2. Form AddEntry muncul
3.a. User mengisi atribut dari kolega yang
ditambah ke buku alamat
3.b. User melakukan klik di tombol Simpan
4. Data disimpan

   
Prototype

   
Collaboration Diagram

   
Class Diagram

   
Sequence Diagram

   
Reference

● Simon Bennet, Steve McRobb, Ray Farmer.


Object Oriented System Analysis And Design
nd
Using UML 2 Edition, McGraw-Hill, 2002

   

Potrebbero piacerti anche