TY - CONF A1 - Schubanz, Mathias A1 - Pleuss, Andreas A1 - Jordan, Howell A1 - Botterweck, Goetz T1 - Guidance for Design Rationale Capture to Support Software Evolution T2 - 6. Workshop "Design for Future'', 28. - 30. April 2014 in Bad Honnef N2 - Documenting design rationale (DR) helps to preserve knowledge over long time to diminish software erosion and to ease maintenance and refactoring. However, use of DR in practice is still limited. One reason for this is the lack of concrete guidance for capturing DR. This paper provides a first step towards identifying DR questions that can guide DR capturing and discusses required future research. KW - design rationale KW - software erosion KW - decision making KW - question catalogue KW - literature review Y1 - 2017 UR - https://opus4.kobv.de/opus4-UBICO/frontdoor/index/index/docId/19124 UR - http://fg-sre.gi.de/fileadmin/gliederungen/fg-sre/wsre2014/wsre_dff_2014_proceedings.pdf UR - http://pi.informatik.uni-siegen.de/stt/34_2/index.html N1 - ISSN 0720-8928 SP - 60 EP - 61 PB - Gesellschaft für Informatik CY - Bonn ER -