Upload
job-reeves
View
217
Download
1
Embed Size (px)
Citation preview
Pertemuan 08 Systems Analysis and Design of a Business Event Driven System
Matakuliah : M0034 /Informasi dan Proses Bisnis Tahun : 2005
Versi : 01/05
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
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
Exhibit 4-17Evolution Of AIS Modeling
Stage 1ManualSystems
Stage 2AutomatedSystems
Stage 3
Resources:ManualProcess: Acct CycleData Stores (Files): Journals & Ledgers
Resources:Information TechnologyProcess: Acct CycleData Stores (Files): Journals & Ledgers
Event Driven ITApplicationsResources:Information TechnologyProcess: Record, Maintain, ReportBusiness Activity DataData Stores: Business Activity DataIntegrated Stores
Bias:Generate financialstatements
Bias:Generate financialstatements
Bias:Support Planning, Control& Evaluation Activities ofVarious InformationCustomers
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
Prototyping: Preliminary Steps
Step 1: Review the business process and identify the business events of interest.
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
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.
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
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.
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
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.
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
Prototyping: Preliminary StepsStep 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.
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
Planning an Event-Driven Application
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
Chapter 2
Chapter 2
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
Planning an Event-Driven Application
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
Chapter 4
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
McKell’s Retail Sale StoreMcKell’s Retail Sale Store
Sale
CustomerMerchandise
SalespersonRegister
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
Application Context Diagram
EVENT-DATADefinitions of various data flows for each business event within the application scope
MAINTENANCE-DATADefinitions 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
Event-Data
ReportsApplicationContextResponse
Notification
Maintenance-Data
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
McKell’s Retail Sale Context Diagram
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-PeriodSales-by-Salesperson = Report-Date + {Salesperson Name + {Merchandise-Description +
Qty-Sold + $ Contribution} Total Sales + Total ContributionCustomer-Profile = Report-Date + Name + State + Birthdate + Telephone +
{Merchandise Description + Qty-Sold}
Event-Data
ReportsApplicationContextResponse
Notification
Maintenance-Data
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
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
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
McKell’s Retail Sale REAL Model With Cardinalities
Sale
CustomerMerchandise
SalespersonRegister(1,1)
(0,*) (0,*)
(1,1)
(0,*)
(1,1)(1,*)
(0,*)
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
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
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
McKell’s Retail Sale Store - Tables
Register (Register#,
Merchandise (Merchandise#,
Sale (Sale#,
Customer (Customer#,
Salesperson (Employee#,
Sale-Merchandise ([Sale#], [Merchandise#],
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
McKell’s Retail Sale Store - Tables
Register (Register#,
Merchandise (Merchandise#,
Sale (Sale#, [Register#], [Customer#], [Employee#],
Customer (Customer#,
Salesperson (Employee#,
Sale-Merchandise ([Sale#], [Merchandise#],
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
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 ([Sale#], [Merchandise#], Qty-Sold, Historical-Cost, Historical-Price, ...
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
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)
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
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.
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
McKell’s Retail Sale UpdatedREAL Model With Cardinalities
Sale
CustomerMerchandise
SalespersonRegister(1,1)
(0,*) (0,*)(1,1)
(0,*)(1,1)(1,*)
(0,*)
Receive Payment
Receipts ClerkCash
(0,*) (0,*)
(0,*)(1,1)(1,1)
(0,*)
(1,1)
Store
(1,1) (0,*)
(1,*)
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
McKell’s Retail Sale StoreTables:
Merchandise
Customer
Salesperson
Sale-Merchandise
Register
We are able to satisfy multiple views by the data we collect:
•What happened?•When?
•What resources were involved and how much?
•Where did it occur?
•Who was involved and what roles did they play?
Sale
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.
The McGraw-Hill Companies, Inc., 2000
Irwin/McGraw-Hill
Customer Places Order
Package and Deliver Product
Receive Payment
Salesperson
Product Components
Packager
Carrier
Customer
Customer Payment Clerk
Cash
Package
Customer Service Center
Distribution Center
Customer Returns Merchandise
Returns Clerk
REAL Business Process Modeling of Mail Order Sales/Collection Process