A service-oriented application creation process in ubiquitous environments

Abstract

Purpose Many features constitute an adaptive system such as user model, interface specification, business functionalities and service implementation. Context awareness is an important facet of service oriented application creation dealing with the gathering, use and representation of context information. Generally, user interfaces and services communities work separately on the adaptation process and do not converge. The aim of this work is to manage the system’s functionalities and the user interface that delivers data to the relevant consumer early since the design phase until the code generation. Design/methodology/approach The authors discuss how a unified method based on a model-driven architecture for adaptive user interface and pervasive service creation eases the work of designers and developers, limits incompatibility issues and supports dynamic generation of systems adapted to different contexts of use. Findings The proposed approach is able to support a semi-automatic ubiquitous application generation with service, behavior, presentation and content adaptation. Originality/value In this paper, the authors tackle context-awareness at two levels: system functionalities and user interface generation. The authors also tackle adaptation at the specification and implementation levels.

Learning from appropriation practices

“…Hence, the initial design forms the basis for the appropriation process, which in turn forms the basis for opportunities for redesign. This process eases the work of designers and developers, limits frustration and supports dynamic generation of e-participation environments adapted to various contexts of use (Taktak and Moussa, 2017).…”

Factors Affecting the Choice of Usability Evaluation Methods for Interactive Adaptive Systems

“…Furthermore, the system can be adapted based on the device on which it is displayed (i.e., desktop, Smartphone). Many adaptive systems of this type have been studied and proposed in the literature over the last decades [20,21].…”

Task scheduling mechanisms in cloud computing: A systematic review

“…Waiting time: It can be said the time between the execution start time and the submission time of the task. Reducing the waiting time can be considered to be an optimizing criterion for cloud task scheduling …”

“…Reducing the waiting time can be considered to be an optimizing criterion for cloud task scheduling. 18 Deadline: Deadline can be defined as the time before which a task should complete its execution, and the most optimized schedule will be when the most numbers of tasks finish before their given deadline. Figure 4 illustrates a classification of the task scheduling approaches in the cloud environment.…”