Matakuliah
: M0034 /Informasi dan Proses Bisnis
Tahun
Versi
: 2005
: 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 Eventdriven 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
and Selection
Steps of a Systems Analysis and
Design Life Cycle (SDLC)
I. TheIV.
Analysis
The Implementation
Phase –
determining
andsystems
Maintenance
requirements
Phase –
and structuring
performing
the requirements
system by
creatingcoding,
process
models,
installing,
logical
Analysis
III. testing,
The
Physical
models, and
documenting,
conceptual
data
user
Design
Phase
–
II. The Logical
training,
models.
supporting
users,
Logical
designing
physical
Design Phase –
and
maintaining
the
Design
files,
databases,
and
developing the
system.
programming
logical design of the
Physical
instructions.
database and
Design
designing forms,
reports, interfaces,
Implementation
and dialogues.
Project
Initiation
J.A. Hoffer, J.F. George, and J.S. Valacich, Modern Systems Analysis
and Design, Reading, Massachusetts: Addison Wesley, 1999.
Maintenance
The Systems Development Process
Systems
Planning
Existing system
details and
limitations
Systems
Support
Planned application
development process
Existing system details
and limitations
Production
information
system
Systems
Implementation
Technical
design
statement
Systems
Analysis
Business
requirements
statement
Systems
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
Christopher Inc. provides baseball caps to Order
personnel
Receive
Reporting
usefulbaseball
major league
teams to sell in their
customer their business
ballparks.
While
analyzing
information
to
Inventory
order analysis team Customer
process,
Christopher’s
information
identified three key operating activities:
Maintaining
customers
Shipping
Recording receive orders from baseball teams (who are
reference data about
personnel
Ship package and ship
operating Christopher’s customers),
resources, agents, and
sale of merchandise),
event data caps to the teams (theOrder
locations and receive payment from the teams Shipping
firm
is kept
increases Collect
at
sends
Bank
Cash
payment
Cashier
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
The Structure of Information Processes
Data
Data
Data
Reporting
Recording
Maintaining
Process
Process
Stimulus
Stimulus
Stimulus
Response
Response
Response
Notification
Notification
Notification
The
reporting
processes
extracta and
convert
resources,
To support
a business
process,
system
must stored
collectdata
dataabout
aboutevents,
the resources,
agents,
and locations
into
information,
and the
formatting
the
information
that define
thetriggers
operating
events.
system
mustfor
allow
data
Executing
each operating
event
need to The
record
descriptive
datathe
about
presentation
to information customers.
to
kept current.
thebeevent.
These
viewsisreference
often
consist
ofinvolves
financial
and performance
measures
anddata
may
takecan
the
Maintaining
data
adding,
deleting,
modifying
about
When data
captured
while
the
operating
event
occurs,or
the
recording
process
form
of hardcopy
source
documents,
hardcopy
electronic
data
flows, or ad
resources,
agents,rules
and locations
(e.g.,
changing reports,
products
offered
by
aevent.
vendor;
execute
business
specified
by management
for each
operating
hoc
queries.
changing
an employee's
marital status;
and adding
a new
vendor
to the vendor
list).
These
rules
are the guidelines,
standards,
policies,
and/or
procedures
intended
to
These
data flows
actions,
provide
other
business
The
is toauthorize
maintain
accurate,
complete,
and timely
data
about
increaseobjective
operational
and
information
quality
bydocumentation
reducing
such to
problems
astheerrors,
functions
or
tooroutside
parties,
support
strategic
decision
resources,
agents,
and locations
involved
inboth
operating
eventsand
for
the and
process
you are
irregularities,
fraud.
Ideally,and
the
execution
of operational
the operating
event
the
related
making.
modeling. process occur simultaneously.
information
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
Berlanjut ke
Pertemuan 12