Context-oriented Software Development

Abstract

<span style="font-family: Times New Roman; font-size: small;"> </span><p style="margin: 0cm 0cm 0pt; layout-grid-mode: char;" class="Abstract"><span style="color: black; font-weight: normal;"><span style="font-size: x-small;"><span style="font-family: Times New Roman;">Context-oriented programming is an emerging technique that enables dynamic behaviour variation based on context changes. In COP, context can be handled directly at the code level by enriching the business logic of the application with code fragments responsible for performing context manipulation, thus providing the application code with the required adaptive behavior. Unfortunately, the whole set of sensors, effectors, and adaptation processes is mixed with the application code, which often leads to poor scalability and maintainability. In addition, the developers have to surround all probable behavior inside the source code. As an outcome, the anticipated adjustment is restricted to the amount of code stubs on hand offered by the creators. Context-driven adaptation requires dynamic composition of context-dependent parts. This can be achieved trough the support of a component model that encapsulates the context-dependent functionality and decouples them from the application&rsquo;s core-functionality. The complexity behind modeling the context-dependent functionality lies in the fact that they can occur separately or in any combination, and cannot be encapsulated because of their impact across all the software modules. Before encapsulating crosscutting context-dependent functionality into a software module, the developers must first identify them in the requirements documents. This requires a formal development paradigm for analyzing the context-dependent functionality; and a component model, which modularizes their concerns. COCA-MDA is proposed in this article as model driven architecture for constructing self-adaptive application from a context oriented component model. </span></span></span></p><span style="font-family: Times New Roman; font-size: small;"> </span

A Framework for Evaluating Model-driven Architecture

“…Such composition requires the design of software modules to be more oriented towards the context information rather than being oriented towards the functionality. The principle of context orientation of software modules was proposed in the COCA-MDA [31]. COCA-MDA proposes a decomposition mechanism of software based on the separation between context-dependent and context-independent functionality.…”

Detecting the Onset of Dementia Using Context-Oriented Architecture

“…The Context-Oriented Component-based Architecture, and the development methodology were described in [4], [14]. This article focuses on the validation and evaluation of the context-oriented software.…”

“…To achieve this target, Context Oriented Software Development (COSD) was proposed as a generic development methodology, which facilitates the development of self-adaptive context-oriented software. The COSD integrates a model-driven architecture approach (Context-Oriented Component-based Applications Model-Driven Architecture (COCA-MDA)) [4] with a behavioural decomposition strategy, based on the observation of context information in requirements analysis and modelling phase. As a result of combining a decomposition strategy with COCA-MDA, a set of behavioural units is produced.…”

“…Aspect Oriented Software Development (AOSD) [5] and COSD [4] are the alternatives for the design and construction of self-adaptive software. Their ultimate goal is to support the adaptability and variability of software systems, and to be able to reduce development cost and effort, while improving the software modularity and complexity.…”

“…Their ultimate goal is to support the adaptability and variability of software systems, and to be able to reduce development cost and effort, while improving the software modularity and complexity. This motivates us to evaluate these technologies with respect to their ability to support software adaptability (modifiability) and the performance gain from using these technologies to implement the case study application in a mobile computing environment [4].…”