Applied software architecture
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
The 4+1 View Model of Architecture
IEEE Software
Quantitative Analysis of Faults and Failures in a Complex Software System
IEEE Transactions on Software Engineering
Preliminary guidelines for empirical research in software engineering
IEEE Transactions on Software Engineering
Metrics for Evaluating the Quality of Entity Relationship Models
ER '98 Proceedings of the 17th International Conference on Conceptual Modeling
Module Size Distribution and Defect Density
ISSRE '00 Proceedings of the 11th International Symposium on Software Reliability Engineering
An Empirical Study of Software Reuse vs. Defect-Density and Stability
Proceedings of the 26th International Conference on Software Engineering
Software Architecture as a Set of Architectural Design Decisions
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Package coupling measurement in object-oriented software
Journal of Computer Science and Technology
Editorial: Design decisions and design rationale in software architecture
Journal of Systems and Software
Reusable architectural decision models for enterprise application development
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
Exploring the Relationships between Design Metrics and Package Understandability: A Case Study
ICPC '10 Proceedings of the 2010 IEEE 18th International Conference on Program Comprehension
| Hi-index | 0.00 |
The architecture of a software system plays a crucial role during evolution and maintenance, as it provides the means to cope with the inherent system complexity by abstracting from implementation and design details. Architectural component models represent high level designs and are frequently used as a central view of architectural descriptions of software systems. Hence, understandability of those models is crucial as they play a key role in supporting the architectural understanding of a software system. In this paper we present the results from a study we carried out to examine to which extent the software architecture could be conveyed through architectural component diagrams. The statistical evaluation of the results shows that metrics such as the number of components, number of connectors, number of elements, and number of symbols used in the diagrams can significantly decrease architectural understandability when they are above and below a certain, roughly predicted threshold. Also, our results indicate that architectural understandability is linearly correlated with the perceived precision and general understandability of the diagrams.