The DOI matches its Crossref record; 45 of the 45 references it cites were found in a registry or an index.
What Industry Needs from Architectural Languages: A Survey
Abstract
Many times we are faced with the proliferation of definitions, concepts, languages, and tools in certain (research) topics. But often there is a gap between what is provided by existing technologies and what is needed by their users. The strengths, limitations, and needs of the available technologies can be dubious. The same applies to software architectures, and specifically to languages designed to represent architectural models. Tens of different architectural languages have been introduced by the research and industrial communities in the last two decades. However, it is unclear if they fulfill the user's perceived needs in architectural description. As a way to plan for next generation languages for architectural description, this study analyzes practitioners' perceived strengths, limitations, and needs associated with existing languages for software architecture modeling in industry. We run a survey by interviewing 48 practitioners from 40 different IT companies in 15 countries. Each participant is asked to fill in a questionnaire of 51 questions. By analyzing the data collected through this study, we have concluded that 1) while practitioners are generally satisfied with the design capabilities provided by the languages they use, they are dissatisfied with the architectural language analysis features and their abilities to define extra-functional properties; 2) architectural languages used in practice mostly originate from industrial development instead of from academic research; 3) more formality and better usability are required of an architectural language.
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
Qualitative Data Analysis: An Expanded Sourcebook
(1994) · Journal of Environmental Psychology · doi:10.1016/s0272-4944(05)80231-2 · Cited by 48,420
Questionnaire Design, Interviewing and Attitude Measurement
Albuam, G., & Oppenheim, A. N. (1993) · Journal of Marketing Research · doi:10.2307/3172892 · Cited by 4,971
Software architecture: perspectives on an emerging discipline
Shaw, M., & Garlan, D. (1996) · CERN Document Server (European Organization for Nuclear Research) · Cited by 2,910
The 4+1 View Model of architecture
Kruchten, P. B. (1995) · IEEE Software · doi:10.1109/52.469759 · Cited by 2,158
Foundations for the study of software architecture
Perry, D. E., & Wolf, A. L. (1992) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/141874.141884 · Cited by 2,023
A classification and comparison framework for software architecture description languages
Medvidovic, N., & Taylor, R. N. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.825767 · Cited by 1,987
Documenting software architectures: views and beyond
Clements, P., Garlan, D., Little, R., Nord, R., & Stafford, J. (2003) · 25th International Conference on Software Engineering, 2003. Proceedings. · doi:10.1109/icse.2003.1201264 · Cited by 1,430
A formal basis for architectural connection
Allen, R., & Garlan, D. (1997) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/258077.258078 · Cited by 1,253
Design and Use of Software Architectures: Adopting and Evolving a Product-Line Approach
Bosch, J. (2000) · Medical Entomology and Zoology · Cited by 1,159
Introduction to Software Architecture
(2009) · Advanced Topics in Science and Technology in China · doi:10.1007/978-3-540-74343-9_1 · Cited by 1,099
Cited by
Towards Human-Bot Collaborative Software Architecting with ChatGPT
Ahmad, A., Waseem, M., Liang, P., Fahmideh, M., Aktar, M. S., & Mikkonen, T. (2023) · Proceedings of the 27th International Conference on Evaluation and Assessment in Software Engineering · doi:10.1145/3593434.3593468 · Cited by 168
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-citationKazman, R., Goldenson, D., Monarch, I., Nichols, W., & Valetto, G. (2016) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2015.2465387 · Cited by 31
How Do Software Architects Specify and Validate Quality Requirements?
Caracciolo, A., Lungu, M. F., & Nierstrasz, O. (2014) · Lecture Notes in Computer Science · doi:10.1007/978-3-319-09970-5_32 · Cited by 32
Metadata
- Authors
- Malavolta, I., Lago, P., Muccini, H., Pelliccione, P., & Tang, A.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2013-06
- Volume
- 39
- Issue
- 6
- Pages
- 869-891
- ISSN
- 0098-5589 (ISSN-L)
- 1939-3520
- OpenAlex
- W2015280671
- Cited by
- 296
- References
- 45
- FWCI
- 35.34
- Type
- journal article
- Language
- en
- Open access
- closed
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: What Industry Needs from Architectural Languages: A Survey. https://app.cochat.ai/papers/10.1109/tse.2012.74
- The paper
- Malavolta, I., Lago, P., Muccini, H., Pelliccione, P., & Tang, A. (2013). What Industry Needs from Architectural Languages: A Survey. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.2012.74
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.