Productivity Evaluation of Self-Adaptive Software Model Driven Architecture

Productivity Evaluation of Self-Adaptive Software Model Driven Architecture

Basel Magableh (Trinity College Dublin, Ireland) and Stephen Barrett (Trinity College Dublin, Ireland)
DOI: 10.4018/jitwe.2011100101
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

Anticipating context changes using a model-based approach requires a formal procedure for analysing and modelling context-dependent functionality and stable description of the architecture which supports dynamic decision-making and architecture evolution. This article demonstrates the capabilities of the context-oriented component-based application-model-driven architecture (COCA-MDA) to support the development of self-adaptive applications; the authors describe a state-of-the-art case study and evaluate the development effort involved in adopting the COCA-MDA in constructing the application. An intensive analysis of the application requirements simplified the process of modelling the application’s behavioural model; therefore, instead of modelling several variation models, the developers modelled an extra-functionality model. COCA-MDA reduces the development effort because it maintains a clear separation of concerns and employs a decomposition mechanism to produce a context-oriented component model which decouples the applications’ core functionality from the context-dependent functionality. Estimating the MDA approach’s productivity can help the software developers select the best MDA-based methodology from the available solutions. Thus, counting the source line of code is not adequate for evaluating the development effort of the MDA-based methodology. Quantifying the maintenance adjustment factor of the new, adapted, and reused code is a better estimate of the development effort of the MDA approaches.
Article Preview

In the literature, there are several MDA approaches which target the development of self-adaptive applications for mobile computing environments which produce component-based applications; this study borrows from the following methodologies: MUSIC, proposed by Wagner, Reichle, Khan, and Geihs (2011); U-MUSIC (Khan, 2010); and Paspallis MDA (Paspallis, 2009).

The MUSIC development methodology (Wagner et al., 2011) adopts a model-driven approach to constructing the application variability model. The applications are built as a component framework with component types as variation points. Middleware is used to resolve the variation points, which involves the election of a concrete component as a realization of the component type. Using this method, a number of application variants can automatically be derived.

Complete Article List

Search this Journal:
Reset
Open Access Articles: Forthcoming
Volume 13: 4 Issues (2018): 1 Released, 3 Forthcoming
Volume 12: 4 Issues (2017)
Volume 11: 4 Issues (2016)
Volume 10: 4 Issues (2015)
Volume 9: 4 Issues (2014)
Volume 8: 4 Issues (2013)
Volume 7: 4 Issues (2012)
Volume 6: 4 Issues (2011)
Volume 5: 4 Issues (2010)
Volume 4: 4 Issues (2009)
Volume 3: 4 Issues (2008)
Volume 2: 4 Issues (2007)
Volume 1: 4 Issues (2006)
View Complete Journal Contents Listing