Cited by 31Software Engineering ResearchSoftware Engineering Techniques and PracticesOpen Source Software Innovations

Evaluating the Effects of Architectural Documentation: A Case Study of a Large Scale Open Source Project

Kazman, Rick, Goldenson, Dennis, Monarch, Ira, Nichols, William, Valetto, Giuseppe·2016·IEEE Transactions on Software Engineering

Abstract

Sustaining large open source development efforts requires recruiting new participants; however, a lack of architectural documentation might inhibit new participants since large amounts of project knowledge are unavailable to newcomers. We present the results of a multitrait, multimethod analysis of the effects of introducing architectural documentation into a substantial open source project-the Hadoop Distributed File System (HDFS). HDFS had only minimal architectural documentation, and we wanted to discover whether the putative benefits of architectural documentation could be observed over time. To do this, we created and publicized an architecture document and then monitored its usage and effects on the project. The results were somewhat ambiguous: by some measures the architecture documentation appeared to effect the project but not by others. Perhaps of equal importance is our discovery that the project maintained, in its Web-accessible JIRA archive of software issues and fixes, enough architectural discussion to support architectural thinking and reasoning. This “emergent” architecture documentation served an important purpose in recording core project members' architectural concerns and resolutions. However, this emergent architecture documentation did not serve all project members equally well; it appears that those on the periphery of the project-newcomers and adopters-still require explicit architecture documentation, as we will show.

Integrity signals

Registry

Crossref · 10.1109/tse.2015.2465387

Cites

78 of 78 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Kazman, R., Goldenson, D., Monarch, I., Nichols, W., & Valetto, G.
Affiliations
  • Software Engineering Institute (US)
  • Fondazione Bruno Kessler (IT)
Venue
IEEE Transactions on Software Engineering
Published
2016-03-01
Volume
42
Issue
3
Pages
220-260
ISSN
  • 0098-5589 (ISSN-L)
  • 1939-3520
OpenAlex
W2296438858
Cited by
31
References
78
Citations by year
2025: 3 · 2024: 3 · 2023: 4 · 2022: 3 · 2021: 5 · 2020: 2 · 2019: 3 · 2018: 2 · 2017: 4 · 2016: 2
FWCI
7.19
Type
journal article
Language
en
Open access
closed
Locations
IEEE Transactions on Software Engineering (publishedVersion)
Funders
  • Department of Defense (FA8721-05-C-0003)
  • Carnegie Mellon University
  • Software Engineering Institute
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
Keywords
architectural documentation, open source software, HDFS, newcomer onboarding, software architecture, large-scale software projects, software maintainability

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