Matakuliah : M0034 /Informasi dan Proses Bisnis

Tahun : 2005
Versi : 01/05

Pertemuan 11
Systems Analysis and Design of
a Business Event Driven System
 Learning Outcomes

Pada akhir pertemuan ini, diharapkan mahasiswa

akan mampu :
• Menjelaskan tahapan dalam menganalisa
dan merancang aplikasi TI
 Outline Materi

• Metode Analisis & Perancangan Sistem

Informasi
 Accounting, Information Technology,
and Business Solutions, 2nd Edition
By Hollander, Denna, Cherrington
Systems Analysis and Design of a Business Event
Driven System

PowerPoint slides by:

Bruce W. MacLean,
Faculty of Management,
Dalhousie University

Chapter 4

Irwin/McGraw-Hill The McGraw-Hill Companies, Inc., 2000

 Objective

 The objective of this chapter is to help you understand

the key steps in analyzing and designing information
technology (IT) applications.

Irwin/McGraw-Hill The McGraw-Hill Companies, Inc., 2000

 Analysis and Design of a Business Event-
driven IT Application

 Designing quality IT applications requires a thorough

understanding of the organization including its current
and desired objectives, strategies, value chains, risks,
and business processes
 There are a variety of methods for analyzing and
designing information systems.
 How do professionals move from a business need for
information to creating the physical IT infrastructure
that can provide that information?

Irwin/McGraw-Hill The McGraw-Hill Companies, Inc., 2000

 Systems Analysis and Design
Methods
 Exhibit 1 presents a systems analysis and design life cycle
(SDLC) by J.A. Hoffer, J.F. George, and J.S. Valacich
 Exhibit 2 displays the systems development process
presented by J.L. Whitten, L.D. Bentley, and V.M. Barlow
 Other analysis and design approaches, including
 object-oriented analysis and design,
 prototyping,
 systems engineering,
 joint application design,
 participatory design,
 essential system design,
 automating the SDLC using CASE tools

Irwin/McGraw-Hill The McGraw-Hill Companies, Inc., 2000

 Project
Identification
Steps of a Systems Analysis and
and Selection Design Life Cycle (SDLC)

Project I. TheIV.
Analysis
The Implementation
Phase –
Initiation determining
andsystems
Maintenance
requirements
Phase –
and structuring performing
the requirements
system by
Analysis creatingcoding,
process
III. testing,
models,
The installing,
logical
Physical
models, and documenting,
conceptual
Design Phase data
user
–
II. The Logical Logical training,
models. supporting
Design Phase – designing physical
users, and
files, maintaining
databases, and
developing the Design
the system.
programming
logical design of the
Physical instructions.
database and Design
designing forms,
reports, interfaces, Implementation
and dialogues.
J.A. Hoffer, J.F. George, and J.S. Valacich, Modern Systems Analysis Maintenance
and Design, Reading, Massachusetts: Addison Wesley, 1999.
 The Systems Development Process

Systems
Existing system Planned application
details and
Planning
development process
limitations

Existing system details

and limitations
Systems Systems
Support Analysis

Production Business
information Technical requirements
system design statement
statement
Systems Systems
Implementation Design

J.L. Whitten, L.D. Bentley, and V.M. Barlow, Systems Analysis and Design,
instructors ed., 3rd ed. Burr Ridge, Ill.: Richard D. Irwin, 1994.
 Phase 1: Systems Analysis
 Step 1-A: Defining systems requirements
 Step 1-B: Structuring systems requirements
using process modeling
 Step 1-C: Structuring systems requirements
using logical models
 Step 1-D: Structuring systems requirements
using conceptual data modeling
 Step 1-E: Selecting a design strategy

Irwin/McGraw-Hill The McGraw-Hill Companies, Inc., 2000

 STEP I-A: Systems Analysis -
Defining Systems Requirements
 After an organization has:
 identified the need for a system project and
 has successfully made a business case to justify investing the time and funds
necessary to undertake the project,
 a project team organizes and plans the work to be completed.
 The team considers the costs, benefits, feasibility, responsibilities,
and project timeline.
 After completing these details they define the system requirements:
 What are the expectations of this system?
 What work and decisions will it support?
 What objectives will it help the organization to accomplish?

Irwin/McGraw-Hill The McGraw-Hill Companies, Inc., 2000

 Defining Systems Requirements
 Your business analysis highlights the activities that an
organization needs to perform effectively and efficiently to
accomplish its objectives.
 An information system should support
these activities.
 Add information processes, including data
stores, and data flows, to the analysis
 Consider the desired environment and
envision innovative ways for the system
to enable organization objectives and
desired processes.

Irwin/McGraw-Hill The McGraw-Hill Companies, Inc., 2000

 Exhibit 4-3 Christopher Inc. REAL Model
Resources Events Agents

Order
Christopher Inc. provides baseballakcaps e s to
Reporting Receive
usefulbaseball t personnel
major league teams to sell in their
includes customer their business
information
ballparks.
Inventory toWhile analyzing p l ac e
process, order
Christopher’s analysis teams Customer
information
Maintaining identified three key operating to
activities:
customers e s
is p o

Recording receive orders from baseball teams

o
g (who are Shipping
m f

reference data about

u
ad

operating Christopher’s customers), Ship packageexand s personnel

ecuteship
e

resources, agents, and

event data caps to the teams (theOrder sale of merchandise),
car
locations and receive payment from the teams ried
by Shipping
is kept firm
at increases Collect sends
Bank Cash
payment takes
in Cashier

Irwin/McGraw-Hill The McGraw-Hill Companies, Inc., 2000

 The Structure of Information Processes
Stimulu
Stimulus
Reporting
Recording
Maintaining Stimulu
s
Data
Data
Data Process s
Response
Process Response
Response
Notification
Notification
Notification
The reporting
To support processes
a business extracta and
process, convert
system must stored
collectdata
dataabout
aboutevents, resources,
the resources,
agents, and locations
Executing into
each operating information,
that define
event and the
thetriggers formatting
operating events. the
need to The information
system
record mustfor
descriptive allow
datatheabout
presentation
data to be kept
the event. to current.
information customers.
These
When views
Maintaining often
data isreferenceconsist
captured dataofinvolves
while financial
the and performance
adding,
operating deleting,
event measures
occurs,or modifying
the anddata
recording may takecan
about
process the
form of hardcopy
resources,
execute business source
agents,rules documents,
and locations
specified (e.g., hardcopy
changing reports,
by management products electronic
for eachoffered by
operatingdata flows, or ad
aevent.
vendor;
hoc queries.
changing
These an employee's
rules marital status;
are the guidelines, and adding
standards, a new
policies, vendor
and/or to the vendor
procedures intended list).
to
 These
increase data flows
The objective
operationalis toauthorize
maintain
and actions,
accurate,
information providebydocumentation
complete,
quality such to
and timely
reducing other
data business
about
problems theerrors,
as
functions
resources, or
irregularities,tooroutside
agents, parties,
Ideally,and
and locations
fraud. support
involved
the inboth
execution of operational
operating eventsand
the operating for strategic
the process
event decision
and the you are
related
making.
modeling.
information process occur simultaneously.

Irwin/McGraw-Hill The McGraw-Hill Companies, Inc., 2000

Berlanjut ke
Pertemuan 12