Formalizing architectural connection
ICSE '94 Proceedings of the 16th international conference on Software engineering
On the criteria to be used in decomposing systems into modules
Communications of the ACM
Conquering aspects with Caesar
Proceedings of the 2nd international conference on Aspect-oriented software development
abc: an extensible AspectJ compiler
Proceedings of the 4th international conference on Aspect-oriented software development
Aspect-oriented programming and modular reasoning
Proceedings of the 27th international conference on Software engineering
Information hiding interfaces for aspect-oriented design
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering
Modular Software Design with Crosscutting Interfaces
IEEE Software
Adding open modules to AspectJ
Proceedings of the 5th international conference on Aspect-oriented software development
Open modules: modular reasoning about advice
ECOOP'05 Proceedings of the 19th European conference on Object-Oriented Programming
| Hi-index | 0.00 |
Aspect-oriented programming (AOP) separates crosscutting concerns from primary concerns. These concerns are woven together by a weaver. Although AOP provides a good module mechanism, it is not necessarily easy for a programmer to understand the overall behavior of a woven program. To deal with this problem, we propose a new kind of information hiding mechanism called weavinginterface that encapsulates weaving in class-based AOP in which all kinds of concerns are described in classes. Weaving-interfaces are completely separated from concerns described as classes. A programmer who designs how to compose concerns does not have to know the detail of class definitions, but has only to be aware of weaving-interfaces. On the other hand, a programmer who designs each concern does not have to know how to be composed, but has only to be aware of weaving-interfaces.