1 / 24

Chapter 5

Chapter 5. System Development Process. Learning Objectives. To understand the qualities of a successful information system To learn the phases that make up the system development life cycle To understand how prototyping is used to develop information systems. Why should you study this ?.

sharon-dennis
Download Presentation

Chapter 5

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 5 System Development Process

  2. Learning Objectives • To understand the qualities of a successful information system • To learn the phases that make up the system development life cycle • To understand how prototyping is used to develop information systems

  3. Why should you study this ? • As Accountants, you will participate in project teams that design accounting systems • As Auditors, you will review and make suggestions for new systems prior to their implementation • You may yourself become a developer of accounting information systems

  4. Qualities of a Successful System • Produce Correct Information - Reliability • Produce Timely Information - Relevant • Reasonable Time for Development • Satisfy the Organization’s Needs • Current • Future • User Satisfaction

  5. How to Achieve these Qualities ?? • Produce Correct Information • Have adequate internal controls • Prevention and Detection of Errors and Fraud • Produce Timely Information • Understand user’s needs • Produce information when the user wants • Use Common Sense

  6. Development Time • Learn to limit the scope of the system • In other words, define boundaries • Use Project Management Techniques • Gantt Charts • PERT • CPM

  7. Satisfy Organization’s Needs • Understand Organization’s Current Information Needs • Predict Future Information Needs • Have Steering Committees to Approve New Systems • Long Range Systems Planning Group • to identify long-range resources • to develop a System Master Plan for new systems

  8. Gaining User Satisfaction • Strongest Indicator of Success • Conduct Surveys and Interviews to measure User Satisfaction • Understand Sources of User Resistance

  9. Sources of User Resistance • Threat to Job or Status • Appearance of Complexity • Rigidity of a Computerized Schedule • Opposition to Change

  10. Overcome User Resistance • User Input in Steering Committee’s decisions • User Support for Project • Active User Participation During Project Development • User Responsibility for the Completed System

  11. System Development Life CycleSDLC Systems Master Plan

  12. System Development Life CycleSDLC Systems Master Plan Systems Analysis

  13. System Development Life CycleSDLC Systems Master Plan Systems Analysis System Design

  14. System Development Life CycleSDLC Systems Master Plan Systems Analysis System Implementation System Design

  15. System Development Life CycleSDLC Systems Master Plan System Operation Systems Analysis System Implementation System Design

  16. System Development Life CycleSDLC Systems Master Plan System Operation Systems Analysis System Implementation System Design

  17. Systems Analysis • Process of examining an existing information system and its environment to identify potential Improvements • Activities in Systems Analysis • Preliminary Survey • Feasibility Study • Reasons for Initiating Systems Analysis • Existing System Inadequate • Totally new information requirement • To take advantage of New Technology

  18. System Design • Translate the recommendations made in Systems Analysis into a form that can be implemented • Activities in System Design • Preliminary Design • Identify inputs, outputs, processes • high level description of the system • Detailed Specification • Detailed description of all inputs, outputs and processes

  19. System Implementation • To create a workable system • Activities - Programming - Equipment Installation - Testing - Training - Conversion

  20. Systems Operation • The period of time during which the users utilize the system • Activities during Operation - Post-implementation Review - System Maintenance

  21. Formal System Development Methodologies • Structured Systems Analysis - Use of Data Flow Diagrams • Structured System Design - Modular Approach - Structure Charts • CASE Tools • Computer Aided Software Engineering

  22. Prototyping • A Small project team quickly creates a high level, working model of the system. Users then revise this model until they are satisfied. • An alternative to SDLC • Good for relatively small AIS projects • Iterative in nature • Less structured • Allows more flexibility

  23. Steps in Prototyping • Analysis • An incomplete paper model • Database Development • Test database using relational DBMS • Menu Development • To identify functions to be performed • Function Development • Describe functional modules • Protytype Iteration • Create each module and make changes to satify user • Detailed Specifications • Refine the system, make it ready for production

  24. Auditor Involvement in SDLC • During Systems Analysis Phase • Provide audit reports on the system under study • During System Design Phase • Review the proposed design for reports, processing steps, equipment selection and Data files, computer and internal control design • Ensure the existence of Audit Trail • During Systems Implementation Phase • Testing, reviewing adequacy of test data • Review conversion procedures • During Systems Operation Phase • Assess adequacy of internal controls

More Related