The DOI matches its Crossref record; 18 of the 18 references it cites were found in a registry or an index.
Scaling up software architecture analysis
Overview
Integrity signals
Registry
Cites
Statistics
Verification
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?
As a software system evolves over time, traceability information becomes obsolete due to separate evolution of its architecture and source code.
“In addition, as a software system evolves over time, the traceability information becomes obsolete due to the separate evolution of its architecture and source code (P3b, P3e-g, P4a, P6a) (Section 6.1; also observed in previous studies, e.g., [41]).”
From Software Architecture in Practice: Challenges and Opportunities (2023) · cites this paper as [41]
Citations
Cites
Software Architecture in Practice
Bass, L., Clements, P., & Kazman, R. (1997) · Cited by 5,033
Self-citationNuseibeh, B., & Easterbrook, S. (2000) · Future of Software Engineering (FOSE) · doi:10.1145/336512.336523 · Cited by 1,836
Evaluating Software Architectures: Methods and Case Studies
Clements, P., Kazman, R., & Klein, M. M. (2001) · Medical Entomology and Zoology · Cited by 849
Self-citationHofmeister, C. C., Nord, R. L., & Soni, D. A. (2009) · CERN Document Server (European Organization for Nuclear Research) · Cited by 645
Safety-critical computer systems
Storey, N. (1996) · International Linear Collider · Cited by 605
A survey on software architecture analysis methods
Dobrica, L., & Niemelä, E. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2002.1019479 · Cited by 524
From software product lines to software ecosystems
Bosch, J. (2009) · Software Product Lines · doi:10.5555/1753235.1753251 · Cited by 497
Software Ecosystem: Understanding an Indispensable Technology and Industry
Messerschmitt, D. G., & Szyperski, C. (2003) · MIT Press Books · Cited by 372
A general model of software architecture design derived from five industrial approaches
Hofmeister, C., Kruchten, P. B., Nord, R. L., Obbink, H., Ran, A., & America, P. (2006) · Journal of Systems and Software · doi:10.1016/j.jss.2006.05.024 · Cited by 308
Evaluating Software Architectures
Tvedt, R. T., Costa, P., & Lindvall, M. (2004) · Advances in computers · doi:10.1016/s0065-2458(03)61001-6 · Cited by 251
Using the ISO/IEC 9126 product quality model to classify defects : a controlled experiment
Vetrò, A., Zazworka, N., Seaman, C. B., & Shull, F. J. (2012) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1049/ic.2012.0025 · Cited by 243
Architecture-level modifiability analysis (ALMA)
Bengtsson, P., Lassing, N. H., Bosch, J., & van Vliet, H. (2003) · Journal of Systems and Software · doi:10.1016/s0164-1212(03)00080-3 · Cited by 243
Proceedings of the 13th International Software Product Line Conference
Muthig, D., & McGregor, J. D. (2009) · Cited by 134
On the similarity between requirements and architecture
de Boer, R. C., & van der Vliet, H. J. (2008) · Journal of Systems and Software · doi:10.1016/j.jss.2008.11.185 · Cited by 65
Goal Oriented Requirements Engineering: Trends and Issues
Yamamoto, S., Kaiya, H., COX, K., et al. (2006) · IEICE Transactions on Information and Systems · doi:10.1093/ietisy/e89-d.11.2701 · Cited by 61
Realizing and Refining Architectural Tactics: Availability
Scott, J., & Kazman, R. (2009) · doi:10.21236/ada512459 · Cited by 40
Self-citationGoal Oriented Requirements Engineering
Rolland, C. (2002) · Springer eBooks · doi:10.1007/978-1-4615-0167-1_4 · Cited by 8
C4ISR for Future Naval Strike Groups
National Research Council (2006) · National Academies Press eBooks · doi:10.17226/11605 · Cited by 5
Flagged first, then by citations
Cited by
Sorted by citations
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
“…studies have put effort into developing methods and tools for architecture representation and documentation [15, 38], analysis and evaluation [41, 73], recovery and optimization [2, 30, 54], as well as knowledge management and decision making [16, 100] to support software architecture…”
Method
Metadata
- Authors
- Kazman, R., Gagliardi, M., & Wood, W.
- Affiliations
- Software Engineering Institute (US)
- Corresponding author
- Kazman, Rick
- ORCID
- Kazman, Rick
- Venue
- Journal of Systems and Software
- Publisher
- Elsevier BV
- Published
- 2012-07
- Volume
- 85
- Issue
- 7
- Pages
- 1511-1519
- ISSN
- 0164-1212 (ISSN-L)
- OpenAlex
- W2099770799
- Cited by
- 31
- References
- 18
- Citations by year
- 2023: 4 · 2022: 1 · 2021: 1 · 2019: 1 · 2018: 2 · 2017: 2 · 2016: 5 · 2015: 8 · 2014: 5 · 2013: 1 · 2012: 1
- FWCI
- 2.06
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- Journal of Systems and Software (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Engineering › Control and Systems Engineering › Systems Engineering Methodologies and Applications
- Physical Sciences › Computer Science › Software › Model-Driven Software Engineering Techniques
- Keywords
- software architecture evaluation, software architecture design, architectural design principles, scalability, architectural design methodology
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
