The DOI matches its Crossref record; 25 of the 25 references it cites were found in a registry or an index.
How Do Software Architects Specify and Validate Quality Requirements?
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?
In the citing paper
“Instead, some organizations rely heavily on periodical manual inspection, in line with the observations of previous studies (e.g., [18]).”
From Software Architecture in Practice: Challenges and Opportunities (2023) · cites this paper as [18]
Citations
Cites
Qualitative Data Analysis: An Expanded Sourcebook
(1994) · Journal of Environmental Psychology · doi:10.1016/s0272-4944(05)80231-2 · Cited by 48,420
Designing and Conducting Mixed Methods Research
Robinson, P. (2007) · Australian and New Zealand Journal of Public Health · doi:10.1111/j.1753-6405.2007.00096.x · Cited by 23,258
The 4+1 View Model of architecture
Kruchten, P. B. (1995) · IEEE Software · doi:10.1109/52.469759 · Cited by 2,158
Specifying distributed software architectures
Magee, J., Dulay, N., Eisenbach, S., & Kramer, J. (1995) · Lecture Notes in Computer Science · doi:10.1007/3-540-60406-5_12 · Cited by 764
Acme: Architectural Description of Component-Based Systems
Garlan, D., Monroe, R. T., & Wile, D. S. (2018) · KiltHub Repository · doi:10.1184/r1/6602945 · Cited by 517
The Architecture Analysis & Design Language (AADL): An Introduction
Feiler, P. H., Gluch, D. P., & Hudak, J. (2006) · Figshare · doi:10.1184/r1/6584909 · Cited by 489
The Architecture Analysis & Design Language (AADL): An Introduction
Feiler, P. H., Gluch, D. P., & Hudak, J. (2006) · doi:10.21236/ada455842 · Cited by 343
What Industry Needs from Architectural Languages: A Survey
Malavolta, I., Lago, P., Muccini, H., Pelliccione, P., & Tang, A. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2012.74 · Cited by 296
Diagrammatic Representation and Inference
Ferri, F. (2018) · Lecture notes in computer science · doi:10.1007/978-3-319-91376-6 · Cited by 263
How do software architects consider non-functional requirements: An exploratory study
Ameller, D., Ayala, C. P., Cabot, J., et al. (2012) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2012.6345838 · Cited by 114
Cited by
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
“Instead, some organizations rely heavily on periodical manual inspection, in line with the observations of previous studies (e.g., [17]).”
Result
Metadata
- Authors
- Caracciolo, A., Lungu, M. F., & Nierstrasz, O.
- Affiliations
- University of Bern (CH)
- Venue
- Lecture Notes in Computer Science
- Publisher
- Springer International Publishing
- Published
- 2014
- Pages
- 374-389
- ISSN
- 0302-9743 (ISSN-L)
- 1611-3349
- OpenAlex
- W2139209962
- Cited by
- 32
- References
- 25
- Citations by year
- 2025: 1 · 2024: 2 · 2023: 1 · 2022: 2 · 2021: 7 · 2020: 1 · 2019: 1 · 2018: 4 · 2017: 4 · 2016: 3 · 2015: 5 · 2014: 1
- FWCI
- 2.55
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- Lecture notes in computer science (publishedVersion)
- BORIS (University Library Bern) (submittedVersion)
- Topics
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Model-Driven Software Engineering Techniques
- Keywords
- software architecture, non-functional requirements, quality attributes, requirements validation, requirements specification, practitioner survey, tool support
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: How Do Software Architects Specify and Validate Quality Requirements? https://app.cochat.ai/papers/10.1007/978-3-319-09970-5_32
- The paper
- Caracciolo, A., Lungu, M. F., & Nierstrasz, O. (2014). How Do Software Architects Specify and Validate Quality Requirements? Lecture Notes in Computer Science. https://doi.org/10.1007/978-3-319-09970-5_32
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.
