Table of Contents | Chapter 9 | Chapter 11
10.0 OBJECTIVE
10.1 TASKS AND ACTIVITIES
10.1.1 Notify
users of new implementation
10.1.2
Execute training plan
10.1.3 Perform
data entry or conversion
10.1.4
Install system
10.1.5 Conduct
post-implementation review
10.1.6
Revise previous documentation
10.2 ROLES AND RESPONSIBILITIES
10.3 DELIVERABLES
10.3.1
Delivered System
10.3.2
Change Implementation Notice
10.3.3
Version Description Document
10.3.4
Post-Implementation Review
In this phase, the system or system modifications are installed and made operational in a production environment. The phase is initiated after the system has been tested and accepted by the user and Project Manager. Activities in this phase include notification of implementation to end users, execution of the previously defined training plan, data entry or conversion, and post implementation review. This phase continues until the system is operating in production in accordance with the defined user requirements.
The new system can fall into three categories, replacement of a manual process, replacement of a legacy system, or upgrade to an existing system. Regardless of the type of system, all aspects of the implementation phase should be followed. This will ensure the smoothest possible transition to the organization’s desired goal.
Tasks and activities in the implementation phase are associated with certain deliverables described in section 10.3. The tasks and activities actually performed depend on the nature of the project. Guidelines for selection and inclusion of tasks for the Implementation Phase may be found in Chapter 13, Alternate SDLC Work Patterns. A description of these tasks and activities is provided below.
The implementation notice should be sent to all users and organizations affected by the implementation. Additionally, it is good policy to make internal organizations not directly affected by the implementation aware of the schedule so that allowances can be made for a disruption in the normal activities of that section. Some notification methods are email, internal memo to heads of departments, and voice tree messages. The notice should include:
It is always a good business practice to provide training before the end user uses the new system. Because there has been a previously designed training plan established, complete with the system user manual, the execution of the plan should be relatively simple. Typically what prevents a plan from being implemented is lack of funding. Good budgeting should prevent this from happening.
With the implementation of any system, typically there is old data which is to be included in the new system. This data can be in a manual or an automated form. Regardless of the format of the data, the tasks in this section are two fold, data input and data verification. When replacing a manual system, hard copy data will need to be entered into the automated system. Some sort of verification that the data is being entered correctly should be conducted throughout this process. This is also the case in data transfer, where data fields in the old system may have been entered inconsistently and therefore affect the integrity of the new database. Verification of the old data becomes imperative to a useful computer system.
One of the ways verification of both system operation and data integrity can be accomplished is through parallel operations. Parallel operations consists of running the old process or system and the new system simultaneously until the new system is certified. In this way if the new system fails in any way, the operation can proceed on the old system while the bugs are worked out.
To ensure that the system is fully operational, install the system in a production environment.
After the system has been fielded a post-implementation review is conducted to determine the success of the project through it’s implementation phase. The purpose of this review is to document implementation experiences to recommend system enhancements and provide guidance for future projects.
In addition, change implementation notices will be utilized to document user requests for fixes to problems that may have been recognized during this phase. It is important to document any user request for a change to a system to limit misunderstandings between the end user and the system programmers.
During this phase, the ICD is revised from the Requirements Analysis Phase. The CONOPS, System Security Plan, Security Risk Assessment, Software Development Document, System Software and the Integration Document are also revised and finalized during the Implementation Phase.
The following deliverables are initiated during the Implementation Phase:
After the Implementation Phase Review and Approval Certification is signed by the Project Manager and the System Proponent representative, the system - including the production version of the data repository - is delivered to the customer for the Operations and Maintenance Phase.
A formal request and approval document for changes made during the Implementation Phase. Appendix C-32 provides a template for a Change Implementation Notice.
The primary configuration control document used to track and control versions of software released to the operational environment. It is a summary of the features and contents for the software build and identifies and describes the version of the software being delivered. Appendix C-33 provides a template for a Version Description Document.
The review is conducted at the end of the Implementation Phase. A post-implementation review shall be conducted to ensure that the system functions as planned and expected; to verify that the system cost is within the estimated amount; and to verify that the intended benefits are derived as projected. Normally, this shall be a one-time review, and it occurs after a major implementation; it may also occur after a major enhancement to the system. The results of an unacceptable review are submitted to the System Proponent for its review and follow-up actions. The System Proponent may decide it will be necessary to return the deficient system to the responsible system development Project Manager for correction of deficiencies. Appendix C-34 provides a template for a Post-Implementation Review.
Once a system has been developed, tested and deployed it will enter the operations and maintenance phase. All development resources and documentation should be transferred to a library or the operations and maintenance staff.
During the Implementation Phase Review, recommendations may be made to correct errors, improve user satisfaction or improve system performance. For contractor development, analysis shall be performed to determine if additional activity is within the scope of the statement of work or within the original contract. An Implementation Phase Review and Approval Certification should be signed off by the Project Manager to verify the acceptance of the delivered system by the system users/owner.
The Implementation Phase-End Review shall be organized, planned, and led by the Project Quality Assurance representative.