A survey of documentation practice within corrective maintenance
2005 (English)In: Journal of Empirical Software Engineering, ISSN 1382-3256, E-ISSN 1573-7616, Vol. 10, no 1, 31-55 p.Article in journal (Refereed) Published
The purpose of documentation is to describe software systems and software processes. Consistent, correct and complete documentation of a software system is an important vehicle for the maintainer to gain its understanding, to ease its learning and/or relearning processes, and to make the system more maintainable. Poor system documentation, on the other hand, is the primary reason for quick software system quality degradation and aging. Proper process documentation records the process, its stages and tasks, executing roles, their decisions and motivations, and the results of each individual process task. It is extremely important for achieving insight and visibility into the processes, important for their meaningful process measurement and thereby pivotal for achieving high process maturity. In this paper, we report on the results of an explorative study in which we have identified a number of rudimentary documentation requirements relevant within corrective maintenance, and found out how they were implemented within eighteen software organizations in Sweden. The goal was to examine the industrial documentation practice within corrective maintenance. Our results show that the documentation within corrective maintenance is still a very neglected issue within the organizations studied. None of our organizations has fully implemented all our documentation requirements.
Place, publisher, year, edition, pages
2005. Vol. 10, no 1, 31-55 p.
corrective maintenance, software system documentation, software process documentation
IdentifiersURN: urn:nbn:se:kth:diva-14515ISI: 000226855600002OAI: oai:DiVA.org:kth-14515DiVA: diva2:332556
QC 201005252010-08-052010-08-05Bibliographically approved