empirical evaluation of metrics on aspect-oriented programs

Abstract


 The quality evaluation of software metrics measurement is considered as the primary indicator of imperfection prediction and software maintenance in various empirical studies of software products. However, there is no agreement on which metrics are compelling quality pointers for new software development approaches such as aspect-oriented programming (AOP) techniques. AOP intends to enhance programming quality by providing fundamentally different parts of the systems, for example, pointcuts, advice, and intertype relationships. Hence, it is not evident if quality characteristics for AOP could be extracted from direct expansions of traditional object-oriented programming (OOP) measurements. Then again, investigations of AOP do regularly depend on established static and dynamic metrics measurement; notwithstanding the late research of AOP in empirical studies, few analyses been adopted using the International Organization for Standardization 9126 quality model as useful markers of flaw inclination in this context. This paper examination we have considered different programming quality models given by various authors every once in a while and distinguished that adaptability was deficient in the current model. We have testing 10 projects developed by AOP. We have used many applications to extract the metrics, but none of them could extract all AOP Metrics. It only can measure some of AOP Metrics, not all of them. This study investigates the suitable framework for extract AOP Metrics, for instance, static and dynamic metrics measurement for hybrid application systems (AOP and OOP) or only AOP application.

Quality Metrics measurement for Hybrid Systems (Aspect Oriented Programming – Object Oriented Programming)

“…Three experienced programmers, with three open AO/OO projects, using a script to extract AOP and the Object-Oriented Programming (OOP) metric approach and reflect on new proposal quality framework. The paper includes a comparison of the developed systems AOP and OOP,Chidamber and Kemerer (hereafter CK) [2], Distance from the most sequence metric proposed by Chidamber and Kemerer Martin [3], out-of-code standard metric (defined as acceptance variety Tests passed) [4,5,6], and productivity metrics for programmers. CK Technology metrics [2] adapted to new aspect-oriented properties [7] [8][9] [10].…”