System Implementation System Analysis and Design System Implementation - Mr. Ahmad Al-Ghoul In the pervious sequence we explained the operational and test environment, training plan and data conversion process. In this sequence we will describe the system changeover methods, explain the post implementation evaluation and the final report that you will deliver to management

System Analysis and Design System Implemantation learning Objectives Identify and describe changeover methods Explain post-implementation evaluation Describe the final report to management Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation System Changeover System changeover is the process of putting the new information system online and retiring the old system The four changeover methods are direct cutover, parallel operation, pilot operation, and phased operation Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation System Changeover Direct Cutover The direct cutover approach causes the changeover from the old system to the new system to occur immediately when the new system becomes operational. Usually is the least expensive changeover method Involves more risk than other changeover methods, because some difficulties can arise when the system goes into operation Detecting minor errors is more difficult because users cannot verify current output by comparing it to output from the old system Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation System Changeover Direct Cutover Most systems operate on weekly, monthly, quarterly, and yearly cycles Companies often choose the direct cutover method for implementing commercial software packages Cyclical information systems usually are converted using the direct cutover method at the beginning of a quarter, calendar year, or fiscal year Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation System Changeover Parallel Operation The parallel operation changeover method requires that both the old and the new information systems operate fully for a specified period. Data is input into both systems, and output generated by the new system is compared with the equivalent output from the old system. The obvious advantage is lower risk If the new system does not work correctly, you can use the old system as a backup Easier to verify that the new system is working properly under parallel operation than under direct cutover Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation System Changeover Parallel Operation It is the most costly changeover method Running both systems might place a burden on the operating environment and cause processing delay Is not practical if the old and new systems are incompatible technically Also is inappropriate when the two systems perform different functions Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation System Changeover Pilot Operation The pilot operation changeover method involves implementing the complete new system at a selected location of the company. The group that uses the new system first is called the pilot site The old system continues to operate for the entire organization After the system proves successful at the pilot site, it is implemented in the rest of the organization, usually using the direct cutover method Restricting the implementation to a pilot site reduces the risk of system failure Is a combination of parallel operation and direct cutover methods Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation System Changeover Phased Operation The phased operation method allows you to implement a new system in stages, or modules. You give a part of the system to all users The risk of errors or failures is limited to the implemented module only Is less expensive than full parallel operation Is not possible, however, if the system cannot be separated easily into logical modules or segments Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation System Changeover Relative risk and cost characteristics of the four changeover methods. Avicenna System Analysis and Design System Implemantation

Post-Implementation Tasks A post-implementation evaluation assesses the overall quality of the information system. The evaluation verifies that the new system meets specified requirements, complies with user objectives, and achieves the anticipated benefits. In addition, by providing feedback to the development team, the evaluation also helps improve IT development practices for future projects. Avicenna System Analysis and Design System Implemantation

Post-Implementation Tasks Post-Implementation Evaluation Includes feedback for the following areas: Accuracy, completeness, and timeliness of information system output User satisfaction System reliability and maintainability Adequacy of system controls and security measures Hardware efficiency and platform performance Avicenna System Analysis and Design System Implemantation

Post-Implementation Tasks Post-Implementation Evaluation Includes feedback for the following areas: Effectiveness of data base implementation Performance of the IT team Completeness and quality of documentation Quality and effectiveness of training Accuracy of cost-benefit estimates and development schedules Avicenna System Analysis and Design System Implemantation

Post-Implementation Tasks Post-Implementation Evaluation When evaluating a system, you should: Interview members of management and key users Observe users and computer operations personnel actually working with the new information system Read all documentation and training materials Avicenna System Analysis and Design System Implemantation

Post-Implementation Tasks Post-Implementation Evaluation When evaluating a system, you should: Examine all source documents, output reports, and screen displays Use questionnaires to gather information and opinions form a large number of users Analyze maintenance and help desk logs Whenever possible, people who were not directly involved in developing the system should conduct the post-implementation evaluation Avicenna System Analysis and Design System Implemantation

Post-Implementation Tasks Post-Implementation Evaluation Users can forget details of the developmental effort if too much time elapses Pressure to finish the project sooner usually results in an earlier evaluation in order to allow the IT department to move on to other tasks Ideally, conducting a post-implementation evaluation should be standard practice for all information systems projects Avicenna System Analysis and Design System Implemantation

Why Implementation Sometimes Fails Two conditions necessary for a successful implementation Management support of the system under development Involvement of users in the development process Avicenna System Analysis and Design System Implemantation

Why Implementation Sometimes Fails Insights about implementation process Risk Commitment to the project Commitment to change Extent of project definition and planning Realistic user expectations Implementation success factors Extent to which system is used User’s satisfaction with system Avicenna System Analysis and Design System Implemantation

Post-Implementation Tasks Final Report to Management Your report should include the following: Final versions of all system documentation Planned modifications and enhancements to the system that have been identified Recap of all systems development costs and schedules Avicenna System Analysis and Design System Implemantation

Post-Implementation Tasks Final Report to Management Your report should include the following: A comparison of actual costs and schedules to the original estimates Post-implementation evaluation, if it has been performed. The final report to management marks the end of systems development work Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation Sequence Summary System changeover is the process of putting the new system into operation Four changeover methods exist: direct cutover, parallel operation, pilot operation, and phased operation A post-implementation evaluation assesses and reports on the quality of the new system and the work done by the project team The evaluation should be conducted early so users have a fresh recollection of the development effort, but not before users have experience using the new system The final report to management includes the final system documentation, describes any future system enhancements that already have been identified, and details the project costs The report represents the end of the development effort and the beginning of the new system’s operational life Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation Sequence Summary In this Sequence we have Identified and described changeover methods including, direct cutover, parallel operation, pilot operation, and phased operation Explained post-implementation evaluation tasks Discussed why implementation sometimes fails Explained the importance of final report to managers and what it should includes Avicenna System Analysis and Design System Implemantation

System Analysis and Design System Implemantation Reference [1] System Analysis and Design, Sixth Edition Authors: Gary B. Shelly, Thomas J. Cashman and Harry J. Rosenblatt Publisher: SHELLY CASHMAN SEWIES. Avicenna System Analysis and Design System Implemantation