Aspect-Oriented Change Realizations and Their Interaction

Valentino Vranić, Radoslav Menkyna, Michal Bebjak, Peter Dolog

Research output: Contribution to journalJournal articleResearchpeer-review

Abstract

With aspect-oriented programming, changes can be treated explicitly and directly at the programming
language level. An approach to aspect-oriented change realization based on a two-level
change type model is presented in this paper. In this approach, aspect-oriented change realizations
are mainly based on aspect-oriented design patterns or themselves constitute pattern-like forms
in connection to which domain independent change types can be identified. However, it is more
convenient to plan changes in a domain specific manner. Domain specific change types can be
seen as subtypes of generally applicable change types. These relationships can be maintained in a
form of a catalog. Some changes can actually affect existing aspect-oriented change realizations,
which can be solved by adapting the existing change implementation or by implementing an
aspect-oriented change realization of the existing change without having to modify its source
code. As demonstrated partially by the approach evaluation, the problem of change interaction
may be avoided to a large extent by using appropriate aspect-oriented development tools, but for
a large number of changes, dependencies between them have to be tracked. Constructing partial
feature models in which changes are represented by variable features is sufficient to discover
indirect change dependencies that may lead to change interaction.
Original languageEnglish
Journale-Informatica Software Engineering Journal
Volume3
Issue number1
Pages (from-to)43-58
Number of pages16
ISSN1897-7979
Publication statusPublished - 2009

Fingerprint

Aspect oriented programming

Cite this

Vranić, Valentino ; Menkyna, Radoslav ; Bebjak, Michal ; Dolog, Peter. / Aspect-Oriented Change Realizations and Their Interaction. In: e-Informatica Software Engineering Journal. 2009 ; Vol. 3, No. 1. pp. 43-58.
@article{7be4e1a0feca11de9a61000ea68e967b,
title = "Aspect-Oriented Change Realizations and Their Interaction",
abstract = "With aspect-oriented programming, changes can be treated explicitly and directly at the programminglanguage level. An approach to aspect-oriented change realization based on a two-levelchange type model is presented in this paper. In this approach, aspect-oriented change realizationsare mainly based on aspect-oriented design patterns or themselves constitute pattern-like formsin connection to which domain independent change types can be identified. However, it is moreconvenient to plan changes in a domain specific manner. Domain specific change types can beseen as subtypes of generally applicable change types. These relationships can be maintained in aform of a catalog. Some changes can actually affect existing aspect-oriented change realizations,which can be solved by adapting the existing change implementation or by implementing anaspect-oriented change realization of the existing change without having to modify its sourcecode. As demonstrated partially by the approach evaluation, the problem of change interactionmay be avoided to a large extent by using appropriate aspect-oriented development tools, but fora large number of changes, dependencies between them have to be tracked. Constructing partialfeature models in which changes are represented by variable features is sufficient to discoverindirect change dependencies that may lead to change interaction.",
author = "Valentino Vranić and Radoslav Menkyna and Michal Bebjak and Peter Dolog",
year = "2009",
language = "English",
volume = "3",
pages = "43--58",
journal = "e-Informatica",
issn = "1897-7979",
publisher = "Politechnika Wroclawska * Oficyna Wydawnicza",
number = "1",

}

Aspect-Oriented Change Realizations and Their Interaction. / Vranić, Valentino; Menkyna, Radoslav; Bebjak, Michal; Dolog, Peter.

In: e-Informatica Software Engineering Journal, Vol. 3, No. 1, 2009, p. 43-58.

Research output: Contribution to journalJournal articleResearchpeer-review

TY - JOUR

T1 - Aspect-Oriented Change Realizations and Their Interaction

AU - Vranić, Valentino

AU - Menkyna, Radoslav

AU - Bebjak, Michal

AU - Dolog, Peter

PY - 2009

Y1 - 2009

N2 - With aspect-oriented programming, changes can be treated explicitly and directly at the programminglanguage level. An approach to aspect-oriented change realization based on a two-levelchange type model is presented in this paper. In this approach, aspect-oriented change realizationsare mainly based on aspect-oriented design patterns or themselves constitute pattern-like formsin connection to which domain independent change types can be identified. However, it is moreconvenient to plan changes in a domain specific manner. Domain specific change types can beseen as subtypes of generally applicable change types. These relationships can be maintained in aform of a catalog. Some changes can actually affect existing aspect-oriented change realizations,which can be solved by adapting the existing change implementation or by implementing anaspect-oriented change realization of the existing change without having to modify its sourcecode. As demonstrated partially by the approach evaluation, the problem of change interactionmay be avoided to a large extent by using appropriate aspect-oriented development tools, but fora large number of changes, dependencies between them have to be tracked. Constructing partialfeature models in which changes are represented by variable features is sufficient to discoverindirect change dependencies that may lead to change interaction.

AB - With aspect-oriented programming, changes can be treated explicitly and directly at the programminglanguage level. An approach to aspect-oriented change realization based on a two-levelchange type model is presented in this paper. In this approach, aspect-oriented change realizationsare mainly based on aspect-oriented design patterns or themselves constitute pattern-like formsin connection to which domain independent change types can be identified. However, it is moreconvenient to plan changes in a domain specific manner. Domain specific change types can beseen as subtypes of generally applicable change types. These relationships can be maintained in aform of a catalog. Some changes can actually affect existing aspect-oriented change realizations,which can be solved by adapting the existing change implementation or by implementing anaspect-oriented change realization of the existing change without having to modify its sourcecode. As demonstrated partially by the approach evaluation, the problem of change interactionmay be avoided to a large extent by using appropriate aspect-oriented development tools, but fora large number of changes, dependencies between them have to be tracked. Constructing partialfeature models in which changes are represented by variable features is sufficient to discoverindirect change dependencies that may lead to change interaction.

M3 - Journal article

VL - 3

SP - 43

EP - 58

JO - e-Informatica

JF - e-Informatica

SN - 1897-7979

IS - 1

ER -