• DocumentCode
    1119669
  • Title

    Rescuing Code

  • Author

    Rainsberger, I.B.

  • Volume
    24
  • Issue
    5
  • fYear
    2007
  • Firstpage
    26
  • Lastpage
    27
  • Abstract
    Imagine you\´ve experienced project heat death at least once. The term "heat death" comes from the second law of thermodynamics: entropy within a closed system increases over time without bound until the system collapses. In software, the entropy we experience most is in the design. Most of the code we add increases design entropy. Project heat death occurs when the design rots to the point where starting over is cheaper than continuing. Project heat death seems inevitable, yet when a large-scale project dies, people often stand around, surprised, asking "why us?" To do better next time, you need a sense of what problems to look for, and you need to start solving them before they spiral out of control. The author hopes this department helps in both regards.
  • Keywords
    software architecture; software development management; design entropy; large-scale project; project heat death; software design; system design; Accidents; Books; Entropy; Logic programming; cost of change; design; entropy; heat death; improvement; improving design; maintenance; refactoring; rescuing code; trade-off;
  • fLanguage
    English
  • Journal_Title
    Software, IEEE
  • Publisher
    ieee
  • ISSN
    0740-7459
  • Type

    jour

  • DOI
    10.1109/MS.2007.143
  • Filename
    4302682