Introduction     

This Quality Assurance Plan is intended to:

                                        Ensure that all steps of the project are monitored.

                                        Ensure proper user acceptance criteria for each type of testing.

                                        Determine signoff procedures for various milestones. Of certain data elements.

Process

                                        We will maintain quality assurance through testing, correction, re-testing, and review sessions. Although the bulk of the QA work will take place in the review sessions, before that happens we will conduct system tests and parallel tests.

System Tests

                                        For system testing:

·         Functional staff scripts and conducts system tests.

·         Technical staff makes programming changes.

·         Functional staff corrects tables.

·         Integration testing management reviews system test results.

Parallel tests  

                                     For parallel testing:

·         Functional and technical staff script and conduct parallel tests.                          

·         Technical staff makes programming changes.                            

·         Functional staff correct tables.

·         Functional and technical staff perform re-testing.

·         Determine necessary interfaces.

        Parallel tests:

                                                        Use converted data--automated and manual--to include interfaces in and out of system, most reports, and security setup. Simulate of varying processes and period ends.               

Quality Assurance Sessions:

                                        The Quality Assurance process will continue in the following sessions:

Budget

                                        The project director, monitored by the steering committee, reviews the budget for cost overrun potential, and actual versus budgeted dollars to date.

Project Plan:

                                        The project team and the steering committee, monitored by project management, review the project plan:

·         To ensure milestone dates are on target,

·         For any changes in scope, and

·         For possible trouble spots.

Communication Plan:

The communication plan is reviewed (monitored by the steering committee) to ensure that key dates are on target, ensure that communications are effective, and to alert the team to changes of scope.

NOTE: The Project Plan reviewer needs to be determined.

Issues-Log Document:

                                        The project team and the steering committee, monitored by project management, review the log document to ensure that:

·         Target dates for resolution are being met,

·         High priority items are being resolved, and

·         The project is not in jeopardy.

Fit/Gap Document:

                                        The project team reviews the fit gap document for

·         Completeness,

·         Scope of changes,

·         Conversion items,

·         Interface items,

·         Processes to be implemented,                                    

Data-mapping Documents:

            Functional and technical staff reviews the data mapping documents for completeness.            

Functional Requirement Documents:

             Functional and technical staff reviews the functional requirement documents.

Technical Requirement Documents:

           Functional and technical staff reviews the technical requirement documents  

Procedural Documentation:

                                 Functional and technical staff reviews procedural documentation.                                                                                                         

Training Materials:

        Functional managers review and sign off on training materials.

Systems Tests:

          Integration testing management reviews system tests                                               

Parallel Tests:  Parallel testing management reviews parallel tests.                                               

                        "Go No-Go" Decision:

                                        The entire team reviews all aspects of the implementation to determine readiness to continue. This review examines:                                       

This review examines:

·         The results of all testing,

·         Security readiness,

·         Hardware readiness,

·         Network readiness,

·         Database readiness, and

·         Production readiness.

                                        On completion, the project management writes their recommendation for approval by the steering committee.                                                      

Cutover Plan:

                                        A committee of the project team will write the cutover plan. The team will review the plan to be sure it documents every step of the cutover. Project management will approve the plan and submit it to the steering committee to sign off.

                        Post-Implementation Review:

                                        The post implementation review documents what we did right and wrong, and what we will improve. This will prove particularly useful when it is referred to in later phases of this project.