Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Exploiting ADLs to specify architectural styles induced by middleware infrastructures
Proceedings of the 21st international conference on Software engineering
On the criteria to be used in decomposing systems into modules
Communications of the ACM
Alloy: a lightweight object modelling notation
ACM Transactions on Software Engineering and Methodology (TOSEM)
Analyzing architectural styles with alloy
Proceedings of the ISSTA 2006 workshop on Role of software architecture for testing and analysis
A Scalable Approach to Multi-style Architectural Modeling and Verification
ICECCS '08 Proceedings of the 13th IEEE International Conference on on Engineering of Complex Computer Systems
Software Architecture: Foundations, Theory, and Practice
Software Architecture: Foundations, Theory, and Practice
Architecture as an independent variable for aspect-oriented application descriptions
ABZ'10 Proceedings of the Second international conference on Abstract State Machines, Alloy, B and Z
Monarch: model-based development of software architectures
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part II
A formal approach to software synthesis for architectural platforms
Proceedings of the 33rd International Conference on Software Engineering
Architectural point mapping for design traceability
Proceedings of the eleventh workshop on Foundations of Aspect-Oriented Languages
Pol: specification-driven synthesis of architectural code frameworks for platform-based applications
Proceedings of the 11th International Conference on Generative Programming and Component Engineering
| Hi-index | 0.00 |
A key idea in modern software engineering is that we can and should make architectural style choices separately from choices about many other system properties. There is a fundamental separation of concerns implicit in this idea: given an application model that expresses system properties independently of architectural style, we can choose a compatible architectural style and then map the application model to one or more architectural models (architectures) in this style. The problem is that we do not have a formal account of this separation of concerns, or the associated architectural maps, sufficient to enable automated synthesis of architectures from application models and architecture style specifications. The contribution of this work is such an account and a demonstration that it enables automated formal derivation of style-specific architectures.