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¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 3 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:afb6628f6030 · see in the full table