1. system conversion project review project deliverable: the final report programmed reviews types of system maintenance information system obsolescence maintenance contacting the cornucopia case portfolio project chapter15 Systems Analysis and Design for the Small Enterprise section V Implementation

2. System Conversion 2 Chapter 15 Systems Analysis and Design for the Small Enterprise Although the analyst might find some of the new system files already exist in machine- readable format, but they require modification to add or delete fields or to change the file organization or medium. In addition, some new system files may not exist at all or exist only within a manual record-keeping system. System conversion involves all six components of an information system. The data component presents special problems:

3. Conversion Options 3 Chapter 15 Systems Analysis and Design for the Small Enterprise There are several ways in which to convert from the existing system to the new system, each with different costs and risks.

4. Figure 15-2: Conversion Options 4 Chapter 15 Systems Analysis and Design for the Small Enterprise Direct Conversion Parallel Conversion Phased Conversion

5. Figure 15-3: Conversion Cost and Risk 5 Chapter 15 Systems Analysis and Design for the Small Enterprise Direct Conversion Parallel Conversion Phased Conversion

6. Figure 15-4: Conversion Plan Outline 6 Chapter 15 Systems Analysis and Design for the Small Enterprise

7. Project Review 7 Chapter 15 Systems Analysis and Design for the Small Enterprise The project review provides an opportunity for the analyst and the user to evaluate the project in terms of its success or failure to meet the project specifications. The summarized results of the project review should be recorded and annotated with any information that will help the analyst and the user with future projects.

8. Project Deliverable: The Final Report 8 Chapter 15 Systems Analysis and Design for the Small Enterprise 1. A cover page transmitting the working product to the user 2. Brief summary of the overall effort 3. Suggested future enhancements 4. Description of the need for ongoing system maintenance While there is no standard format for the final report, it should contain several elements: Note: The final report is distinct from the product documentation manuals.

9. Figure 15-7: Contents of Final Report 9 Chapter 15 Systems Analysis and Design for the Small Enterprise

10. Programmed Review 10 Chapter 15 Systems Analysis and Design for the Small Enterprise A programmed review is a systematic evaluation of all facets of an operational information system. Its purpose is to determine how well the system functions when compared to its own, or to industry-established performance norms. Programmed reviews should occur regularly throughout the maintenance and review phase of the SDLC.

11. Information System Programmed Review 11 Chapter 15 Systems Analysis and Design for the Small Enterprise Periodic programmed reviews occur during the maintenance and review phase of the life cycle

12. Types of System Maintenance 12 Chapter 15 Systems Analysis and Design for the Small Enterprise 1.Positioning within the SDLC model 2.Associated complexity and cost 3.Impact on the information system There are several types of system maintenance, each differing in terms of:

13. Types of Information System Maintenance 13 Chapter 15 Systems Analysis and Design for the Small Enterprise

14. Preventive Maintenance Tasks 14 Chapter 15 Systems Analysis and Design for the Small Enterprise

15. Information System Obsolescence 15 Chapter 15 Systems Analysis and Design for the Small Enterprise Eventually, every information system must be replaced. Functional obsolescence describes a system that can no longer satisfy the information needs of the user. As an information system approaches functional obsolescence, maintenance costs begin to rise steadily. These costs may continue to rise as analysts try to keep the system operational or they may actually level off, indicating a reluctance to devote more resource to alter a product at the end of its useful life.

16. Chapter Summary Chapter 15 16 Many cutover phase activities begin well before the system becomes operational The project should be evaluated and brought to a definitive close by signing a user acceptance form System maintenance is by far the longest period of the SDLC and often has a tremendous influence on the overall success of a product Obsolescence is a natural part of the SDLC Systems Analysis and Design for the Small Enterprise