Software aging¶
Parnas, D. L. (1994). Software aging. Proceedings of the 16th International Conference on Software Engineering (ICSE '94), 279-287.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Legacy Integration
- Legacy integration enables diagnostic and design reasoning about organizational transitions, addressing the trade-offs Parnas (1994) makes explicit in his analysis of software aging and the costs of deferred preservation.
This sourceCoined the term "software aging" and identified its causes (kept-going-too-long ignorance, incremental change without redesign); foundational for technical-debt, refactoring, and rejuvenation literature.
- Legacy integration enables diagnostic and design reasoning about organizational transitions, addressing the trade-offs Parnas (1994) makes explicit in his analysis of software aging and the costs of deferred preservation.
- Maintenance
- The central tension: maintenance consumes resources today to prevent catastrophic costs tomorrow, yet its success is measured by what does not happen—a paradox that leads to chronic underinvestment, deferred maintenance that compounds, and institutional amnesia about how to maintain what was built, a phenomenon Parnas (1994) identifies in his analysis of how undocumented decisions and skill loss accelerate decay even in well-funded systems.
This sourceCoined the term "software aging" and identified its causes (kept-going-too-long ignorance, incremental change without redesign); foundational for technical-debt, refactoring, and rejuvenation literature.
- The central tension: maintenance consumes resources today to prevent catastrophic costs tomorrow, yet its success is measured by what does not happen—a paradox that leads to chronic underinvestment, deferred maintenance that compounds, and institutional amnesia about how to maintain what was built, a phenomenon Parnas (1994) identifies in his analysis of how undocumented decisions and skill loss accelerate decay even in well-funded systems.
- Temporal Decay and Degradation
- The alternative—ignoring degradation—is sudden, catastrophic failure or a forced, expensive emergency rewrite.
This sourceCoined the term "software aging" and identified its causes (kept-going-too-long ignorance, incremental change without redesign); foundational for technical-debt, refactoring, and rejuvenation literature.
- The alternative—ignoring degradation—is sudden, catastrophic failure or a forced, expensive emergency rewrite.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:afb6628f6030 · see in the full table