Schubanz, MathiasPleuss, AndreasJordan, HowellBotterweck, Goetz2023-03-162023-03-162014https://dl.gi.de/handle/20.500.12116/40870Documenting 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.enText/Journal Article0720-8928