The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
A survey of architecture design rationale
Open accessAbstract
Many claims have been made about the consequences of not documenting design rationale. The general perception is that designers and architects usually do not fully understand the critical role of systematic use and capture of design rationale. However, there is to date little empirical evidence available on what design rationale mean to practitioners, how valuable they consider it, and how they use and document it during the design process. This paper reports a survey of practitioners to probe their perception of the value of design rationale and how they use and document the background knowledge related to their design decisions. Based on 81 valid responses, this study has discovered that practitioners recognize the importance of documenting design rationale and frequently use them to reason about their design choices. However, they have indicated barriers to the use and documentation of design rationale. Based on the findings, we conclude that further research is needed to develop methodology and tool support for design rationale capture and usage. Furthermore, we put forward some specific research questions about design rationale that could be further investigated to benefit industry practice.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Toward reference models for requirements traceability
Ramesh, B., & Jarke, M. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.895989 · Cited by 912
Cited by
Building Up and Reasoning About Architectural Knowledge
Kruchten, P., Lago, P., & van Vliet, H. (2006) · Lecture Notes in Computer Science · doi:10.1007/11921998_8 · Cited by 290
10 years of software architecture knowledge management: Practice and future
Capilla, R., Jansen, A., Tang, A., Avgeriou, P., & Babar, M. A. (2016) · Journal of Systems and Software · doi:10.1016/j.jss.2015.08.054 · Cited by 160
Self-citationDasanayake, S., Aaramaa, S., Markkula, J., & Oivo, M. (2019) · Journal of Software: Evolution and Process · doi:10.1002/smr.2160 · Cited by 32
Automatic Identification of Decisions from the Hibernate Developer Mailing List
Li, X., Liang, P., & Li, Z. (2020) · Proceedings of the Evaluation and Assessment in Software Engineering · doi:10.1145/3383219.3383225 · Cited by 21
Metadata
- Authors
- Tang, A., Babar, M. A., Gorton, I., & Han, J.
- Venue
- Journal of Systems and Software
- Publisher
- Elsevier BV
- Published
- 2006-12
- Volume
- 79
- Issue
- 12
- Pages
- 1792-1804
- ISSN
- 0164-1212 (ISSN-L)
- OpenAlex
- W2087048098
- Cited by
- 206
- References
- 1
- FWCI
- 34.90
- Type
- journal article
- Language
- en
- Open access
- green
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: A survey of architecture design rationale. https://app.cochat.ai/papers/10.1016/j.jss.2006.04.029
- The paper
- Tang, A., Babar, M. A., Gorton, I., & Han, J. (2006). A survey of architecture design rationale. Journal of Systems and Software. https://doi.org/10.1016/j.jss.2006.04.029
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.