1. Post Implementation Review The Post Implementation Review is carried out once the system is fully operational. The Post Implementation Review is carried out once the system is fully operational. The review is carried out by the development team of analysts, designers and programmers but also involves the client and end users of the system. The review is carried out by the development team of analysts, designers and programmers but also involves the client and end users of the system. The Post Implementation Review determines how well the system is working and whether or not improvements to the system will be necessary at a later stage. The Post Implementation Review determines how well the system is working and whether or not improvements to the system will be necessary at a later stage. The Post Implementation Review is a form of evaluation of the system. The Post Implementation Review is a form of evaluation of the system.

2. Post Implementation Review After the system is implemented and conversion is complete, a Post Implementation Review(PIR) of the system is conducted by users and developers alike. After the system is implemented and conversion is complete, a Post Implementation Review(PIR) of the system is conducted by users and developers alike. This is a formal process to determine how well the system is working, how it has been accepted and whether adjustments are needed. This is a formal process to determine how well the system is working, how it has been accepted and whether adjustments are needed. The review is also important to gather information for the maintenance of the system. The post implementation review provides the first source of information for maintenance purposes. The review is also important to gather information for the maintenance of the system. The post implementation review provides the first source of information for maintenance purposes. The most fundamental concern during the post implementation review is determining whether or not the system has met its objectives. The analyst will want to know if the performance of the users has improved and if the system is producing the result intended The most fundamental concern during the post implementation review is determining whether or not the system has met its objectives. The analyst will want to know if the performance of the users has improved and if the system is producing the result intended

3. Post Implementation Review Usually, members of the project team will want to complete the review as a natural extension of their responsibility to develop and deliver the system. They understand what was required, what was changed, how it was achieved and how things are supposed to work. Usually, members of the project team will want to complete the review as a natural extension of their responsibility to develop and deliver the system. They understand what was required, what was changed, how it was achieved and how things are supposed to work. However, many people feel that the review should be performed by an independent team. This reduces the risk that any errors or omissions in the system could be overlooked during the review. However, many people feel that the review should be performed by an independent team. This reduces the risk that any errors or omissions in the system could be overlooked during the review. One common solution is to do both. One common solution is to do both.

4. Post Implementation Review The purpose of the Post Implementation Review is to: The purpose of the Post Implementation Review is to: determine the extent to which the project met its objectives, planned benefits and addressed requirements as originally defined; determine the extent to which the project met its objectives, planned benefits and addressed requirements as originally defined; examine all aspects of the system to see if further improvements can be made to optimise the benefits delivered. These would be carried out during future maintenance of the system; examine all aspects of the system to see if further improvements can be made to optimise the benefits delivered. These would be carried out during future maintenance of the system; find out users' perspective of the system - do they like it, is it easy to use, what difficulties have they come across? find out users' perspective of the system - do they like it, is it easy to use, what difficulties have they come across?

5. Post Implementation Review The purpose of the Post Implementation Review is to: The purpose of the Post Implementation Review is to: determine the extent to which the project met its objectives, planned benefits and addressed requirements as originally defined; determine the extent to which the project met its objectives, planned benefits and addressed requirements as originally defined; examine all aspects of the system to see if further improvements can be made to optimise the benefits delivered. These would be carried out during future maintenance of the system; examine all aspects of the system to see if further improvements can be made to optimise the benefits delivered. These would be carried out during future maintenance of the system; find out users' perspective of the system - do they like it, is it easy to use, what difficulties have they come across? find out users' perspective of the system - do they like it, is it easy to use, what difficulties have they come across? The Post-Implementation Review should be scheduled some time after the solution has been fully deployed. Typical periods range from 6 weeks to 6 months, depending on the complexity of the system. The Post-Implementation Review should be scheduled some time after the solution has been fully deployed. Typical periods range from 6 weeks to 6 months, depending on the complexity of the system. It should not be performed while the initial snags are still being dealt with or while users are still being trained and getting used to its operation. It should not be performed while the initial snags are still being dealt with or while users are still being trained and getting used to its operation.

6. Post Implementation Review Typical evaluation criteria include: Typical evaluation criteria include: functionality, functionality, speed of processing, speed of processing, accuracy and reliability of processing results, accuracy and reliability of processing results, quality of output, quality of output, ease of use, ease of use, robustness, robustness, compatibility with other systems, compatibility with other systems, security, security, possible improvements and future maintenance needs. possible improvements and future maintenance needs. A suitable list of evaluation criteria should be drawn up to cover all elements of the operational solution. The criteria must focus on the purpose of the Post Implementation Review, namely: A suitable list of evaluation criteria should be drawn up to cover all elements of the operational solution. The criteria must focus on the purpose of the Post Implementation Review, namely: to determine the extent to which the system meets its requirements; to determine the extent to which the system meets its requirements; to determine how easy the system is to use; to determine how easy the system is to use; to determine requirements for future maintenance. to determine requirements for future maintenance.

7. Post Implementation Review The Post Implementation Review should be carried out using a combination of investigative techniques including interviews, examination of documentation, performance statistics, hands-on tests and checks: The Post Implementation Review should be carried out using a combination of investigative techniques including interviews, examination of documentation, performance statistics, hands-on tests and checks: Interviews of management and end users of the system; Interviews of management and end users of the system; Observation of end users actually working with the new information system; Observation of end users actually working with the new information system; Read all documentation and training materials; Read all documentation and training materials; Examine all source documents, output reports, and screen displays; Examine all source documents, output reports, and screen displays; Analyse maintenance and help desk logs; Analyse maintenance and help desk logs; Use questionnaires to gather information and opinions from a large number of users. Use questionnaires to gather information and opinions from a large number of users.

8. Post Implementation Review The Post Implementation Review assesses the overall quality of the information system. It checks whether or not the new system meets specified requirements and achieves the anticipated benefits. The requirements and expected benefits should have been defined in the System Specification. The Post Implementation Review assesses the overall quality of the information system. It checks whether or not the new system meets specified requirements and achieves the anticipated benefits. The requirements and expected benefits should have been defined in the System Specification. In order to determine the degree to which the operational system matches the system specification, each requirement listed should be considered individually by the evaluation team. The Post Implementation Review must: In order to determine the degree to which the operational system matches the system specification, each requirement listed should be considered individually by the evaluation team. The Post Implementation Review must: cover all requirements listed in the system specification; cover all requirements listed in the system specification; describe the extend to which those requirements have been achieved; describe the extend to which those requirements have been achieved; make recommendations in any case where a requirement has not fully been met or a problem has been identified. make recommendations in any case where a requirement has not fully been met or a problem has been identified.

9. Post Implementation Review The Post Implementation Review must take account of the views and opinions of end users of the operational system. The Post Implementation Review must take account of the views and opinions of end users of the operational system. Feedback from users is useful in determining how well the system meets its requirements and identifying possible improvements to the system. Feedback from users is useful in determining how well the system meets its requirements and identifying possible improvements to the system. User feedback is essential, however, when measuring the user friendliness of the system and determining its ease of use. User feedback is essential, however, when measuring the user friendliness of the system and determining its ease of use. Users of the system should be asked to evaluate: Users of the system should be asked to evaluate: the overall performance of the system, the overall performance of the system, user-friendliness of the system, user-friendliness of the system, completeness and quality of documentation, completeness and quality of documentation, quality and effectiveness of training. quality and effectiveness of training.

10. Post Implementation Review During the Post Implementation Review, all aspects of the system are examined to see if further improvements can be made to maximise the benefits delivered. Any such improvements would be carried out during future maintenance of the system. During the Post Implementation Review, all aspects of the system are examined to see if further improvements can be made to maximise the benefits delivered. Any such improvements would be carried out during future maintenance of the system. The Post Implementation Review should also contain recommended actions in any situation where a requirement has not fully been met or a problem has been identified. These actions would be carried out during future maintenance of the system. The Post Implementation Review should also contain recommended actions in any situation where a requirement has not fully been met or a problem has been identified. These actions would be carried out during future maintenance of the system. Maintainability refers to the ease with which a system can be understood, corrected, adapted or enhanced. Maintainability can be enhanced by: Maintainability refers to the ease with which a system can be understood, corrected, adapted or enhanced. Maintainability can be enhanced by: good initial design; good initial design; comprehensive and accurate system design documentation; comprehensive and accurate system design documentation; use of standards (design, language, coding, etc.) throughout the development; use of standards (design, language, coding, etc.) throughout the development; availability of extensive test cases. availability of extensive test cases.

11. Maintenance Maintenance, in fact, isn't part of the implementation process. It can only begin after the fully functional system has been released and is in use. In other words, maintenance takes place after the system has been fully implemented. In the Systems Analysis and Design Life Cycle, maintenance is listed as a separate stage of the development process. Maintenance, in fact, isn't part of the implementation process. It can only begin after the fully functional system has been released and is in use. In other words, maintenance takes place after the system has been fully implemented. In the Systems Analysis and Design Life Cycle, maintenance is listed as a separate stage of the development process. Maintenance involves making changes to the system to improve it or adapting it in some way. Since the system is already fully functional, system design documentation will already exist. This is used by the maintenance team to provide them with an understanding of the structures within the system. Maintenance involves making changes to the system to improve it or adapting it in some way. Since the system is already fully functional, system design documentation will already exist. This is used by the maintenance team to provide them with an understanding of the structures within the system.

12. Maintenance Maintenance refers to any changes that need to be made to a product after it has been handed over to the client. The maintenance of existing software can account for over 60% of all development effort. In this topic we will consider different types of maintenance that can be carried out on an existing database system. Maintenance refers to any changes that need to be made to a product after it has been handed over to the client. The maintenance of existing software can account for over 60% of all development effort. In this topic we will consider different types of maintenance that can be carried out on an existing database system. Maintenance is not just about "fixing mistakes" but also includes any post-delivery modification to an existing system. Because a database system consists of more than just database structures and scripts, any changes to documentation, manuals, or any other component of the product are also examples of maintenance. Maintenance is not just about "fixing mistakes" but also includes any post-delivery modification to an existing system. Because a database system consists of more than just database structures and scripts, any changes to documentation, manuals, or any other component of the product are also examples of maintenance.

13. Maintenance Maintenance can be categorised into the following four types: Maintenance can be categorised into the following four types: Corrective maintenance; Corrective maintenance; Adaptive maintenance; Adaptive maintenance; Perfective maintenance; Perfective maintenance; Preventive maintenance. Preventive maintenance.

14. Maintenance Corrective maintenance is the most burdensome part of systems maintenance, because it corrects design, coding and implementation errors that should never have occurred. Corrective maintenance is the most burdensome part of systems maintenance, because it corrects design, coding and implementation errors that should never have occurred. Since testing of the system should have been systematic and thorough, errors that are discovered after a system is fully operational tend to be very obscure. Since testing of the system should have been systematic and thorough, errors that are discovered after a system is fully operational tend to be very obscure. The need for corrective maintenance can often be traced to poor design during the Systems Analysis and Design Life Cycle. The need for corrective maintenance can often be traced to poor design during the Systems Analysis and Design Life Cycle. Corrective maintenance may be needed to correct residual faults in specification, design, coding and documentation. Corrective maintenance may be needed to correct residual faults in specification, design, coding and documentation. Often, corrective maintenance involves an urgent or emergency condition that calls for immediate attention. Often, corrective maintenance involves an urgent or emergency condition that calls for immediate attention. The ability to diagnose and remedy the errors or malfunction rapidly is of considerable value to the organisation. The ability to diagnose and remedy the errors or malfunction rapidly is of considerable value to the organisation. This type of maintenance is necessary because it is accepted that testing of the system will never detect all errors and bugs in a large complex database system. This type of maintenance is necessary because it is accepted that testing of the system will never detect all errors and bugs in a large complex database system. During operational use of any large system, errors will occur and be reported to the developer. The process that includes diagnosis and correction of one or more such errors is corrective maintenance. During operational use of any large system, errors will occur and be reported to the developer. The process that includes diagnosis and correction of one or more such errors is corrective maintenance.

15. Maintenance Adaptive maintenance is performed to satisfy changes in the processing or data environment and meet new user requirements. Adaptive maintenance is performed to satisfy changes in the processing or data environment and meet new user requirements. The environment in which the system operates is dynamic therefore the system must continue to respond to changing user requirements. The environment in which the system operates is dynamic therefore the system must continue to respond to changing user requirements. For example, a new tax law may require a change in calculation of net pay. Or a new report is required, or a new accounting method must be installed before the end of the financial year. For example, a new tax law may require a change in calculation of net pay. Or a new report is required, or a new accounting method must be installed before the end of the financial year. Generally, adaptive maintenance is good and inevitable. Generally, adaptive maintenance is good and inevitable. Information systems don't function in isolation. Information systems don't function in isolation. Typically, they interact with operating systems, database systems, network protocols, other external software packages, and various hardware platforms. Typically, they interact with operating systems, database systems, network protocols, other external software packages, and various hardware platforms. Adaptive maintenance is necessary because of the rapid change that is encountered in every area of computing. New generations of hardware are announced on a 24-month cycle; new operating systems or new releases of old ones appear regularly; peripheral equipment and other system elements are frequently upgraded or modified. Adaptive maintenance is necessary in order to modify software to properly interface with a changing environment. As the specifications of computer systems change, reflecting changes in the external world, so must the systems themselves. Adaptive maintenance is necessary because of the rapid change that is encountered in every area of computing. New generations of hardware are announced on a 24-month cycle; new operating systems or new releases of old ones appear regularly; peripheral equipment and other system elements are frequently upgraded or modified. Adaptive maintenance is necessary in order to modify software to properly interface with a changing environment. As the specifications of computer systems change, reflecting changes in the external world, so must the systems themselves.

16. Maintenance Perfective maintenance enhances the performance of an operational system. Perfective maintenance enhances the performance of an operational system. It allows the system to meet user requirements that were unrecognised when the system was originally developed. Users and developers are never satisfied. It allows the system to meet user requirements that were unrecognised when the system was originally developed. Users and developers are never satisfied. Even if a system is wildly successful, someone will want new or enhanced features added to it. Even if a system is wildly successful, someone will want new or enhanced features added to it. For example, users may want to change the way that a certain component of the system works or may want to improve the user- friendliness of the system. The process of receiving suggestions and requests for such enhancements or modifications, evaluating their effects, and implementing them is called perfective maintenance. For example, users may want to change the way that a certain component of the system works or may want to improve the user- friendliness of the system. The process of receiving suggestions and requests for such enhancements or modifications, evaluating their effects, and implementing them is called perfective maintenance. Perfective maintenance accounts for the majority of all maintenance work. As soon as the success of a software package has been acknowledged by the user, recommendations for new capabilities, modifications to existing functions and suggestions for general enhancements are received. To satisfy these requests, perfective maintenance is necessary Perfective maintenance accounts for the majority of all maintenance work. As soon as the success of a software package has been acknowledged by the user, recommendations for new capabilities, modifications to existing functions and suggestions for general enhancements are received. To satisfy these requests, perfective maintenance is necessary

17. Maintenance Preventive maintenance consists of periodic inspection and review of the system to uncover and anticipate problems. Preventive maintenance consists of periodic inspection and review of the system to uncover and anticipate problems. As members of the maintenance team with a system, they often find defects that signal potential errors. As members of the maintenance team with a system, they often find defects that signal potential errors. While not requiring immediate attention, these defects, if not corrected in their minor stages, could significantly affect either the functioning of the system or the ability to maintain the system in the future. While not requiring immediate attention, these defects, if not corrected in their minor stages, could significantly affect either the functioning of the system or the ability to maintain the system in the future. Preventative maintenance refers to changes to the system which seek to avoid problems associated with some future crises. Preventative maintenance refers to changes to the system which seek to avoid problems associated with some future crises. The identification and removal of the Y2K bug is an example of preventive maintenance. The identification and removal of the Y2K bug is an example of preventive maintenance.

18. Maintenance It is estimated that on average, maintenance accounts for 70% of the total cost of the product. Arguably one of the most difficult tasks in the Systems Analysis and Design Life Cycle, maintenance is usually assigned to junior member of an organisation, leaving development of new systems to the better or more experienced members of the team. Maintenance becomes difficult when previously undetected errors cannot be traced. There can be a number of reasons for this including: It is estimated that on average, maintenance accounts for 70% of the total cost of the product. Arguably one of the most difficult tasks in the Systems Analysis and Design Life Cycle, maintenance is usually assigned to junior member of an organisation, leaving development of new systems to the better or more experienced members of the team. Maintenance becomes difficult when previously undetected errors cannot be traced. There can be a number of reasons for this including: Inadequate system design documentation showing software design and structure; Inadequate system design documentation showing software design and structure; Loss of first-hand knowledge of system due to staff turnover; Loss of first-hand knowledge of system due to staff turnover; Previous maintenance and changes have not adequately documented making it difficult to track changes. Previous maintenance and changes have not adequately documented making it difficult to track changes. When maintenance of an operational system is being carried out, there is an overall loss in productivity since the system will not be available at points when it is being updated. All maintenance activities inevitably lead to changes in the system. When maintenance of an operational system is being carried out, there is an overall loss in productivity since the system will not be available at points when it is being updated. All maintenance activities inevitably lead to changes in the system. Maintainability refers to the ease with which software can be understood, corrected, adapted or enhanced. Maintainability can be enhanced by: Maintainability refers to the ease with which software can be understood, corrected, adapted or enhanced. Maintainability can be enhanced by: good initial design, good initial design, comprehensive and accurate system design documentation, comprehensive and accurate system design documentation, use of standards (design, language, coding, etc.) throughout the development, use of standards (design, language, coding, etc.) throughout the development, availability of extensive test cases. availability of extensive test cases.