Communications of the ACM
Report from an Experiment: Impact of Documentation onMaintenance
Empirical Software Engineering
Software Documentation: How Much Is Enough?
CSMR '03 Proceedings of the Seventh European Conference on Software Maintenance and Reengineering
A Survey of Documentation Practice within Corrective Maintenance
Empirical Software Engineering
Predicting acceptance of Software Process Improvement
HSSE '05 Proceedings of the 2005 workshop on Human and social factors of software engineering
A study of the documentation essential to software maintenance
Proceedings of the 23rd annual international conference on Design of communication: documenting & designing for pervasive information
Determining Inspection Cost-Effectiveness by Combining Project Data and Expert Opinion
IEEE Transactions on Software Engineering
The Impact of UML Documentation on Software Maintenance: An Experimental Evaluation
IEEE Transactions on Software Engineering
Guide to Advanced Empirical Software Engineering
Guide to Advanced Empirical Software Engineering
A Realistic Empirical Evaluation of the Costs and Benefits of UML in Software Maintenance
IEEE Transactions on Software Engineering
Guidelines for conducting and reporting case study research in software engineering
Empirical Software Engineering
Evidence-Based Insights about Issue Management Processes: An Exploratory Study
ICSP '09 Proceedings of the International Conference on Software Process: Trustworthy Software Development Processes
Action research use in software engineering: An initial survey
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Journal of Systems and Software
A Metrics-Based Approach to Technical Documentation Quality
QUATIC '10 Proceedings of the 2010 Seventh International Conference on the Quality of Information and Communications Technology
Hi-index | 0.00 |
Context: Software documentation is an integral part of any software development process. However, software practitioners are often concerned about the lack of usage and quality of documentation in practice. Unfortunately, in many projects, practitioners find that software documentation artifacts are outdated, incomplete and sometimes not beneficial. Objective: Motivated by the needs of NovAtel Inc. (NovAtel), a world-leading company of GPS software systems, we propose in this paper an approach to analyze the usage and quality of software documentation in development and maintenance phases. Method: The approach incorporates inputs from automated analysis (e.g., mining of project's data) and also experts' opinion extracted from survey-based questionnaire. The approach has been designed based on the "action-research" approach and in close collaboration between industry and academia. Results: To evaluate the feasibility and usefulness of the proposed approach, we have applied it in an industrial setting and results are presented in this paper. One of the results is that, in the context of our case-study, usage of documentation for an implementation purpose is higher than the usage for maintenance purposes. Conclusion: It is concluded that the usage of documentation differs for various purposes and it depends on the type of the information needs as well as the task to be completed (e.g. development and maintenance). In addition, we identify the most important and relevant quality attributes which are critical to improving documentation quality.