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

1. Pertemuan 11Systems Analysis and Design of a Business Event Driven System Matakuliah : M0034 /Informasi dan Proses Bisnis Tahun : 2005 Versi : 01/05

2. Learning Outcomes Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu : • Menjelaskan tahapan dalam menganalisa dan merancang aplikasi TI

3. Outline Materi • Metode Analisis & Perancangan Sistem Informasi

4. Systems Analysis and Design of a Business Event Driven System Chapter 4

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

6. 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?

7. 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 processpresented 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

8. Project Identification and Selection I. The Analysis Phase – determining systems requirements and structuring the requirements by creating process models, logical models, and conceptual data models. IV. The Implementation and Maintenance Phase – performing system coding, testing, installing, documenting, user training, supporting users, and maintaining the system. Project Initiation Analysis III. The Physical Design Phase – designing physical files, databases, and programming instructions. Logical Design II. The Logical Design Phase – developing the logical design of the database and designing forms, reports, interfaces, and dialogues. Physical Design Implementation Maintenance Steps of a Systems Analysis and Design Life Cycle (SDLC) J.A. Hoffer, J.F. George, and J.S. Valacich, Modern Systems Analysis and Design, Reading, Massachusetts: Addison Wesley, 1999.

9. The Systems Development Process Systems Planning Existing systemdetails and limitations Planned applicationdevelopment process Existing system detailsand limitations Systems Support Systems Analysis Businessrequirementsstatement Productioninformationsystem Technicaldesignstatement Systems Implementation 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.

10. 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 Process Modeling Logical Models Conceptual data modeling

11. 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?

12. 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.

13. Order personnel Reporting useful information to information customers takes Receive customer order includes Inventory Customer places Maintaining reference data about resources, agents, and locations goes to Recording operating event data Shippingpersonnel is made up of Ship Order executes Shipping firm carried by is kept at Collect payment increases sends Bank Cash Cashier takes in Exhibit 4-3 Christopher Inc. REAL Model Resources Agents Events 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

14. Data Response Recording Process Stimulus Notification Maintaining Process • 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. • 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. Stimulus • 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. Data Response Notification Reporting Process Data Response Stimulus Notification The Structure of Information Processes

15. Berlanjut ke Pertemuan 12