Aspect-oriented Programming Implementation Research Articles

MAINTENANCE EFFORT PREDICTION MODEL USING ASPECT-ORIENTED COGNITIVE COMPLEXITY METRICS

Software development is a multifaceted process. It is challenging to define or measure software qualities and quantities and to determine a valid and concurrent measurement metric. In software development, a metric is the measurement of a particular characteristic of a program's performance or efficiency.The goal of software metrics is to improve understanding of a product or process. Aspect Oriented Programming (AOP) extends the traditional object-oriented programming (OOP) model to improve code reuse across different object hierarchies. AOP can be used with object oriented programming. AspectJ is an implementation of aspect-oriented programming for Java. Software maintenance is the most desired, but most elusive and difficult task in software engineering. The cost of maintenance is as high as 60% to 80% of the total cost of the software. So, plenty of this project are going on in software maintenance. Though, Aspect-oriented paradigm has made it easier, it remains the critical hotspot of research. One way of grappling with the maintenance problem, is to use the complexity metrics. Many studies were made to understand the relationship among complexity metrics, cognition, and maintenance. This paper wrestles with four newly proposed object-oriented cognitive complexity metrics to develop maintenance effort prediction models through various statistical techniques.Empirical study designs are made with ANOVA and experimented.Discussion on results proves the maintenance effort prediction models are more robust, more accurate, and can be employed to estimate the maintenance effort.

The Study on the Implementation of AOP in .NET Platform

AOP(Aspect Oriented Programming) is a programming technology that makes the OOP (Object Oriented Programming) technology more complementary and perfect when being applied together with OOP technology. AOP provides ideal modularized structure for programming. At the moment, AOP has been supported and applied in two leading programming platforms: Java and .Net. Java provides perfect support to AOP, but .Net has not clearly provided the technique to support AOP. Meanwhile, Design Pattern has been widely used in programming. This study analyzes the theory of AOP technique and provides an implementation strategy for AOP based techniques on Proxy Pattern in .Net platform.

Dynamic aspect mining

Legacy systems often contain several crosscutting concerns that could potentially benefit from an aspect-oriented programming implementation. In this paper, we focus on the problem of aspect identification in existing code. The main idea is that use-cases can be defined in order to separate the base logics from the crosscutting concerns to be aspectised. The relationship between the execution traces associated with the use-cases and the executed computational units (class methods) is analysed through concept analysis. The results obtained on some case studies are discussed in the paper.

Using aspect orientation in legacy environments for reverse engineering using dynamic analysis—An industrial experience report

This paper reports on the challenges of using aspect-oriented programming (AOP) to aid in re-engineering a legacy C application. More specifically, we describe how AOP helps in the important reverse engineering step which typically precedes a re-engineering effort. We first present a comparison of the available AOP tools for legacy C code bases, and then argue on our choice of Aspicere, our own AOP implementation for C. Then, we report on Aspicere’s application in reverse engineering a legacy industrial software system and we show how we apply a dynamic analysis to regain insight into the system. AOP is used for instrumenting the system and for gathering the data. This approach works and is conceptually very clean, but comes with a major quid pro quo: integration of AOP tools with the build system proves an important issue. This leads to the question of how to reconcile the notion of modular reasoning within traditional build systems with a programming paradigm which breaks this notion.