 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood 11 - 1 Systems Development: A Survey Chapter 11.

Slides:



Advertisements
Similar presentations
System Development Life Cycle (SDLC)
Advertisements

Systems Implementation and Operation
Systems Development Environment
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
The System Development Life Cycle
Systems Development and Analysis
11.1 Lecture 11 CASE tools IMS Systems Design and Implementation.
Lab/Sessional -CSE-374. SYSTEM DEVELOPMENT LIFE CYCLE.
6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice Hall Building Information Systems Chapter 13 VIDEO CASES Video Case 1: IBM: Business.
Discovering Computers Fundamentals, 2011 Edition Living in a Digital World.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Chapter 1 Assuming the Role of the Systems Analyst
Lecture 13 Revision IMS Systems Analysis and Design.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 18-1 Accounting Information Systems 9 th Edition Marshall.
Computers: Tools for an Information Age
Chapter 1 Assuming the Role of the Systems Analyst
System Development Life Cycle (SDLC)
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
7.2 System Development Life Cycle (SDLC)
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 16-1 Accounting Information Systems 9 th Edition Marshall.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Chapter 22 Systems Design, Implementation, and Operation Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 22-1.
Chapter 8: Systems Development Please turn your cell phone off.
Systems Analysis and Design: The Big Picture
 2004 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, by Bodnar/Hopwood 11 – 1 Chapter 11 Systems Implementation, Operation,
Chapter 10.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Laudon & Laudon: Canadian Edition
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
Managing the development and purchase of information systems (Part 1)
Systems Development and Analysis. ©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart Lecture 03-2 Introduction.
Introduction to Systems Development Life Cycle
Chapter 14 Information System Development
Computers Are Your Future © 2006 Prentice Hall, Inc.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Fundamentals of Information Systems, Third Edition1 Systems Design Answers the question “How will the information system do what it must do to solve a.
Systems Analysis and Design
Computers Are Your Future © 2008 Prentice Hall, Inc.
 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Planning, Analysis, and Design Chapter 12.
Computers Are Your Future Tenth Edition Chapter 13: Systems Analysis & Design Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall1.
 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Implementation, Operation, and Control Chapter.
 2004 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, by Bodnar/Hopwood 10 – 1 Systems Planning and Analysis Chapter 10.
 2004 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, by Bodnar/Hopwood 13 – 1 Chapter 13 Auditing Information Technology.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Systems Development Life Cycle (SDLC)
State of Georgia Release Management Training
The Planning Phase Recognize the problem MIS steering committee 7. ManagerSystems analyst Define the problem Set system objectives Identify system constraints.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
Accounting systems design & evaluation 9434SB 18 March 2002.
Chapter 1 Assuming the Role of the Systems Analyst.
The System Development Life Cycle
Fundamentals of Information Systems, Sixth Edition
Systems Planning and Analysis
Fundamentals of Information Systems, Sixth Edition
Systems Implementation,
Developing Information Systems
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
System Development Life Cycle (SDLC)
The System Development Life Cycle
CLINICAL INFORMATION SYSTEM
System Development Life Cycle (SDLC)
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Presentation transcript:

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Development: A Survey Chapter 11

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Overview l Systems development is the process of modifying or replacing a portion or all of an information system. l This process requires a substantial commitment of time and resources and is an ongoing activity in many organizations.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Organizational Context of Systems Development l In information systems terminology, a user or end user is an organizational function other than the information system function that requires computer data processing. l The information system function is separate from user functions.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Organizational Context of Systems Development Systems Analysis Systems Analysis Systems Design Systems Design Operations Users Information Systems System Output System Requirements

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Analysis l Systems analysis is responsible for the development of the general design of system applications. l Systems analysis works with users to define their specific information requirements. l These requirements are then communicated to the systems design function.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Analysis l There are four general phases in systems analysis: 1 Survey the existing system. 2 Identify the information needs of users. 3 Identify the system requirements that are necessary to satisfy the information needs of users. 4 Prepare a systems analysis report.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Design l What is systems design? l There are three general phases in systems design. l What are these three phases? 1 Evaluate alternative designs for the proposed system. 2 Prepare detailed design specifications. 3 Prepare the systems design report.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Operations l The operations subfunction of information systems actually operates the computer equipment. l Implementation occurs when newly developed systems are actually up and running on the computer equipment.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Development Life Cycle l Systems development projects normally are undertaken by a project team. l This team is composed of system analysts, programmers, accountants, and other people who are knowledgeable about or affected by the project. l Every systems development project goes through essentially the same life cycle.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Development Life Cycle Analysis Design Implementation

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Development Life Cycle l The life-cycle concept implies that each systems development project should be factored into a number of distinct phases with formal management control points. l The basic control principle is that each phase should generate documentation to be formally reviewed and approved prior to entering the next phase of a project’s life cycle.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Development Life Cycle General PhasesDetailed Phases AnalysisFeasibility assessment Information analysis AnalysisFeasibility assessment Information analysis Design System design Program development Design System design Program development ImplementationConversion Operation and maintenance Audit and review ImplementationConversion Operation and maintenance Audit and review

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Problems with Systems Development Life Cycle Wild EnthusiasmDisillusionment Total Confusion

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Problems with Systems Development Life Cycle Search for the Guilty Punishment of the Innocent Promotion of Nonparticipants

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Problems with Systems Development Life Cycle As Proposed by User Manager As Approved by the Steering Committee As Structured by the Data Administrator

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Problems with Systems Development Life Cycle As Designed by the Lead Analyst As Implemented by the Application Programmers What the User Actually Wanted

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Business Reengineering l What is business reengineering? l What has stimulated interest in business reengineering? – total quality performance (TQP), or TQM – trends in information services

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Business Reengineering l Business reengineering concerns business reinvention (not improvement), enhancement, or modification. l Business reengineering is concerned with multiplicative rather than marginal improvements in performance.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood The Role of Information Technology l Information technology is a powerful enabler of process innovation. l There are nine categories of ways in which information technology can support process innovation: 1 Automational support 2 Informational support

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood The Role of Information Technology 3 Sequential support 4 Tracking support 5 Analytical support 6 Geographical support 7 Integrative support 8 Intellectual support 9 Disintermediating support

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Documentation Standards l Documentation standards set forth explicit requirements for the documentation to be developed during a project. l The basic concept of system development standards is to define the phases in the systems development life cycle and to specify the documents that should be generated during each phase.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Overview of Systems Development Documentation l feasibility study ? l Logical flow diagrams ? l data dictionary ? l user specification ? l conceptual design report ? l systems design report ? l program description ?

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Overview of Systems Development Documentation l run manual ? l Data entry procedures ? l What is a conversion plan? l testing plan ?

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Overview of Systems Development Documentation Module A Module B Module C Old System New System Old System New System Immediate Cutover Phased Conversion Parallel Operation Time

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Maintenance of Systems Documentation Standards l Maintaining systems documentation standards and using them consistently in systems development are formidable tasks. l Documentation standards my be developed in-house or purchased from a vendor. l Documentation is frequently referred to as deliverables.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Analyst/Programmer Productivity Control l The major portion of total systems development costs is the salaries of analysts and programmers. l The end product of an analyst is a system design for a program, which is not as concrete as an actual program.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Analyst/Programmer Productivity Control l The use of structured analysis, design, and graphic techniques should increase the overall productivity of the analyst function. l Controls suggested for improving the productivity of programmers concern the way programs are designed and coded and the organization of programming personnel.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Structured Programming l What is structuring programming? l The team approach establishes a team consisting of a lead or chief programmer, assistant programmers as needed, and a programming secretary.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Structured Programming l Programmer productivity may also be increased through technical aids. l Special software packages, called preprocessors, and automated documentation systems also increase programmer productivity.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Computer-Aided Software Engineering (CASE) Diagramming Tools Diagramming Tools Repository Code Generation Code Generation Project Management Project Management Prototyping Syntax Verifiers Syntax Verifiers l What is computer-aided software engineering?

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Prototyping l What is prototyping? l Object-oriented technology includes object- oriented programming (OOP) and object- oriented databases. l The goal of object-oriented programming is to make software easier to create, simpler to use, and more reliable through reusability.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Object-Oriented Technology l An objet-oriented database stores both data and the procedures that operate on the data as a single unit, that is, an object. l With object-oriented programming, common functions are defined as objects and stored in a repository. l Parent objects contain code for common functions.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Program-Change Control l Program-change controls concern the maintenance of application programs. l The objective of such controls is to prevent unauthorized and potentially fraudulent changes from being introduced into previously tested and accepted programs. l Control of program changes involves documentation and review.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Database Administration l A major control activity of the DBA is to establish standards and documentation for the data elements in a database. l Database administration must deal with the issues of data security, integrity, data sharing, recovery/backup, and audit trails.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Planning and Organizing a Systems Project l Project selection is usually the responsibility of a steering committee or other organizationwide unit to assure active user participation in the selection process. l One important task of management is to assemble a suitable project team.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Project Team Organization Information Systems Department Steering Committee User Department Analysts/ Programmers Analysts/ Programmers Lead Analysts Lead Analysts Technical Staff Technical Staff User Member User Member Project Leader Project Leader

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Project Leader Responsibilities Progress and Time Reporting Allocation of Resources Status Reporting Task Assignment Activity Task/ Scheduling Project Breakdown SchedulingPlanningControl

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Factoring a Project into Phases and Tasks ImplementationAnalysisDesign New System Application Study Vendor Selection Output Design Form Design Program Design Equipment Delivery Documen- tation

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Work Measurement Techniques l The simplest approach to estimation is to guess. l More rigorous approaches to estimation are based on the concept of work measurement. 1 Identify the tasks to be estimated. 2 For each task, estimate the total size or volume of the task in some suitable manner.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Work Measurement Techniques 3 Convert the size or volume estimate into a time estimate by multiplying the size or volume estimate by a standard or estimated processing rate. 4 Adjust the estimated processing rate to include circumstantial considerations such as idle time, task complexity, or task newness.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Accuracy of Estimates l There is general agreement on several points related to the estimation process. 1 Estimates are only estimates. 2 Accuracy of estimation improves as a project proceeds through its course of activities. 3 Initial estimates are frequently made too low.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Project Accounting l A project accounting system is a cost accounting system in which costs are assigned to individual projects. l Effective project control requires a project accounting system that can keep track of costs incurred to date on a project and provide a summary cost report at a project’s completion.

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Project Accounting System Computer Usage Summaries Computer Usage Summaries Project Accounting System Project Accounting System Overhead Rates Overhead Rates Cost to Date Cost to Date Progress Report Progress Report Time Sheets Time Sheets Revised Cost Estimate Revised Cost Estimate

 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Project Accounting System Project Accounting System Project Accounting System Number Costs Actual Budget Materials XXX XXX LaborXXXXXXXX Overhead XXX XXX Project Schedule Number Costs Actual Budget Materials XXX XXX LaborXXXXXXXX Overhead XXX XXX Project Schedule Project File