Traceability and association between models in aspect oriented programming

Traceability and association between models in aspect oriented programming

Asim IsmailAmbreen Yousuf 

SZABIST Dubai, CIIT Pakistan

Corresponding Author Email:
31 March 2017
| Citation



Aspect Oriented Programming (AOP) is evolving as a better modular programming paradigm compared to the traditional Object Oriented Programming (OOP). Due to the increasing popularity, there is a need of techniques for the quantifiable measurement of AOP-based system design models. The main idea therefore is to develop such a technique, which can evaluate AOP-based software models for the association between them, and to improve traceability of system requirements. Software metric could map design models with each other, and could provide a mechanism to trace requirements from early phase to their implementation.There are some metrics already available to evaluate some specific property of an aspect-oriented model, such as cohesion, coupling, size, etc. However, there was a chance to design metrics for evaluating Aspect Oriented and UML models comprehensively, for example for evaluating mapping of models, associationbetween models and inter and intra-dependencies of models. In this research traceability technique has been designed to check the validation of aspect oriented and UML models. Models are mapped with the help of traceability matrix and metadata keys. Each design model has a unique key, which has three parts: module number, phase ID and diagram number. With the help of this key, 3D traceability matrix and mapping diagrams have been designed, which shows the association between the models and as a result make the overall system design more traceable. The evaluation of the technique has revealed that the resultant technique has improved mapping between the design models and as a result have enhanced effective traceability of the requirements of the system.


AOP, UML, Metric, Traceability, Metadata Key.

1. Introduction
2. Methodology
3. Problem Verbalization
4. Aspect Oriented Programming
5. Key
6. Tables and Figures
7. Conclusions

[1] Futrell R.T., Shafer L.I., D.F. (2002). Quality Software Project Management, Upper Saddle River, Prentice Hall PTR, NJ, USA.

[2] SantAnna A.C., Garcia C., Chavez C., Lucena A., Von Staa. (2003). On the reuse and maintenance of aspect-oriented software: an assessment framework, in Proceedings of Brazilian Symposium on Software Engineering, pp. 19-34.

[3] Z.F., Requirements traceability matrix, from, accessed 25 Dec 2016.

[4] Schlageter G., Unland R., Wilkes W., Zieschang R., Maul G., Nagl M., Meyer R. (1988). Oops-an object-oriented programming system with integrated data management facility in Data Engineering, Proceedings Fourth International Conference 1988 IEEE, pp. 118-125. DOI: 10.1109/ICDE.1988.105453

[5] Bachmendo B., Hanenberg S., Herrmann S., Kniesel G. (2003). Aspect-oriented software development, Proceedings of the Third German AOSD-Workshop of the SIG Object-Oriented Software Development, German Informatics Society,2003.