DISCUSS ANY FOUR APPROACHES TO SYSTEM CHANGEOVER

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Point of Sale (POS) Client & Back Office Server. Operational Concept What is our Objective? What is our Objective? What are our Goals? What are our Goals?
Systems Implementation and Operation
Data Conversion Khoo Kay Vin.
Changeover Lecture 12 Change-Over Strategies for Implementation 1 BTEC HNC Systems Support Castle College 2007/8.
ERP Implementation Strategies
Designing new systems or modifying existing ones should always be aimed at helping an organization achieve its goals State the purpose of systems design.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Chapter 8 System Implementation and Operation. Learning Objectives l To discover which activities take place during the third and fourth phases of the.
Chapter 2 Succeeding as a Systems Analyst
System Implementation
Chapter 23 Computerised accounting systems
Systems Analysis and Design (Level 3)
Introduction to Computer Technology
Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Information Technology Project Management by Jack T. Marchewka Power Point Slides by Jack T. Marchewka, Northern Illinois University Copyright 2006 John.
Information Technology Project Management By Denny Ganjar Purnama, MTI Universitas Pembangunan Jaya May 2014.
SDLC: Development Phase
System Development Life Cycle
Chapter 22 Systems Design, Implementation, and Operation Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 22-1.
Chapter 12 Implementation
Chapter 10.
Systems Implementation
12.
Design Completion A Major Milestone System is Presented to Users and Management for Approval.
CCSB223/SAD/CHAPTER141 Chapter 14 Implementing and Maintaining the System.
Laudon & Laudon: Canadian Edition
Chapter 8: Systems analysis and design
Question 23 As an accountant of an organization, discuss why it might be necessary to initiate systems analysis. {6 marks} Giving reasons for your answer,
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Systems Life Cycle 1.Project Idenification 2. Initial Investigation 3. Feasibilty Study 4. Analysis 5. Design 6. Development and testing 7. Implementation.
Fundamentals of Information Systems, Third Edition1 Systems Design Answers the question “How will the information system do what it must do to solve a.
 To help you understand and describe a range of methods for installing a new computer-based system; › Parallel › Phased › Direct › Pilot  Also, to help.
Principles of Information Systems Eighth Edition
Systems Life Cycle A2 Module Heathcote Ch.38.
System Conversion System Conversion is the process of changing from the old system to the new one. There are four methods of handling a systems conversion:
Methods of Installing a new computer-based system.
System Implementation. © 2011 Pearson Education, Inc. Publishing as Prentice Hall 2 Chapter 13 FIGURE 13-1 Systems development life cycle with the implementation.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
A BRIEF LOOK AT THE COMPONENTS THAT MAKE UP THE SYSTEM LIFE CYCLE.
1 Object-Oriented Analysis and Design with the Unified Process Figure 13-1 Implementation discipline activities.
Thepul Ginige Lecture-7 Implementation of Information System Thepul Ginige.
Modern Systems Analysis and Design Third Edition Chapter 2 Succeeding as a Systems Analyst 2.1.
Observing the Current System Benefits Can see how the system actually works in practice Can ask people to explain what they are doing – to gain a clear.
A brief look at the components that make up the system life cycle.
IT 21103/ System Analysis & Design. Chapter 14 Testing, Documentation, Training Chapter 15 Conversion, Maintenance, Review.
Prepared by: Arjaa Salem Makkawi ID: Sec : 2.
Thepul Ginige Lecture-5 Implementation of Information System Part - I Thepul Ginige.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 1 for testing you need: test data and test cases test plans and.
The information systems lifecycle Far more boring than you ever dreamed possible!
ICT IGCSE Theory – Revision Presentation The Systems Life Cycle Chapter 7: The Systems Life Cycle Analysis 7.2 Design 7.3 Development.
Accounting systems design & evaluation 9434SB 18 March 2002.
Core Concepts of ACCOUNTING INFORMATION SYSTEMS Moscove, Simkin & Bagranoff John Wiley & Sons, Inc. Developed by: S. Bhattacharya, Ph.D. Florida Atlantic.
Principles of Information Systems Eighth Edition Chapter 13 Systems Development: Design, Implementation, Maintenance, and Review.
OHT 10.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The testing process Determining the test methodology phase Planning.
Information Systems Development
System Conversion.
Information Systems Development
Conversion Strategies
Developing Information Systems
Information Technology Project Management – Fifth Edition
Information Systems Development
Systems Design, Implementation, and Operation
Lecture-5 Implementation of Information System Part - I Thepul Ginige
SYSTEMS ANALYSIS & DESIGN
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
Chapter 22, Part
3.3.5: Implementing computer-based information systems
Systems Development Lifecycle
What is a System? A system is a collection of interrelated components that work together to perform a specific task.
Presentation transcript:

DISCUSS ANY FOUR APPROACHES TO SYSTEM CHANGEOVER DISCUSS ANY FOUR APPROACHES TO SYSTEM CHANGEOVER.BRIEFLY OUTLINE THE ADVANTAGES AND DISADVANTAGES System changeover is the process of putting new information system online and retiring the old system, for instance, changing from a manual system to a computerised system

Direct change over/ Cold Turkey Cutover This is an approach where the old system is cut and overwritten by the new system, that is, the old system is stopped and the new system starts simultaneously and it becomes operational. It may be the only approach to take when two systems cannot co-exist or activating the new system is an emergency. An example can be the immediate switch from electricity to an automatic generator when there is a blackout in places like hospitals.

Advantages Less expensive and easy method as only one system is in use, unlike other approaches like the parallel approach. Has a short conversion time since the organisation immediately switches from the old system to the new system. There is no need for any interfaces between the old and the new system.

Disadvantages High risk of loss of data as a firm cannot revert to the old system as a backup plan. It involves more risk of total system failure as system errors that are not detected during the walk through and testing steps may materialise unexpectedly, which may disrupt the system. It also opens risk for the system not to be accepted by its users.

PARALLEL OPERATION The word parallel suggests things that are being run simultaneously It requires that both the old and new systems operate fully for a specified period of time When users, management and the information technology group are satisfied that the new system operates effectively and efficiently, the old system is then terminated.

ADVANTAGES Low risk is involved , if the new system does not work correctly the old system can be used as a back-up. By running two systems the user can reconcile outputs to identify debug errors before switching to the full operation of the new system. The old system can be used as back-up. Also, gives room to reversing the decision if the system fails to meet organisation objectives.

DISADVANTAGES It is costly as it essentially doubles resource consumption and data has to be input in both systems Users must work in both systems and it results in increased work load which can lead to overtime costs and processing delays. Increases or makes room for more errors as employees are expected to process all transactions twice.

PILOT OPERATION The method involves the implementation of the new system at a selected location/department/division within the organisation. It is mainly used by large organisations that have multiple locations or largely independent departments. The division or department that uses the system first is called the Pilot Site. The old system continues to operate within the entire organisation including the pilot site and if the system proves to be successful at the pilot site, it is implemented to the rest of the organisation.

ADVANTAGES Any implementation problems affect the pilot site only and not the whole organisations’ system, therefore any problems encountered can be rectified quickly, reducing system failure. It is less expensive as compared to parallel operation because pilot site only uses both the old and new system for a limited period of time. It can be designed or adjusted before putting it to the entire organisation. It is easier to monitor as focus is given to only one department.

DISADVANTAGES If the system that is implemented is successful in one department, it does not guarantee the success of the system in every department within the organisation as every department has its needs. Has a long conversion time There is a need for interfaces between old and new systems.

PHASE-IN OPERATION It is the implementation of the new system in modules or stages of phased operations for example one might implement the new system by starting with the sales sub-system followed by the inventory control subsystem and finally the purchases sub-system Implementing special conversion system that provide temporary interfaces during the change-over period can assist in the phase-in.

ADVANTAGES By phasing in the new system in modules, the risk of a system failure is reduced as the risk of errors or failures is limited to the implemented module only. It is less expensive than the full parallel operation method.

Disadvantages It can create incompatibilities between new subsystems and yet to be replaced subsystems. It limits the extent of implementation problem but may not be possible with other subsystems. It can be costly where the system involves a large number of separate phases.

The need for post implementation review; It can produce insight into ways to improve the process for the future system. To see if the system has achieved the organisation`s objective. To increase the efficiency of the system by correcting any errors in the implementation system. To measure the performance of the system against expectations . To add something new, if it is an in-house package. To check if the system is operating at full capacity. Improves the ability of analysts to evaluate costs and benefits. The knowledge of the review being performed motivates the members of the project design team. It helps in evaluating internal controls in the new system.

b) Why is post implementation review necessary for a new system?(8) A post implementation review`s objective is to measure the success of the system and processes. system designers and analysts strive to produce a system that is on time, on budget and meets user needs but it is not always possible.