MDD Approach for the Development of Context-Aware Applications

Abstract

Context-aware systems offer entirely new opportunities for application developers and for end users by gathering context information and adapting systems behavior accordingly. Several context models have been defined and various context-aware middleware has been developed in order to simplify the development of context-aware applications. Unfortunately, the development of an application by using these middleware products introduces several technical details in the application. These technical details are specific to a given middleware and reduce the possibility of reusing the application on other middleware. In this paper, we propose an MDD (Model Driven Development) approach that makes it possible to design context-aware applications independently of the platform. This approach is based on several phases that approach step by step the context platform and allow designers to automatically map their models to several platforms through the definition of automatic and modular transformations. To be able to apply this approach we define a new UML profile for context-aware applications, that we use to explore our approach.

A Model to Design and Verify Context-Aware Adaptive Service Composition

“…For instance, the first state in S could be identified by the vector (1, 1, 1), the second state by the vector (1, 1, 0), and so on. Correspondingly, the first state is encoded by the Boolean formula s 1 ∧s 2 ∧s 3 , the second state by s 1 ∧s 2 ∧¬s 3 (notice the last negation), and so on 2 . Sets of states are encoded by Boolean formulae as well, by taking the disjunction of the Boolean formulae encoding each state in the set.…”

“…Determinism: Algorithm 2 computes the set of conditions (in the form of a BDD) that enable transitions to more than a destination state (notice: in our encoding we assume that the message name has been encoded in the condition 2 By slight abuse of notation, the same symbols s i (i ∈ {1, . .…”

“…They evaluate its performance without considering possible un-modeled situations. A model-driven approach to model a contextual and variable process of an application structure, as well as its behaviour and its architecture, is defined by Ayed et al [2]. They have evaluated their approach only by implementing the UML profile, but not using verification techniques.…”

Formal modelling, knowledge representation and reasoning for design and development of user-centric pervasive software: a meta-review

“…Hence, an amalgamation of MDD and ontologies has been envisaged, argued for a limited problem space, and presumed to be promising in Katasonov and Palviainen (2010), Knublauch (2004), Parreiras and Staab (2010), Valiente (2010). On the one hand, in the software engineering domain, automated development of complex software products from higher abstract models has gained great momentum (Ayed et al, 2007), and considerable expertise along with a mature tool portfolio has been constructed, particularly with the emergence of MDD. On the other hand, ontologies as KR and logic paradigm have been utilised as run-time and development time software artefacts due to the their higher level of expressivity, formal semantics, and reasoning and inference capabilities.…”

A Novel Context Ontology to Facilitate Interoperation of Semantic Services in Environments with Wearable Devices

“…Some of the most important examples are: object oriented models [10]; key-value models [11]; graphical models [12][13][14]; etc. However, several studies [6] [ [15][16] state that the use of ontologies to model context is one of the best choices.…”