Matakuliah
: M0034 /Informasi dan Proses Bisnis
Tahun
Versi
: 2005
: 01/05
Pertemuan 08
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
• Model-model tahapan Analisis &
Perancangan Sistem Informasi (Cont'..)
– Evolution Of AIS Modeling
– Prototyping
– Building an IT Application Prototype
Lanjutan Dari
Pertemuan 12
Exhibit 4-17
Evolution Of AIS Modeling
Stage 1
Manual
Systems
Resources:
Manual
Process:
Acct Cycle
Data Stores (Files):
Journals & Ledgers
Bias:
Generate financial
statements
Irwin/McGraw-Hill
Stage 2
Automated
Systems
Resources:
Information Technology
Process:
Acct Cycle
Data Stores (Files):
Journals & Ledgers
Bias:
Generate financial
statements
Stage 3
Event Driven IT
Applications
Resources:
Information Technology
Process:
Record, Maintain, Report
Business Activity Data
Data Stores:
Business Activity Data
Integrated Stores
Bias:
Support Planning, Control
& Evaluation Activities of
Various Information
Customers
The McGraw-Hill Companies, Inc., 2000
Prototyping: Preliminary Steps
Step 1: Review the business process and identify
the business events of interest.
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
Prototyping: Preliminary Steps
Step 1: Review the business process and identify
the business events of interest.
Step 2: Analyze each event to identify the event
resources, agents, and locations.
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
Prototyping: Preliminary Steps
Step 1: Review the business process and identify
the business events of interest.
Step 2: Analyze each event to identify the event
resources, agents, and locations.
Step 3: Identify the relevant
behaviors, characteristics, and
attributes of the event,
resources, agents, and
locations.
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
Prototyping: Preliminary Steps
Step 1: Review the business process and identify
the business events of interest.
Step 2: Analyze each event to identify the event
resources, agents, and locations.
Step 3: Identify the relevant behaviors, characteristics,
and attributes of the event, resources, agents, and
locations.
Step 4: Identify the direct
relationships between objects.
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
Prototyping: Preliminary Steps
Step 1: Review the business process and identify
the business events of interest.
Step 2: Analyze each event to identify the event
resources, agents, and locations.
Step 3: Identify the relevant behaviors, characteristics,
and attributes of the event, resources, agents, and
locations.
Step 4: Identify the direct relationships between
objects.
Step 5: Validate the model with the business person.
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
Planning an Event-Driven Application
C
h
a
p
t
e
r
2





Identifying the business events of interest
Identifying the resources, agents, and locations of each
event of interest
Identifying the relevant behaviors, characteristics and
attributes of the events, resources, agents, and locations
Identifying the direct relationship between objects
Validating your business process model with business
persons
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
Planning an Event-Driven Application
C
h
a
p
t
e
r
4





Defining the scope of the IT application
Enhancing the relationships of the REAL model by
defining their cardinalities
Designing the data repository
Linking the recording, maintaining, and reporting process
to the data repository
Constructing the prototype
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
McKell’s Retail Sale Store
Salesperson
Register
Sale
Merchandise
Irwin/McGraw-Hill
Customer
The McGraw-Hill Companies, Inc., 2000
Application Context Diagram
Event-Data
Maintenance-Data
Response
Application
Context
Reports
Notification
EVENT-DATA
Definitions of various data flows for each business event within the application scope
MAINTENANCE-DATA
Definitions of various data flows for maintaining application reference data
RESPONSES
Definitions of various responses provided by the application
NOTIFICATIONS
Definitions of various notifications provided by the application
REPORTS
Definitions of various reports provided by the application
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
McKell’s Retail Sale Context Diagram
Event-Data
Maintenance-Data
Response
Application
Context
Reports
Notification
EVENT-DATA Example=
Sale-Data = Sale-Date + Register # + Customer # + Employee # + {Merchandise # + Qty-Sold}
MAINTENANCE-DATA Example=
Definitions of various data flows for maintaining customer, salesperson, and register reference data
RESPONSE Example=
Sales-Invoice = Invoice# +Sale-Date + Register # + Customer Name + Salesperson Name +
{Merchandise Name + Qty-Sold + Price + Item-Total} + Sale-Total
NOTIFICATION Example =
Warehouse-notification = Invoice#+{Merchandise# + Qty-Sold}
REPORT Example =
Product-Sales = Report-Date + {Merchandise # + Merchandise Description + Qty-Sold +
%Margin + $ Contribution}
Accounting-Revenue = Report-Date + Reporting-Period + Revenue for Reporting-Period
Sales-by-Salesperson = Report-Date + {Salesperson Name + {Merchandise-Description +
Qty-Sold + $ Contribution} Total Sales + Total Contribution
Customer-Profile = Report-Date + Name + State + Birthdate + Telephone +
{Merchandise Description + Qty-Sold}
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
Additional Prototyping Steps:
Step 6: Define the scope of the application.
Step 7: Enhance the relationships of the REAL
model by defining their cardinalities.
• object 1(min, max) --- object 2(min, max)
•minimums denote business rules
•maximums help establish data structures
•both help structure your audit trail
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
McKell’s Retail Sale REAL Model With
Cardinalities
Salesperson
Register
(1,1)
(1,1)
(0,*)
(0,*)
Sale
(0,*)
(1,*)
Merchandise
Irwin/McGraw-Hill
(0,*)
(1,1)
Customer
The McGraw-Hill Companies, Inc., 2000
Additional Prototyping Steps:
Step 6: Define the scope of the application.
Step 7: Enhance the relationships of the REAL
model by defining their cardinalities.
Step 8: Design the data repository structure.
•tables or objects
•primary keys
•posted keys
•nonkey attributes
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
McKell’s Retail Sale Store - Tables
Register
(Register#,
Merchandise (Merchandise#,
Sale
(Sale#,
Customer
(Customer#,
Salesperson (Employee#,
Sale-Merchandise
Irwin/McGraw-Hill
([Sale#], [Merchandise#],
The McGraw-Hill Companies, Inc., 2000
McKell’s Retail Sale Store - Tables
Register
(Register#,
Merchandise (Merchandise#,
Sale
(Sale#, [Register#], [Customer#], [Employee#],
Customer
(Customer#,
Salesperson (Employee#,
Sale-Merchandise
Irwin/McGraw-Hill
([Sale#], [Merchandise#],
The McGraw-Hill Companies, Inc., 2000
McKell’s Retail Sale Store - Tables
Register
(Register#, Store, Date-Purchased, Cost, ...
Merchandise (Merchandise#, Description, Current-Price,
Current-Cost, ...
Sale
(Sale#, [Register#], [Customer#], [Employee#],
Time, ...
Customer
(Customer#, Name, Address, State, Zip,
Birthdate, Telephone#, Marital-Status, ...
Salesperson (Employee#, Name, Commission-Rate, ...
Sale-Merchandise
Irwin/McGraw-Hill
([Sale#], [Merchandise#], Qty-Sold,
Historical-Cost, Historical-Price, ...
The McGraw-Hill Companies, Inc., 2000
Additional Prototyping Steps:
Step 6: Define the scope of the application.
Step 7: Enhance the relationships of the REAL
model by defining their cardinalities.
Step 8: Design the data repository structure.
Step 9: Link the recording, maintenance, and
reporting processes to the data repository.
• Record events
• Maintain resources, agents, and locations
• Report (source documents, queries, reports)
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
Additional Prototyping Steps:
Step 6: Define the scope of the application.
Step 7: Enhance the relationships of the REAL
model by defining their cardinalities.
Step 8: Design the data repository structure.
Step 9: Link the recording, maintenance, and
reporting processes to the data repository.
Step 10: Build the application prototype.
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
McKell’s Retail Sale Updated
REAL Model With Cardinalities
Salesperson
Register
(1,1)
(1,1)
(0,*)
(0,*)
Sale
(0,*)
(1,*)
(1,*)
(1,1)
Merchandise
(1,1) (0,*)
Store
Cash
Irwin/McGraw-Hill
(0,*)
(1,1)
(0,*)
(0,*)
Customer
(1,1)
(0,*)
Receive
Payment
(0,*)
(1,1)
Receipts
Clerk
The McGraw-Hill Companies, Inc., 2000
McKell’s Retail
Sale Store
Tables:
We are able to satisfy multiple views
by the data we collect:
Sale
Merchandise
Sale-Merchandise
•What happened?
•When?
•What resources were involved and how much?
•Where did it occur?
Register
•Who was involved and what roles did they
play?
Customer
Salesperson
Irwin/McGraw-Hill
The McGraw-Hill Companies, Inc., 2000
Steps for Building an IT Application Prototype
1. Build a table for each table defined using the REAL model,
2. Build a menu system that has the following choices:
Record Event Data, Maintain Data, Reports, and Exit.
3. Develop the necessary forms and procedures to collect event
data and store it in the appropriate tables.
4. Develop the necessary forms and procedures to maintain the
resource, agent, and location tables.
5. Develop queries required to generate desired information.
6. Develop report formats for each report.
7. Write the procedures required to execute the queries and format
the reports.
8. Link each recording, maintaining, and reporting form to the
application menu defined in step 2. Each form becomes a choice
under either the Record Event Data, Maintenance, or Reports menu
options.
REAL Business Process Modeling of
Mail Order Sales/Collection Process
Customer Service
Center
Salesperson
Product
Components
Customer Places
Order
Customer
Distribution Center
Package and
Deliver Product
Carrier
Package
Cash
Irwin/McGraw-Hill
Packager
Receive Payment
Customer Payment
Clerk
Customer Returns
Merchandise
Returns Clerk
The McGraw-Hill Companies, Inc., 2000
Berlanjut ke
Pertemuan 14