Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Monitoring compliance of a software system with its high-level design models
Proceedings of the 18th international conference on Software engineering
Automatic code generation from design patterns
IBM Systems Journal
The pragmatic programmer: from journeyman to master
The pragmatic programmer: from journeyman to master
Software Change Impact Analysis
Software Change Impact Analysis
ArchJava: connecting software architecture to implementation
Proceedings of the 24th International Conference on Software Engineering
Software Reflexion Models: Bridging the Gap between Design and Implementation
IEEE Transactions on Software Engineering
MDA Explained: The Model Driven Architecture: Practice and Promise
MDA Explained: The Model Driven Architecture: Practice and Promise
Speechnet: A Network of Hyperlinked Speech-Accessible Objects
WECWIS '99 Proceedings of the International Workshop on Advance Issues of E-Commerce and Web-Based Information Systems
Code Generation in Action
The Golden Age of Software Architecture
IEEE Software
EMF: Eclipse Modeling Framework 2.0
EMF: Eclipse Modeling Framework 2.0
Domain-Specific Modeling
ArchStudio 4: An Architecture-Based Meta-Modeling Environment
ICSE COMPANION '07 Companion to the proceedings of the 29th International Conference on Software Engineering
Software Architecture: Foundations, Theory, and Practice
Software Architecture: Foundations, Theory, and Practice
Taming changes With 1.x-Way architecture-implementation mapping
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
| Hi-index | 0.00 |
A new architecture-implementation mapping approach, 1.x-way mapping, is presented to address architecture-implementation conformance. It targets maintaining conformance of structure and behavior, providing a solution to architecture changes, and protecting architecture-prescribed code from being manually changed. Technologies developed in this work include deep separation of generated and non-generated code, an architecture change model, architecture-based code regeneration, and architecture change notification.