Coupling on Method Call Metric—A Cognitive Approach

  • K. R. Martin
  • E. Kirubakaran
  • E. George Dharma Prakash Raj
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 645)


Software development is a greatly multifaceted and intellect-oriented movement. In the early days of program development, developers engraved programs using machine language in which programmers consumed added time, thinking about a particular machine’s instruction set than the difficulty at hand. Progressively, programmers wandered to higher level languages. In order to progress software using higher level languages, there are different approaches and selection of software development approach depending on the type of application to be established. Aspect-oriented software development (AOSD) is a novel paradigm in software development that addresses certain concerns in software development that regards modularization as an important aspect. The practices of AOSD create the possibilities to modularize, crosscutting the concerns of a system. Analogous to objects in object-oriented software development, aspects in AOSD may ascend at any point of time of the software life cycle, containing requirements specification, design, implementation, etc. As this effort is built on empirical validating aspect-oriented metrics, coupling on method call (CMC) metric is selected. This work focuses on empirical validation of the metrics. Novel metric is cognitive weighted metric, which is calculated for CMC to calculate the coupling complexity value of the aspect.


Software metrics Aspect-oriented software development (AOSD) Aspect-oriented programming (AOP) Coupling on method call (CMC) Cognitive weighted coupling on method call (CWCMC) 


  1. 1.
    Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Lopes, C., Loingtier, J.M., Irwin, J.: Aspect-Oriented Programming, pp. 220–242. Springer, Berlin, Heidelberg (1997)Google Scholar
  2. 2.
    The AspectJ Team: The AspectJ Programming Guide (2003)Google Scholar
  3. 3.
    Ceccato, M., Tonella, P.: Measuring the Effects of Software Aspectization: WARE (2004)Google Scholar
  4. 4.
    Aloysius, A., Arockia Sahaya Sheela, G.: Aspect oriented programming metrics—a survey. Int. J. Emerg. Trends Comput. Commun. Technol. 1(3), 125–130 (2015)Google Scholar
  5. 5.
    Kulesza, U.: Quantifying the effects of aspect-oriented programming: a maintenance study. In: 22nd IEEE International Conference on Software Maintenance 2006, ICSM’06. IEEE (2006)Google Scholar
  6. 6.
    The AspectJ Team: The AspectJ Programming Guide (2001). Gradecki, J.D., Lesiecki, N.: Mastering AspectJ—Aspect-Oriented Programming in Java (2003)Google Scholar
  7. 7.
    Bartsch, M., Harrison, R.: An evaluation of coupling measures for AspectJ. In: LATE Workshop AOSD (2006)Google Scholar
  8. 8.
    Wang, Y.: On cognitive informatics. In: IEEE International Conference on Cognitive Informatics, pp. 69–74 (2002)Google Scholar

Copyright information

© Springer Nature Singapore Pte Ltd. 2018

Authors and Affiliations

  • K. R. Martin
    • 1
  • E. Kirubakaran
    • 2
  • E. George Dharma Prakash Raj
    • 3
  1. 1.St. Joseph’s CollegeTiruchirappalliIndia
  2. 2.BHELTiruchirappalliIndia
  3. 3.Bharathidasan UniversityTiruchirappalliIndia

Personalised recommendations