Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Abstractions for Software Architecture and Tools to Support Them
IEEE Transactions on Software Engineering - Special issue on software architecture
The mythical man-month (anniversary ed.)
The mythical man-month (anniversary ed.)
Software reflexion models: bridging the gap between source and high-level models
SIGSOFT '95 Proceedings of the 3rd ACM SIGSOFT symposium on Foundations of software engineering
An empirical study of static call graph extractors
Proceedings of the 18th international conference on Software engineering
IBM Systems Journal
Structural Redocumentation: A Case Study
IEEE Software
Recovering the Structure of Software Systems Using Tube Graph Interconnection Clustering
ICSM '96 Proceedings of the 1996 International Conference on Software Maintenance
A hybrid process for recovering software architecture
CASCON '96 Proceedings of the 1996 conference of the Centre for Advanced Studies on Collaborative research
View Extraction and View Fusion in Architectural Understanding
ICSR '98 Proceedings of the 5th International Conference on Software Reuse
An Introduction to Software Architecture
An Introduction to Software Architecture
Deriving a Fault Architecture from Defect History
ISSRE '99 Proceedings of the 10th International Symposium on Software Reliability Engineering
Information-Theoretic Software Clustering
IEEE Transactions on Software Engineering
Computer Supported Cooperative Work
An Iterative Framework for Software Architecture Recovery: An Experience Report
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
Coordination implications of software architecture in a global software development project
Journal of Systems and Software
On the congruence of modularity and code coupling
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
| Hi-index | 0.00 |
Architectural documentation is recognised as a mechanism for improving software quality and reducing development costs. However, many existing systems do not have any architectural documentation. To obtain the benefits of accurate architectural documentation, research suggests that we use tools to recover the architecture of a system, then continue to use these tools to keep the documentation up to date. This paper describes how the organization of system developers can be extracted and analysed to form an ownership architecture. According to Conway's law, the ownership architecture serves as a predictor of the concrete (as built) architecture, and also provides facts about the location of live design knowledge. To evaluate the usefulness of ownership architectures, we examined three large software systems: Linux1 (800 KLOC), Mozilla (1.5 MLOC), and a commercial software development system (3.8 MLOC). Experience with these systems indicates that ownership architectures can be a powerful addition to a reverse engineering endeavour.