SciELO - Scientific Electronic Library Online

 
vol.12 issue3The marginal value of increased testing: an empirical analysis using four code coverage measuresExperiences tracking agile projects: an empirical study author indexsubject indexarticles search
Home Pagealphabetic serial listing  

Journal of the Brazilian Computer Society

Print version ISSN 0104-6500

Abstract

SOUZA, Sergio Cozzetti B. de; ANQUETIL, Nicolas  and  OLIVEIRA, Káthia M. de. Which documentation for software maintenance?. J. Braz. Comp. Soc. [online]. 2006, vol.12, n.3, pp. 31-44. ISSN 0104-6500.  http://dx.doi.org/10.1007/BF03194494.

Software engineering has been striving for years to improve the practice of software development and maintenance. Documentation has long been prominent on the list of recommended practices to improve development and help maintenance. Recently however, agile methods started to shake this view, arguing that the goal of the game is to produce software and that documentation is only useful as long as it helps to reach this goal. On the other hand, in the re-engineering field, people wish they could re-document useful legacy software so that they may continue maintain them or migrate them to new platform. In these two case, a crucial question arises: How much documentation is enough? In this article, we present the results of a survey of software maintainers to try to establish what documentation artifacts are the most important to them.

        · text in English     · pdf in English