Abstract :
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.