A Hybrid Methodology for Analyzing Software Documentation Quality and Usage
暂无分享,去创建一个
[1] Jacob Katzenelson. Documentation and the management of a software project—a case study , 1971, Softw. Pract. Exp..
[2] Nicolas Anquetil,et al. Which documentation for software maintenance? , 2010, Journal of the Brazilian Computer Society.
[3] Shihong Huang,et al. A qualitative assessment of the efficacy of UML diagrams as a form of graphical documentation in aiding program understanding , 2003, SIGDOC '03.
[4] Morgan Ericsson,et al. A Metrics-Based Approach to Technical Documentation Quality , 2010, 2010 Seventh International Conference on the Quality of Information and Communications Technology.
[5] Wayne G. Lutters,et al. Revealing actual documentation usage in software maintenance through war stories , 2007, Inf. Softw. Technol..
[6] 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.
[7] 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).
[8] David Lorge Parnas,et al. Precise Documentation of Critical Software , 2007 .
[9] James D. Arthur,et al. Assessing the adequacy of documentation through document quality indicators , 1989, Proceedings. Conference on Software Maintenance - 1989.
[10] Barry W. Boehm,et al. Value-Based Software Engineering: A Case Study , 2003, Computer.
[11] Per Runeson,et al. Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.
[12] Ademar Aguiar,et al. Patterns for consistent software documentation , 2009, PLoP '09.
[13] Janice Singer,et al. How software engineers use documentation: the state of the practice , 2003, IEEE Software.
[14] Jürgen Münch,et al. GQM^+ Strategies -- Aligning Business Strategies with Software Measurement , 2007, ESEM 2007.
[15] Tore Dybå,et al. The Future of Empirical Methods in Software Engineering Research , 2007, Future of Software Engineering (FOSE '07).
[16] Shari Lawrence Pfleeger,et al. Principles of survey research part 6: data analysis , 2003, SOEN.
[17] Lionel C. Briand,et al. A Realistic Empirical Evaluation of the Costs and Benefits of UML in Software Maintenance , 2008, IEEE Transactions on Software Engineering.
[18] Howard A. Kanter,et al. Measuring the Readability of Software Requirement Specifications: An Empirical Study , 2008 .
[19] V. Basili. Software modeling and measurement: the Goal/Question/Metric paradigm , 1992 .
[20] Scott R. Tilley,et al. Documenting software systems with views V: towards visual documentation of design patterns as an aid to program understanding , 2007, SIGDOC '07.
[21] Nicolas Anquetil,et al. A study of the documentation essential to software maintenance , 2005, SIGDOC '05.
[22] Janice Redish,et al. Readability formulas have even more limitations than Klare discusses , 2000, AJCD.
[23] Paul Clements,et al. Software Architecture Documentation in Practice: Documenting Architectural Layers , 2000 .
[24] Reinhold Plösch,et al. Automatic Checking of Quality Best Practices in Software Development Documents , 2011, 2011 11th International Conference on Quality Software.
[25] Denys Poshyvanyk,et al. Using Traceability Links to Assess and Maintain the Quality of Software Documentation , 2007 .
[26] Kai Petersen,et al. Systematic Mapping Studies in Software Engineering , 2008, EASE.
[27] F. Wilcoxon. Individual Comparisons by Ranking Methods , 1945 .
[28] Thomas Zimmermann,et al. How documentation evolves over time , 2007, IWPSE '07.
[29] Scott W. Ambler,et al. Agile modeling: effective practices for extreme programming and the unified process , 2002 .
[30] Frank A. Cioch,et al. A documentation suite for maintenance programmers , 1996, 1996 Proceedings of International Conference on Software Maintenance.
[31] Scott R. Tilley,et al. Documentation for software engineers: what is needed to aid system understanding? , 2001, SIGDOC '01.
[32] Hillel Rubin,et al. Supporting agile software development through active documentation , 2011, Requirements Engineering.
[33] Keith H. Bennett,et al. Maintaining maintainability , 1998, Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272).
[34] Bill Curtis,et al. Experimental evaluation of software documentation formats , 1989, J. Syst. Softw..
[35] Lionel C. Briand,et al. Software documentation: how much is enough? , 2003, Seventh European Conference onSoftware Maintenance and Reengineering, 2003. Proceedings..
[36] Jeffrey C. Carver,et al. An empirical methodology for introducing software processes , 2001, ESEC/FSE-9.
[37] Gerrit Muller,et al. Systems Architecting: a Business Perspective , 2011 .
[38] Siw Elisabeth Hove,et al. The impact of UML documentation on software maintenance: an experimental evaluation , 2006, IEEE Transactions on Software Engineering.
[39] Sang Lyul Min,et al. LRFU: A Spectrum of Policies that Subsumes the Least Recently Used and Least Frequently Used Policies , 2001, IEEE Trans. Computers.
[40] Christoph J. Stettina,et al. Necessary and neglected?: an empirical study of internal documentation in agile software development teams , 2011, SIGDOC '11.
[41] Ademar Aguiar,et al. WikiWiki weaving heterogeneous software artifacts , 2005, Int. Sym. Wikis.
[42] George R. Klare,et al. The measurement of readability: useful information for communicators , 2000, AJCD.
[43] John W. Bailey,et al. The Effects of the Symbology and Spatial Arrangement of Software Documentation in a Modification Task. , 1981 .
[44] T. T. Barker,et al. Software documentation: from instruction to integration , 1990 .
[45] Wayne G. Lutters,et al. Understanding documentation value in software maintenance , 2007, CHIMIT '07.
[46] Scott R. Tilley,et al. Documenting-in-the-large vs. documenting-in-the-small , 1993, CASCON.
[47] Eirik Tryggeseth,et al. Report from an Experiment: Impact of Documentation on Maintenance , 1997, Empirical Software Engineering.
[48] Mira Kajko-Mattsson,et al. A Survey of Documentation Practice within Corrective Maintenance , 2004, Empirical Software Engineering.
[49] Barry W. Boehm,et al. Value-based software engineering: reinventing , 2003, SOEN.
[50] William H. DuBay. The Principles of Readability. , 2004 .
[51] Thomas R. Gruber,et al. A translation approach to portable ontology specifications , 1993 .
[52] Evie McCrum-Gardner,et al. Which is the correct statistical test to use? , 2008, The British journal of oral & maxillofacial surgery.
[53] Shihong Huang,et al. Towards a documentation maturity model , 2003, SIGDOC '03.
[54] E. Burton Swanson,et al. Characteristics of application software maintenance , 1978, CACM.
[55] Curtis R. Cook,et al. Assessing the State of Software Documentation Practices , 2004, PROFES.
[56] Muhammad Ali Babar,et al. A Survey of the Use and Documentation of Architecture Design Rationale , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).
[57] Andrew Forward,et al. Software documentation: Building and maintaining artefacts of communication. , 2002 .
[58] Aamer Nadeem,et al. A state-based approach to integration testing based on UML models , 2007, Inf. Softw. Technol..
[59] Jarmo J. Ahonen,et al. Improving the Product Documentation Process of a Small Software Company , 2009, PROFES.
[60] David Lorge Parnas,et al. Precise Documentation: The Key to Better Software , 2010, The Future of Software Engineering.
[61] W. Kruskal,et al. Use of Ranks in One-Criterion Variance Analysis , 1952 .
[62] M. Coleman,et al. A computer readability formula designed for machine scoring. , 1975 .
[63] Michel R. V. Chaudron,et al. A cognitive perspective on developer comprehension of software design documentation , 2011, SIGDOC '11.
[64] Timothy Lethbridge,et al. The relevance of software documentation, tools and technologies: a survey , 2002, DocEng '02.
[65] S. Shapiro,et al. An Analysis of Variance Test for Normality (Complete Samples) , 1965 .
[66] Hausi A. Müller,et al. Documenting software systems with views , 1992, SIGDOC '92.