Identification of crosscutting concerns at design level Online publication date: Sat, 26-Nov-2016
by Fairouz Dahi; Nora Bounour
International Journal of Computer Applications in Technology (IJCAT), Vol. 54, No. 4, 2016
Abstract: The existence of crosscutting concerns scattered or tangled in the source code complicates the software comprehension, maintenance, evolution and reuse. To improve the modularity of software systems, several approaches aimed to identify the crosscutting concerns to allow their modelling by aspects, in order to take advantage of the benefits of the aspect-oriented paradigm. In the absence of early detection of these crosscutting concerns, they tend to be overlooked and become closely linked, not allowing developers to identify an optimal design. This paper proposes a new approach for crosscutting concerns identification at design level. This latter is materialised by class and sequence diagrams. Sequence diagram carries pertinent information which consists of interactions between objects of the software system, and the chronological order of its tasks.
Existing subscribers:
Go to Inderscience Online Journals to access the Full Text of this article.
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of Computer Applications in Technology (IJCAT):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable). See our Orders page to subscribe.
If you still need assistance, please email subs@inderscience.com