This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
March/April 2009 (vol. 26 no. 2)
pp. 25-27
Uwe Zdun, Vienna University of Technology
Capturing software design knowledge is important because it tends to evaporate as software systems evolve. This has severe consequences for many software projects. To counteract this phenomenon, effective, systematic documentation of design knowledge is important. However, many proposed approaches for capturing design knowledge are still experimental or in an early-adoption stage. In this article, we discuss existing and new approaches to deal with parts of the knowledge evaporation problem.

[1a] M.M. Lehman and L.A. Belady, Program Evolution—Processes of Software Change, Academic Press, 1985.
[1b] O. Zimmermann et al., "Combining Pattern Languages and Architectural Decision Models in a Comprehensive and Comprehensible Design Method," Proc. 7th Working IEEE/IFIP Conf. Software Architecture (WICSA 08), IEEE CS Press, 2008, pp. 156–166.
[2b] N. Harrison, P. Avgeriou, and U. Zdun, "Using Patterns to Capture Architectural Decisions," IEEE Software, vol. 24, no. 4, 2007, pp. 38–45.
[3b] P. Lago and P. Avgeriou, "First Workshop on Sharing and Reusing Architectural Knowledge," SIGSOFT Software Eng. Notes, vol. 31, no. 5, 2006, pp. 32–36.
[4b] P. Avgeriou, P. Lago, and P. Kruchten, "Sharing and Reusing Architectural Knowledge (Shark 2008)," companion to Proc. 30th Int'l Conf. Software Eng. (ICSE 08), IEEE CS Press, 2008.

Index Terms:
design knowledge, design knowledge evaporation, architectural knowledge
Citation:
Uwe Zdun, "Guest Editor's Introduction: Capturing Design Knowledge," IEEE Software, vol. 26, no. 2, pp. 25-27, March-April 2009, doi:10.1109/MS.2009.37
Usage of this product signifies your acceptance of the Terms of Use.