Software documentation quality: A case study for the software documentation of SIGEPE

Requirements determine the correct construction of software and are frequently represented explicitly in the accompanying documentation in ways that vary according to the adopted software process. The documentation is typically written in natural language and can contain elements such as figures, tables or a more formal description. The quality assurance of artifacts written in natural language has advanced significantly since the mid-70s. SIGEPE makes use of checklists with criteria weighted by both form and content. The quality assurance team conducts periodic and individual checks on strategically selected projects. In little over a year, there was a noticeable improvement in the quality of the documentation and it was possible to identify the most common points of success and failure. This paper describes a Case Study to verify the quality of the elements of SIGEPE documentation.

[1]  Claes Wohlin,et al.  An Experimental Comparison of Usage-Based and Checklist-Based Reading , 2003, IEEE Trans. Software Eng..

[2]  John C. Knight,et al.  An improved inspection technique , 1993, CACM.

[3]  Maristela Holanda,et al.  Business process modelling: A study case within the Brazilian Ministry of Planning, Budgeting and Management , 2014, 2014 9th Iberian Conference on Information Systems and Technologies (CISTI).

[4]  James Miller,et al.  Further Experiences with Scenarios and Checklists , 1998, Empirical Software Engineering.

[5]  Marcelo Schneck de Paula Pessôa,et al.  Qualidade de software , 1995 .

[6]  Reinhold Plösch,et al.  The Value of Software Documentation Quality , 2014, 2014 14th International Conference on Quality Software.

[7]  Per Runeson,et al.  A replicated experiment of usage-based and checklist-based reading , 2004, 10th International Symposium on Software Metrics, 2004. Proceedings..

[8]  Peng Liang,et al.  Knowledge-based approaches in software documentation: A systematic literature review , 2014, Inf. Softw. Technol..

[9]  Michael E. Fagan Design and Code Inspections to Reduce Errors in Program Development , 1976, IBM Syst. J..

[10]  Remco C. de Boer,et al.  Writing and Reading Software Documentation: How the development process may affect understanding , 2009, 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering.

[11]  Dirk Muthig,et al.  A view-based approach for improving software documentation practices , 2006, 13th Annual IEEE International Symposium and Workshop on Engineering of Computer-Based Systems (ECBS'06).

[12]  Wei-Tek Tsai,et al.  N-Fold inspection: a requirements analysis technique , 1990, Commun. ACM.

[13]  Shinji Kusumoto,et al.  An experimental comparison of checklist-based reading and perspective-based reading for UML design document inspection , 2002, Proceedings International Symposium on Empirical Software Engineering.

[14]  B BisantDavid,et al.  A Two-Person Inspection Method to Improve Programming Productivity , 1989 .

[15]  James R. Lyle,et al.  A Two-Person Inspection Method to Improve Prog ramming Productivity , 1989, IEEE Transactions on Software Engineering.