Software architecture in practice
Software architecture in practice
The structure and value of modularity in software design
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
A survey on software architecture analysis methods
IEEE Transactions on Software Engineering
ASAAM: Aspectual Software Architecture Analysis Method
WICSA '04 Proceedings of the Fourth Working IEEE/IFIP Conference on Software Architecture
An analysis of modularity in aspect oriented design
Proceedings of the 4th international conference on Aspect-oriented software development
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
Assessing aspect modularizations using design structure matrix and net option value
Transactions on Aspect-Oriented Software Development I
An agenda for concern-oriented software engineering
Proceedings of the FSE/SDP workshop on Future of software engineering research
A design perspective on modularity
Proceedings of the tenth international conference on Aspect-oriented software development
Controlling software architecture erosion: A survey
Journal of Systems and Software
Hi-index | 0.00 |
Current scenario-based architecture analysis methods analyze the architecture with respect to scenarios that relate to stakeholder concerns. Albeit the primary motivation is to analyze the impact of stakeholders' concerns, it appears that concerns are not explicitly represented as first class abstractions. The lack of an explicit notion of concern in scenario-based analysis approaches can result in an incomplete analysis because scenarios are too specific and can only partially represent the concerns. We propose the concern-oriented architecture analysis method (COSAAM) that builds on scenario-based approaches but includes an explicit notion of concern in the analysis. COSAAM applies Dependency Structure Matrices (DSMs) to represent and analyze the dependencies among scenarios, concerns and architectural elements. Further, COSAAM extends DSMs by introducing explicit DSM patterns and heuristic rules for analyzing the impact of concerns on the architecture and for supporting the refactoring of the architecture.