SAAM: a method for analyzing the properties of software architectures
ICSE '94 Proceedings of the 16th international conference on Software engineering
AntiPatterns: refactoring software, architectures, and projects in crisis
AntiPatterns: refactoring software, architectures, and projects in crisis
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Safer C: Developing Software for in High-Integrity and Safety-Critical Systems
Safer C: Developing Software for in High-Integrity and Safety-Critical Systems
Extending and Managing Software Reflexion Models
Extending and Managing Software Reflexion Models
The Rational Unified Process: An Introduction
The Rational Unified Process: An Introduction
Effective C++: 55 Specific Ways to Improve Your Programs and Designs (3rd Edition)
Effective C++: 55 Specific Ways to Improve Your Programs and Designs (3rd Edition)
Using dependency models to manage complex software architecture
OOPSLA '05 Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Improving software quality with static analysis
PASTE '07 Proceedings of the 7th ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
Effective Java (2nd Edition) (The Java Series)
Effective Java (2nd Edition) (The Java Series)
Software evolution visualization: A systematic mapping study
Information and Software Technology
| Hi-index | 0.00 |
In lots of software projects unfortunately an architectural erosion happens over time. Modules which were independent, become connected, plug-ins finally depend on each other, and in general the architecture gets violated more and more. In this paper we will discuss how to avoid such architecture- and design-erosion and how an already eroded system can be fixed again. We will look at three different level of static analysis and examine architectural analysis in detail. Also typical use cases for architectural analysis are examined, followed by a collection of requirements for powerful tool support. The eclipse platform serves as case study and we look if, and how far architectural erosion happened there and if it can be fixed. Finally we discuss pros and cons of architectural analysis and conclude with an out view.