Cost, benefits and quality of software development documentation: A systematic mapping
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
The incompleteness of design documentation is discussed in the literature.
“The incompleteness of design documentation is also discussed in the literature (e.g., [113]).”
From Software Architecture in Practice: Challenges and Opportunities (2023) · cites this paper as [113]
Cites
Systematic Mapping Studies in Software Engineering
Petersen, K., Feldt, R., Mujtaba, S., & Mattsson, M. (2008) · Electronic Workshops in Computing · doi:10.14236/ewic/ease2008.8 · Cited by 3,239 · see citing works
Flagged first, then by citations
Cited by
Sorted by citations
Garousi, V., Felderer, M., & Mäntylä, M. V. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.09.006 · Cited by 831 · see citing works
Ampatzoglou, A., Bibi, S., Avgeriou, P., Verbeek, M., & Chatzigeorgiou, A. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.10.006 · Cited by 305 · see citing works
Hutchinson, B., Smart, A., Hanna, A., Denton, R., Greer, C., Kjartansson, O., Barnes, P., & Mitchell, M. (2021) · Proceedings of the 2021 ACM Conference on Fairness, Accountability, and Transparency · doi:10.1145/3442188.3445918 · Cited by 279 · see citing works
Aligning software engineering education with industrial needs: A meta-analysis
Garousi, V., Giray, G., Tüzün, E., Catal, C., & Felderer, M. (2019) · Journal of Systems and Software · doi:10.1016/j.jss.2019.06.044 · Cited by 119 · see citing works
AI Documentation: A path to accountability
Königstorfer, F., & Thalmann, S. (2022) · Journal of Responsible Technology · doi:10.1016/j.jrt.2022.100043 · Cited by 55 · see citing works
Tan, M., & Subramonyam, H. (2024) · Proceedings of the CHI Conference on Human Factors in Computing Systems · doi:10.1145/3613904.3642592 · Cited by 40 · see citing works
Studying the difference between natural and programming language corpora
Casalnuovo, C., Sagae, K., & Devanbu, P. (2019) · Empirical Software Engineering · doi:10.1007/s10664-018-9669-7 · Cited by 33 · see citing works
Software Architecture in Practice: Challenges and Opportunities
Wan, Z., Zhang, Y., Xia, X., Jiang, Y., & Lo, D. (2023) · Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3611643.3616367 · Cited by 30 · see citing works
“The incompleteness of design documentation is also discussed in the literature (e.g., [109]).”
Background
- Authors
- Zhi, J., Garousi-Yusifoğlu, V., Sun, B., Garousi, G., Shahnewaz, S., & Ruhe, G.
- Affiliations
- University of Toronto (CA)
- University of Calgary (CA)
- Venue
- Journal of Systems and Software
- Publisher
- Elsevier BV
- Published
- 2015-01
- Volume
- 99
- Pages
- 175-198
- ISSN
- 0164-1212 (ISSN-L)
- OpenAlex
- W2513125375
- Cited by
- 112
- References
- 1
- Citations by year
- 2026: 5 · 2025: 6 · 2024: 10 · 2023: 6 · 2022: 16 · 2021: 14 · 2020: 14 · 2019: 8 · 2018: 10 · 2017: 8 · 2016: 13 · 2015: 1 · 2014: 1
- FWCI
- 21.24
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- Journal of Systems and Software (publishedVersion)
- Funders
- NSERC CRD (CRDPJ414157-11)
- NSERC ENGAGE (EGP-413039)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Artificial Intelligence › Advanced Software Engineering Methodologies
- Keywords
- software documentation, documentation quality, documentation completeness, documentation consistency, software development process, agile software development, research gaps, software reuse, software testing, software metrics, software design, software requirements, software configuration management
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
