Year 2000 Renovation
Organization Year 2000 Program Phase or Activity Questions:
Awareness Assessment
Renovation Validation
Implementation Program
Management
Organizations Year 2000 Program Phase or Activity -- Processes:
3.0 Renovation
The renovation--conversion, replacement, or retirement--phase involves
making and documenting
software and hardware changes, developing replacement systems, and
decommissioning eliminated
systems. Renovation involves conversion of an existing application;
replacement deals with the
development of a new application; elimination focuses on the retirement
or decommissioning of an
existing application or system component. In all three cases, the process
must also consider the
complex interdependencies among applications, hardware platforms, databases,
and the internal
and external interfaces.
All changes to the information systems and their components must be
made under configuration
management to ensure that changes are adequately documented and coordinated
throughout the
organization. Equally important is the need for each organization to
assess dependencies and to communicate
all changes to the information systems to internal and external users.
Key Processes
3.1. Convert selected applications, databases, archives, and related
system components
3.2. Develop data bridges and filters
3.3. Replace selected applications and related system components
3.4. Document code and system changes
3.5. Schedule unit, integration, and system tests
3.6. Retire selected applications and related system components
3.7. Communicate changes to information systems to internal and
external users
3.8. Track conversion and replacement process, collect project metrics
3.9. Share information among Year 2000 projects, including lessons
learned and best
practices
3.1. Convert selected applications, databases, archives, and related system
components
In converting application systems, consider changes in operating systems,
compilers,
utilities, domain-specific program products, and commercial database
management
systems.
3.2. Develop data bridges and filters
Ensure that all internal and external data sources meet the Year 2000 date
standards of the
converted or replaced systems. Develop bridges or filters to convert
non-conforming data.
3.3. Replace selected applications, platforms, database management systems,
operating systems, compilers, utilities, and other commercial off-the-shelf
(COTS) software
Ensure that replacement products are Year 2000 compliant, including their
ability to
properly handle the leap year adjustments. Direct contract specialist
and legal staff to
review contracts and warranties.
3.4. Document code and system changes
Implement and use configuration management procedures to ensure that all
changes to
information systems and their components are properly documented and
managed.
3.5. Schedule unit, integration, and system tests
Schedule unit, integration, and system tests following the conversion of
individual
application and software modules. Coordinate scheduling with other
project teams to
ensure that all components--including data bridges or filters--are
available for testing.
3.6. Retire selected applications, platforms, database management systems,
operating systems, utilities, and COTS software
Prepare to retire replaced applications, platforms, database management
systems,
operating systems, utilities, and COTS software upon the successful
completion of
acceptance testing.
3.7. Communicate changes to information systems to all internal and external
users
Communicate changes to the organization’s information systems and components,
and
specifically all changes to date formats for data exchanged with other
systems or external
organizations. Document changes through the configuration management
process.
3.8. Track the conversion and replacement process and collect project metrics
Track the conversion and replacement projects and collect and use project
metrics to
manage cost and schedule.
3.9. Share information among Year 2000 projects and disseminate lessons
learned and best practices
Ensure that project staffs understand the need to collect and disseminate
information on
lessons learned and best practices. Develop dissemination strategy
and tools, such as
intranet web sites and newsletters.
The Disaster Center Year 2000
Page| |The Disaster Center Index Page
Formatted and altered from text provided by: The
United States General Accounting Office Accounting and Information Management
Division HTML format Copyrighted by The Disaster Center 1998