Reconciling environment integration and software evolution
ACM Transactions on Software Engineering and Methodology (TOSEM)
Mediators: easing the design and evolution of integrated systems
Mediators: easing the design and evolution of integrated systems
Evaluating The Mediator Method: Prism as a Case Study
IEEE Transactions on Software Engineering
Non-modularity in aspect-oriented languages: integration as a crosscutting concern for AspectJ
AOSD '02 Proceedings of the 1st international conference on Aspect-oriented software development
Formalizing Design Spaces: Implicit Invocation Mechanisms
VDM '91 Proceedings of the 4th International Symposium of VDM Europe on Formal Software Development-Volume I: Conference Contributions - Volume I
Eos: instance-level aspects for integrated system design
Proceedings of the 9th European software engineering conference held jointly with 11th ACM SIGSOFT international symposium on Foundations of software engineering
| Hi-index | 0.01 |
Component integration creates value by automatingthe costly and error-prone task of imposing desiredbehavioral relationships on components manually.Requirements for component integration, however,complicate software design and evolution in severalways: first, they lead to coupling among components;second, the code that implements various integrationconcerns in a system is often scattered over and tangledwith the code implementing the component behaviors.Straightforward software design techniques mapintegration requirements to scattered and tangled code,compromising modularity in ways that dramaticallyincrease development and maintenance costs.