............................................................................................................................ iii Acknowledgements .......................................................................................................... iv Table of

Though programming languages and programming styles evolve with remarkable speed today, there is no such evolution in the field of program documentation. And although there exist some popular approaches like Knuth’s literate programming system WEB [26], and nowadays JavaDoc [15] or Doxygen [16], tools for managing software development and documentation are not as widespread as desirable. This p...

Conventional software documentation systems are mostly based on textutal descriptions that explain or annotate the program's source code. Typically they also support interactive browsing of high-level control ows, and name-based searching of program primitives such as variable declarations and function deenitions. Because these systems rely solely on texts, it is diicult for program authors to ...

" Motivation Limited Domain relations (LD-relations) " What happens for out of domain arguments? Difficulty parsing complex mathematical specifications " What does that do, again? " Objective Clear, formal representation of requirements specifications in a tabular format " Mathematic foundation " Possible for both human and machine parsing " Better partitioned specifications " Techniques Used M...

Automated source code documentation approaches often describe methods in abstract terms, using the words contained in the static source code or code excerpts from repositories. In this paper, we describe DynamiDoc: a simple automated documentation generator based on dynamic analysis. Our representation-based approach traces the program being executed and records string representations of concre...

Software design patterns are a promising idea with many advocates. While subjective reports of their usefulness are available, scienti c proof is still missing. We consider the case of programmers using design pattern documentation (in the form of comments in the source program) during maintenance. Is such pattern documentation (PD) helpful for understanding a program more quickly and designing...