Using AOP to Improve Design Patterns Modularity.
Mario Luca Bernardi, Giuseppe Antonio Di Lucca
Abstract
Mario Luca Bernardi, Giuseppe Antonio Di Lucca
Abstract
The way Design Patterns (DP) are implemented may affect the modularity of a software system, due to some typical deficiencies of Object Oriented (OO) languages. Aspect Oriented Programming (AOP) provide patterns’ developers with powerful quantification constructs to better handle modularity and composition and to overcome some of the OO design trade-offs in current DP implementations. In this paper a case study where AOP has been used to re-implement DPs in existing systems from real world is presented: some different AOP re-implementations of the DPs were performed and evaluated with respect to a set of selected metrics in order to drive a better AOP design of improved DP.
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
The way Design Patterns (DP) are implemented may affect the modularity of a software system, due to some typical deficiencies of Object Oriented (OO) languages. Aspect Oriented Programming (AOP) provide patterns’ developers with powerful quantification constructs to better handle modularity and composition and to overcome some of the OO design trade-offs in current DP implementations. In this paper a case study where AOP has been used to re-implement DPs in existing systems from real world is presented: some different AOP re-implementations of the DPs were performed and evaluated with respect to a set of selected metrics in order to drive a better AOP design of improved DP.
Key concepts: Modularity (biology), Computer science, Implementation, Aspect-oriented programming, Object-oriented programming, Programming language, Software design pattern, Separation of concerns