Multi-paradigm design with feature modeling

Abstract

In this article, a method for selecting paradigms, viewed as solution domain concepts, appropriate for given application domain concepts is proposed. In this method, denoted as multi-paradigm design with feature modeling, both application and solution domain are modeled using feature modeling. The selection of paradigms is performed in the process of feature modeling based transformational analysis as a paradigm instantiation over application domain concepts. The output of transformational analysis is a set of paradigm instances annotated with the information about the corresponding application domain concepts and features. According to these paradigm instances, the code skeleton is being designed. The approach is presented in conjunction with its specialization to AspectJ programming language. Transformational analysis performed according to the AspectJ paradigm model enables an early aspect identification.

Aspect-Oriented Change Realization Based on Multi-Paradigm Design with Feature Modeling

“…Such paradigms are being denoted as small-scale to distinguish them from the common concept of the (largescale) paradigm as a particular approach to programming (like object-oriented or procedural programming) [3].…”

“…This is modeled by optional features Inter-Type Declarations, Advices, and Pointcuts (indicated by empty circle ended edges). These features represent references to equally named auxiliary concepts that represent plural forms of respective concepts that actually represent paradigms in their own right (and their own feature models [3]). To achieve its intent, an aspect may -similarly to a class -employ Methods (with the method being yet another paradigm) and Fields.…”

“…To postpone change realization and develop a whole catalog may be unacceptable with respect to time and effort needed. The problem of selecting a suitable realizing change type resembles paradigm selection in multi-paradigm design [3]. This other way around -to treat change realization types as paradigms and employ multi-paradigm design to select the appropriate one -is the topic of this paper.…”

Developing Applications with Aspect-Oriented Change Realization

“…This is related to change interaction which is exhibited as dependencies between changes. A simplified view of change dependencies is that a change may require another change or two changes may be mutually exclusive, but the dependencies between changes could be as complex as feature dependencies in feature modeling and accordingly represented by feature diagrams and additional constraints expressed as logical expressions [22] (which can be partly embedded into feature diagrams by allowing them to be directed acyclic graphs instead of just trees [8]). …”

“…An example of this are features that belong to the same change request. Again, feature modeling can be used to model such dependencies with so-called default dependency rules that may also be represented by logical expressions [22].…”