An initial assessment of aspect-oriented programming
Proceedings of the 21st international conference on Software engineering
A study on exception detection and handling using aspect-oriented programming
Proceedings of the 22nd international conference on Software engineering
Specification, implementation, and deployment of components
Communications of the ACM
COTS Software: The Economical Choice?
IEEE Software
ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
A Process for COTS Software Product Evaluation
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
Aspect-Oriented Programming with C# and .NET
ISORC '02 Proceedings of the Fifth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing
Large-scale AOSD for middleware
Proceedings of the 3rd international conference on Aspect-oriented software development
Overlooked Aspects of COTS-Based Development
IEEE Software
Components meet aspects: Assessing design stability of a software product line
Information and Software Technology
Developing applications with aspect-oriented change realization
CEE-SET'08 Proceedings of the Third IFIP TC 2 Central and East European conference on Software engineering techniques
ECSA'11 Proceedings of the 5th European conference on Software architecture
Improving extensibility of object-oriented frameworks with aspect-oriented programming
ICSR'06 Proceedings of the 9th international conference on Reuse of Off-the-Shelf Components
Hi-index | 0.00 |
More and more software projects are using COTS (Commercial-off-the-shelf) components. Using COTS components brings both advantages and risks. To manage some risks in using COTS components, it is necessary to increase the reusability of the glue-code so that the problematic COTS components can easily be replaced by other components. Aspect-oriented programming (AOP) claims to make it easier to reason about, develop, and maintain certain kinds of application code. To investigate whether AOP can help to build an easy-to-change COTS-based system, a case study was performed by comparing changeability between an object-oriented application and its aspect-oriented version. Results from this study show that integrating COTS component using AOP may help to increase the changeability of the COTS component-based system, if the cross-cutting concerns in the glue-code are homogenous (i.e., consistent application of the same or very similar policy in multiple places). Extracting heterogeneous or partial homogenous crosscutting concerns in glue-code as aspects does not provide benefits. Results also show that some limitations in AOP tools may make it impossible to use AOP in COTS-based development.