MIS Policies Manual

Chapter 3: Systems Analysis and Design

Section 4: Systems Implementation

This section covers the procedures governing implementation of a proposed system.

1. Systems Implementation Prerequisites
   The following must be completed before a system is implemented and approved as operational:
   • The systems documentation conforming to standards outlined in chapter two of this manual.
   • A systems walkthrough
     
     • Purpose
       The purpose of a systems walkthrough is to prove the logic of the system. A walkthrough team will be established for each project.
     • Input Requirements
       Input requirements include:
       (a) Raw data or machine usable input.
       (b) Batch or on line input.
       (c) Control totals or record counts
       (d) Database elements chosen or generated to provided realistic test data.
     • Anticipated Processing
       This includes the process steps required to provide output of data or update of the database or files.
     • Anticipated Outputs
       These are normally classified into categories and are checked to ensure all data elements are available in the forms required.
       (a) Total record counts, units, dollars, or other data are checked against expected values.
       (b) The contents and format of screens are checked against standards and expected values.
       (c) Errors are identified for those items expected to be rejected by the system.
       (d) Output data elements that will become input to other processes are checked for compatibility.
2. Implementation Procedures
   The implementation phase includes the following:
   • Develop implementation plans, estimates, and conversion procedures.
   • Review and update systems specifications developed during programming.
   • Develop test data for program and systems testing.
   • Evaluate results from program tests, systems tests, volume tests, and any parallel testing.
   • Update changes to the schedule.
   • Develop training procedures.