Every program must continuously evolve, or it will become obsolete. This paper explores a methodology for software evolution within the setting of object-orientated programming. The methodology is based on the top–down propagation of change, and it is remotely related to stepwise refinement. To present the methodology, this paper uses one small example (Gregorian calendar) and one medium-sized example (calendar maintainer). This paper also explores an algorithm for scheduling object classes for update, and introduces a tool, ‘Ripples’, which helps programmers work with the process of software evolution.
No takes yet. Share an insight, caveat, or question.
Václav Rajlich (1997) studied this question.
Synapse has enriched 3 closely related papers on similar clinical questions. Consider them for comparative context: