Software design support using case-based reasoning

This paper proposes a software design support method using case-based reasoning. The need for raising productivity in software development has long been felt, and a variety of design methods have been proposed in response to this need. These, however, deal mostly with rough procedures, and there is a need for detailed procedures that designers can follow when performing actual design work. One technique for obtaining a detailed procedure would be to refer to actual design cases from the past. The problem here, though, is that such information has not normally been collected and stored because of the additional burden placed on software designers. The authors have thus investigated a way to record design information during design work without placing a burden on the designer, and have developed a system to support design work by effectively reusing past design cases. In this system, past design cases are recorded, and through the use of case-based reasoning techniques, the design procedure and design results are presented to the designer as reusable candidates.<<ETX>>

[1]  Colin Potts,et al.  Recording the reasons for design decisions , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[2]  Michael L. Begeman,et al.  gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.

[3]  Leon J. Osterweil,et al.  Software processes are software too , 1987, ISPW.

[4]  Masaki Hamada,et al.  Recording software design processes for maintaining the software , 1993, Proceedings of 1993 IEEE 17th International Computer Software and Applications Conference COMPSAC '93.

[5]  Jintae Lee,et al.  Extending the Potts and Bruns model for recording design rationale , 1991, [1991 Proceedings] 13th International Conference on Software Engineering.