A  Planning for top level steps, plus schedule and manpower allocation

1. Implementation Techniques to be considered

2. Conversion Priorities

3. Standards Requirements

4. Resources and Timing

B. Develop an Inventory of all programs, classified or grouped by

1. Program set

2. Status vis-à-vis Y2K, e.g.:

a. in use

b. will be replaced/upgraded before Y2K

c. obsolete now or before Y2K

3. Frequency of use

4. Determine projected (type of) failure dates

5. Classify by:

a. Leave alone (not date-sensitive)

b. Re-host (move to new platform)

c. Replace (with vendor supplied system that is Y2K compliant)

d. Retire (not in use in Y2K or cost too high to fix)

e. Assign Degree of Urgency (e.g., Mission Critical)

C. Inspection

1. Scan for date fields

2. Classify by type of failure date fields

D. Assessment/Estimate/Planning (for each major subsystem - see below)

1. In $, and

2. Man-months (actually more important than $)

E. Correction

1. Develop detail plan for each subsystem and execution/implementation of the plan, plus

2. Contingency plan

3. Cost-benefit (impact) analysis in terms of tangible and intangible factors

F. Test, Verification & Validation

1. Unit - Testing data fixes on individual programs

2. Integration - Every time a program is put together with other programs

2a. This step requires Regression Testing whenevr an error is discovered and corrected.

3. System - When putting toether all sub-systems (components)

4. Regression - same as above this step may be needed after system testing

5. Coupling within AMMOS/TMOD systems - includes volume and simulation testing

G. Re-deployment (release for operation) approach

1. Abrupt

2. Pilot

3. Phased

4. Parallel