Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
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
Operating systems (2nd ed.): design and implementation
Operating systems (2nd ed.): design and implementation
IBM Systems Journal
Linux as a case study: its extracted software architecture
Proceedings of the 21st international conference on Software engineering
Characteristics of application software maintenance
Communications of the ACM
The Cathedral and the Bazaar
The 4+1 View Model of Architecture
IEEE Software
The Orphan Adoption Problem in Architecture Maintenance
WCRE '97 Proceedings of the Fourth Working Conference on Reverse Engineering (WCRE '97)
Wins and Losses of Algebraic Transformations of Software Architectures
Proceedings of the 16th IEEE international conference on Automated software engineering
Characterizing software architecture changes: A systematic review
Information and Software Technology
Controlling software architecture erosion: A survey
Journal of Systems and Software
Hi-index | 0.00 |
As a software system evolves, it is common for the as-built architecture to diverge from the as-designed architecture. This gap between the as-designed (conceptual) and the as-built (concrete) architecture leads to a false understanding of the system, resulting in error prone maintenance decisions. We present an approach to repair an architecture of a software system. Our approach attempts to reconcile the conceptual architecture with the concrete architecture by performing a series of simple, semi-automatic repair actions. We applied our architecture repair actions to the Linux kernel and were able to repair many of the anomalies its architecture.