Using Design Rationales for Agile Documentation

Recently, Agile Software Processes have been dis-cussed as flexible and light-weight alternatives to estab-lished Software Engineering approaches, in order to overcome the obstacles created by the cost of producing and maintaining documents on higher abstraction levels. Depending on requirements and needs on the documents itself, Agile Documentation becomes a key issue and brings up questions on how to create, maintain and dis-tribute documents among the team members without cre-ating unnecessary or unjustifiable cost. This paper de-scribes a technique allowing to produce documentation automatically, by conducting analysis on the series of development steps taken during project planning and enactment. 1