Pertemuan 11 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

• Metode Analisis & Perancangan Sistem Informasi

By Hollander, Denna, Cherrington

PowerPoint slides by: Bruce W. MacLean, Bruce W. MacLean,

Faculty of Management, Faculty of Management,

Dalhousie UniversityDalhousie University

Accounting, Information Technology, and Business Solutions, 2nd Edition

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

Systems Analysis and Design of a Business Event Driven System

Chapter 4

The McGraw-Hill Companies, Inc., 2000

Irwin/McGraw-Hill

Objective

The objective of this chapter is to help you understand the key steps in analyzing and designing information technology (IT) applications.

The McGraw-Hill Companies, Inc., 2000

Irwin/McGraw-Hill

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?

The McGraw-Hill Companies, Inc., 2000

Irwin/McGraw-Hill

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

Implementation

Maintenance

Physical Design

Logical

Design

Analysis

Project Identification and Selection

Project Initiation

J.A. Hoffer, J.F. George, and J.S. Valacich, Modern Systems Analysis and Design, Reading, Massachusetts: Addison Wesley, 1999.

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

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

I. The Analysis Phase – determining systems

requirements and structuring the

requirements by creating process models, logical models, and conceptual

data models.

II. The Logical Design Phase – developing the

logical design of the database and designing forms, reports, interfaces, and

dialogues.

III. The Physical Design Phase – designing physical files, databases, and programming instructions.

IV. The Implementation and Maintenance Phase – performing system

coding, testing, installing,

documenting, user training, supporting

users, and maintaining the

system.

The Systems Development Process

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.

Systems Planning Planned application

development process

Systems Analysis

Businessrequirements

statement

Systems Design

Technicaldesign

statement

Existing system detailsand limitationsSystems

Support

Existing systemdetails and limitations

Systems Implementation

Productioninformation

system

The McGraw-Hill Companies, Inc., 2000

Irwin/McGraw-Hill

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

The McGraw-Hill Companies, Inc., 2000

Irwin/McGraw-Hill

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?

The McGraw-Hill Companies, Inc., 2000

Irwin/McGraw-Hill

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.

The McGraw-Hill Companies, Inc., 2000

Irwin/McGraw-Hill

Recording operating event data

Maintaining reference data

about resources, agents, and

locations

Exhibit 4-3 Christopher Inc. REAL ModelResources Events Agents

Order personnel

CustomerInventory

Receivecustomer

orderincludes

takes

places

Cashier

Collectpayment

CashBank

is keptat increases

takes in

sends

Shippingpersonnel

Shippingfirm

ShipOrder

is made

up of

goes to

executes

carried by

Christopher Inc. provides baseball caps to major league baseball teams to sell in their ballparks. While analyzing their business

process, Christopher’s analysis team identified three key operating activities:

receive orders from baseball teams (who are Christopher’s customers), package and ship caps to the teams (the sale of merchandise),

and receive payment from the teams

Reporting useful information to information customers

The McGraw-Hill Companies, Inc., 2000

Irwin/McGraw-Hill

The Structure of Information Processes

RecordingProcess

Stimulus

Response

Notification

Data

Executing each operating event triggers the need to record descriptive data about the event. When data is captured while the operating event occurs, the recording process can execute business rules specified by management for each operating event. These rules are the guidelines, standards, policies, and/or procedures intended to increase operational and information quality by reducing such problems as errors, irregularities, or fraud. Ideally, the execution of the operating event and the related information process occur simultaneously.

MaintainingProcess

Stimulus

Response

Notification

Data

To support a business process, a system must collect data about the resources, agents, and locations that define the operating events. The system must allow the data to be kept current. Maintaining reference data involves adding, deleting, or modifying data about resources, agents, and locations (e.g., changing products offered by a vendor; changing an employee's marital status; and adding a new vendor to the vendor list). The objective is to maintain accurate, complete, and timely data about the resources, agents, and locations involved in operating events for the process you are modeling.

ReportingProcess

StimulusData Response

Notification

The reporting processes extract and convert stored data about events, resources, agents, and locations into information, and formatting the information for presentation to information customers.These views often consist of financial and performance measures and may take the form of hardcopy source documents, hardcopy reports, electronic data flows, or ad hoc queries. These data flows authorize actions, provide documentation to other business functions or to outside parties, and support both operational and strategic decision making.

Berlanjut ke Berlanjut ke

Pertemuan 12Pertemuan 12