|
Replacing the Entire System
Easier said than done. When considering the
replacement of an entire system, significant concern must
be placed on the certainty that a potential new system will
absolutely work. After all, the legacy system has reliably
functioned, usually for decades.
Requirements to replace the entire system
The usual answer is, "maybe". Building
a new system will require conceptual design, engineering,
prototyping, testing, manufacturing, additional testing, debugging,
and eventually certification of a final product. Until the
new system is actually operating and in place, no one knows
if it will work as reliably as the legacy system always has.
This route is the most expensive path for solving the problem
of obsolete components. The time required to build a replacement
may exceed the life expectancy of the overall system or program,
which may completely fail while being replaced due to software
compatibility. System failure is not an acceptable scenario.
The only advantage for a complete system
replacement is the potential for new feature sets provided
by new technology. A complete upgrade might be needed at some
point in time. However, the cost and time to implement a complete
replacement system must be well timed, sufficiently funded,
and properly overlap the legacy system.
Next: Can a subsystem
in the system be replaced or upgraded?
|
