Stovepipe system
From Wikipedia, the free encyclopedia
In engineering and computing, a stovepipe system is a legacy system that is an assemblage of inter-related elements that are so tightly bound together that the individual elements cannot be differentiated, upgraded or refactored. The stovepipe system must be maintained until it can be entirely replaced by a new system.
Examples of stovepipe systems:
- Systems for which new hardware is no longer available.
- Systems whose original source code has been lost.
- Systems that were built using old or ad hoc engineering methodologies for which support can no longer be found.
The term is also used to describe a system that does not interoperate with other systems, presuming instead that it is the only extant system.
A stovepipe system is an example of an anti-pattern legacy system and demonstrates software brittleness.
[edit] References
Stovepipes are “systems procured and developed to solve a specific problem, characterized by a limited focus and functionality, and containing data that cannot be easily shared with other systems.” (DOE 1999)
DOE. Committee to Assess the Policies and Practices of the Department of Energy, Improving Project Management in the Department of Energy, National Academy Press, Washington, D.C., 1999, page 133.
