If you put effort into investigating your code, you will want to
document your work. We started by creating a database that listed all
the modules in the operating system. As engineers completed their
investigations, they filed formal reports for all code, using the ratings we established to identify the status of
all modules and date-related interfaces.
As this information was entered into the database, we could
periodically poll the database to track our status in terms of
investigation completion and Year 2000 readiness.
If engineers found Year 2000 limitations in the code they investigated,
these were detailed in a separate database along with the proposed
solution (either a code change or enhanced documentation). As you can
see from the results of our
investigations, the problem reports were minimal.
» Return to Guidelines for Year 2000 Code Investigations home page