Context-awareness and model driven engineering: Illustration by an E-commerce application scenario

Taconet, Chantal; Kazi-Aoul, Zakia

doi:10.1109/icdim.2008.4746829

Cited by 9 publications

(4 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…-The hardware: which is all platforms specific technical aspects including all the interaction possibilities, screen size, memory, etc. [98,90,14,91]. -Software: which is the set of applications installed on the platform including an operating system, virtual machine,.…”

Section: Context Modelingmentioning

confidence: 99%

See 1 more Smart Citation

Assessing the quality of mobile graphical user interfaces using multi-objective optimization

et al. 2019

View full text Add to dashboard Cite

Aesthetic defects are a violation of quality attributes that are symptoms of bad interface design programming decisions. They lead to deteriorating the perceived usability of mobile user interfaces and negatively impact the Users eXperience (UX) with the mobile app. Most existing studies relied on a subjective evaluation of aesthetic defects depending on end-users feedback, which makes the manual evaluation of mobile user interfaces human-centric, time-consuming, and error-prone. Therefore, recent studies have dedicated their effort to focus on the definition of mathematical formulas that each targets a specific structural quality of the interface. As the UX is tightly dependent on the user profile, the combination and calibration of quality attributes, formulas, and users characteristics, when defining a defect, is not straightforward. In this context, we propose a fully automated framework which combines literature quality attributes with the users profile to identify aesthetic defects of MUI. More precisely, we consider the mobile user interface evaluation as a multi-objective optimization problem where the goal is to maximize the number of detected violations while minimizing the detection complexity of detection rules and enhancing the interfaces overall quality in means

show abstract

Section: Context Modelingmentioning

confidence: 99%

“…-Software: which is the set of applications installed on the platform including an operating system, virtual machine,. [81,90,75].…”

Section: Context Modelingmentioning

confidence: 99%

Assessing the quality of mobile graphical user interfaces using multi-objective optimization

et al. 2019

View full text Add to dashboard Cite

show abstract

“…It produces two kinds of artefacts: implementations and models. The presentation of this modelling task is out of the scope of the paper and can be found in [26]. Of course, the APIs of the collectors vary and this task should benet from standardisation actions.…”

Section: Design Overviewmentioning

confidence: 99%

“…The type of the observables necessary to compute an interpreted observable is provided by the observable meta-model, not described in this paper (see [26]).…”

Section: Ca3m Context-awareness Meta-modelmentioning

confidence: 99%

CA3M: A Runtime Model and a Middleware for Dynamic Context Management

Taconet

Kazi-Aoul

Zaier

et al. 2009

On the Move to Meaningful Internet Systems: OTM 2009

Self Cite

View full text Add to dashboard Cite

In ubiquitous environments, context-aware applications need to monitor their execution context. They use middleware services such as context managers for this purpose. The space of monitorable entities is huge and each context-aware application has specic monitoring requirements which can change at runtime as a result of new opportunities or constraints due to context variations. The issues dealt with in this paper are 1) to guide context-aware application designers in the specication of the monitoring of distributed context sources, and 2) to allow the adaptation of context management capabilities by dynamically taking into account new context data collectors not foreseen during the development process. The solution we present, CA3M, follows the model-driven engineering approach for answering the previous questions: 1) designers specialised into context management specify context-awareness concerns into models that conform to a context-awareness meta-model, and 2) these context-awareness models are present at runtime and may be updated to cater with new application requirements. This paper presents the whole chain from the context-awareness model denition to the dynamic instantiation of context data collectors following modications of context-awareness models at runtime.

show abstract