TY - GEN
T1 - An aspect-oriented weaving mechanism based on component and connector architecture
AU - Ubayashi, Naoyasu
AU - Sakai, Akihiro
AU - Tamai, Tetsuo
PY - 2007/12/1
Y1 - 2007/12/1
N2 - Aspect-oriented programming (AOP) separates crosscutting concerns from primary concerns. These concerns are woven together by a weaver. Although AOP provides an effective 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 a weaving-interface that encapsulates weaving in class-based AOP in which all kinds of concerns are described according to classes. Weaving-interfaces are completely separated from concerns described in terms of classes. A programmer who designs how to compose concerns does not have to know the details of class definitions, but has only to be aware of weaving-interfaces. A programmer who designs each concern does not have to know how the concern is composed, but has only to be aware of weaving-interfaces. Adopting the weaving-interface mechanism, AO weaving can be realized by the component-and-connector software architecture. This weaving-interface mechanism is effective for software modularity, evolution, and reuse.
AB - Aspect-oriented programming (AOP) separates crosscutting concerns from primary concerns. These concerns are woven together by a weaver. Although AOP provides an effective 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 a weaving-interface that encapsulates weaving in class-based AOP in which all kinds of concerns are described according to classes. Weaving-interfaces are completely separated from concerns described in terms of classes. A programmer who designs how to compose concerns does not have to know the details of class definitions, but has only to be aware of weaving-interfaces. A programmer who designs each concern does not have to know how the concern is composed, but has only to be aware of weaving-interfaces. Adopting the weaving-interface mechanism, AO weaving can be realized by the component-and-connector software architecture. This weaving-interface mechanism is effective for software modularity, evolution, and reuse.
UR - http://www.scopus.com/inward/record.url?scp=70450236413&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=70450236413&partnerID=8YFLogxK
U2 - 10.1145/1321631.1321656
DO - 10.1145/1321631.1321656
M3 - Conference contribution
AN - SCOPUS:70450236413
SN - 9781595938824
T3 - ASE'07 - 2007 ACM/IEEE International Conference on Automated Software Engineering
SP - 154
EP - 163
BT - ASE'07 - 2007 ACM/IEEE International Conference on Automated Software Engineering
T2 - 22nd IEEE/ACM International Conference on Automated Software Engineering, ASE'07
Y2 - 5 November 2007 through 9 November 2007
ER -