Recording software design processes for maintaining the software

This paper proposes a method of supporting software change propagation analysis using a recorded software design rationale. This paper discusses recording costs, the usage and effectiveness of the recorded information for change propagation analysis, which other papers don't. Change propagation analysis of the software being modified is difficult when no design rationale for the software is left. In the proposed method, the designer makes a design process record that includes his/her design rationale. The method enables a maintainer to search for the recorded information that is essential to change propagation analysis. The cost of recording the design process is small because the designer just writes down fragmentary design results. From the experience of using a prototype system, the effectiveness of the proposed method is discussed.<
>