A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
Evaluating Software Engineering Technologies
IEEE Transactions on Software Engineering
Software evolution: the software maintenance challenge
Software evolution: the software maintenance challenge
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
ICSE '94 Proceedings of the 16th international conference on Software engineering
Proceedings of the 32nd conference on Winter simulation
Practical Software Maintenance: Best Practices for Managing Your Software Investment
Practical Software Maintenance: Best Practices for Managing Your Software Investment
Software Engineering Economics
Software Engineering Economics
Spice: The Theory and Practice of Software Process Improvement and Capability Determination
Spice: The Theory and Practice of Software Process Improvement and Capability Determination
Ageing of a data-intensive legacy system: symptoms and remedies
Journal of Software Maintenance: Research and Practice
Software Maintenance: The Problems and Its Solutions
Software Maintenance: The Problems and Its Solutions
Software Maintenance Management
Software Maintenance Management
Building a Case-Based Help Desk Application
IEEE Expert: Intelligent Systems and Their Applications
The Real World Software Process
APSEC '02 Proceedings of the Ninth Asia-Pacific Software Engineering Conference
An Overview of Industrial Software Documentation Practice
SCCC '02 Proceedings of the XII International Conference of the Chilean Computer Science Society
Requirements Documentation: Why a Formal Basis is Essential
ICRE '00 Proceedings of the 4th International Conference on Requirements Engineering (ICRE'00)
A Survey on the Software Maintenance Process
ICSM '98 Proceedings of the International Conference on Software Maintenance
Information Retrieval Models for Recovering Traceability Links between Code and Documentation
ICSM '00 Proceedings of the International Conference on Software Maintenance (ICSM'00)
Software Documentation: How Much Is Enough?
CSMR '03 Proceedings of the Seventh European Conference on Software Maintenance and Reengineering
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Towards automatically generating summary comments for Java methods
Proceedings of the IEEE/ACM international conference on Automated software engineering
Measuring API documentation on the web
Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering
Automatically detecting and describing high level actions within methods
Proceedings of the 33rd International Conference on Software Engineering
Effective communication of software development knowledge through community portals
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Evaluating usage and quality of technical software documentation: an empirical study
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
Hi-index | 0.00 |
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 ageing. 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 organisations studied. None of our organisations has fully implemented all our documentation requirements.