Matakuliah
Tahun
Versi
: M0446/Analisa dan Perancangan Sistem Informasi
: 2005
: 0/0
Pertemuan 2
Object Oriented
Understanding
1
Learning Outcomes
Pada akhir pertemuan ini, diharapkan mahasiswa
akan mampu :
• Mahasiswa dapat Menunjukkan kegunaan dari analisis
dan perancangan berorientasi object dan membuat
sistem definisi
2
Outline Materi
•
•
•
•
System Context
Pengertian Sistem
Siklus Pengembangan Sistem
Rich Picture
3
System Context
System
user
Problem
Domain
Application Domain
4
Model
Problem Domain
Application Domain
Payroll
System
• Employee
• Contracts
• Work Schedule
Personal Office
Air Traffic
•
•
•
•
•
Plane
Flight Departure
Flight Corridors
Runaway
Flight Position
Part of the air traffic
controller’s job
Telephone
Signal
•
•
•
•
Signal
Line
Transmitter
Receiver
Part of the technical job
5
System
Kumpulan dari komponen yang
mengimplementasikan model dari
requirement, function dan interface
6
System Architecture
user
Other system
Interface
Function
Model
• Mudah dimengerti
• Tidak ada keraguan
system
7
Air Traffic Controller
Model Component
Function Component
Interface Component
Planes, flight
departures, flight
corridors, position,
and the relation
among them
Plane change
• Monitors,
position, system
Printouts, other
update function, and
facilites to interact
change the model
w/ users
componen’s state
• Connect to other
system
8
Siklus Pengembangan dengan OOAD
Requirements
for use
Problem
Domain
Analysis
Model
Application
Domain
Analysis
Component
Design
Specifications of
components
Specifications of
architecture
Architectural
Design
9
Siklus Pengembangan dengan OOAD
Problem Domain
analysis
•Classes
•Structure
•Behavior
Application Domain
analysis
Usage
Functions
Interface
Component design
•Criteria
•Components
•Processes
Architecture
Design
•Model Component
•Function Component
•Connected Components
10
Problem Domain Analysis
Ada 3 kegiatan
• Mencari elemen dari Problem Domain
yaitu Objects, classes, dan events
• Buat model berdasarkan hubungan
strutural antara class dan objects yang
dipilih
• Interaksi antar object dan class serta
behaviour dari object dan class
11
Dasar Dari Analisis Problem Domain
System Definition
Behaviour
Classes
Iterate
Structure
Model
12
Analisis Problem Domain
Activity
Classes
Structure
Content
Concepts
Which objects and
events are part of
the object system?
Class
Object
Event
How are classes and
objects conceptually
tied together?
Generalisation
Aggregation
Association
Cluster
Event sequence
Behavioural pattern
Attribute
Behaviour Which dynamic
properties do the
objects have?
13
Dasar Dari Analisis Problem Domain
• Memodel dunia nyata seperti yang akan
dilihat oleh pemakai
• Buat dahulu secara umum baru ke detil
14
System Choice
• Tujuan:
– Mengetahui karakteristik suatu sistem secara
lengkap
• Konsep:
– Definisi sistem: membuat penjelasan padat
mengenai sistem yang terkomputerisasi,
dalam bahasa natural.
15
System Definition
Ideas
Situation
System
definition
Systems
16
Rich Picture
• A rich picture is an informal drawing that
presents the illustrator’s understanding of
a situation.
• A rich picture focuses on important
aspects of a situation, which are
determined by the illustrator.
• See Figure 2.2 page 26
17
Ideas for symbols for Rich Pictures
• Process and Structure
• Things and People
18
Practical Advise
Rich Pictures should:
• Contain a lot of information and be open to interpolation
• Present processes and structures in a coherent, wellbalanced way;
• Show at least one problematic area;
• Point at several relevant computerized systems;
• Be rich, but not chaotic;
• Illuminate key aspects pf a situation in a way that
promotes understanding at many levels; and
• Avoid representing data and data processing
19
Define Systems
• Principle: define alternative systems
• Create useful system definitions:
– Use general terms and focus on emergent properties
– Focus on ideas rather than describing the situation as
it is
– Make the definition brief and precise
– Experiment with several system definitions
– Go beyond habitual ways of thinking
– Use the selection process to discover additional
relevant properties
20
FACTOR CRITERION
• Functionality: The system functions that support the
application-domain tasks
• Application Domain: those parts of an organization that
administrate, monitor, or control a problem domain
• Conditions: The conditions under which the system will
be developed and used
• Technology: Both the technology used to develop the
system and the technology on which the system will run
• Objects: The main objects in the problem domain
• Responsibility: The system’s overall responsibility in
relation to its context.
21
Principles (Conclusion)
• Appreciate the situation
• Cultivate new ideas
• Define alternative systems
22