A Toolkit of Mechanism and Context Independent Widgets

Crease, Murray; Gray, Peter J.; Brewster, Stephen

doi:10.1007/3-540-44675-3_8

Cited by 10 publications

(10 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We note that most of these works focus on the software architecture modeling. Based on the identification of two levels of abstraction (AIOs and CIOs) [33], they propose conceptual and implementational frameworks for supporting adaptation [22] [20] [10]. But adaptation is limited to the presentation level [20] [10].…”

Section: Comets and The State Of The Artmentioning

confidence: 99%

See 1 more Smart Citation

Towards a New Generation of Widgets for Supporting Software Plasticity: The ”Comet”

Calvary

Coutaz

Dâassi

et al. 2005

Engineering Human Computer Interaction and Interactive Systems

View full text Add to dashboard Cite

Abstract. This paper addresses software adaptation to context of use. It goes one step further than our early work on plasticity [5]. Here, we propose a revision of the notion of software plasticity that we apply at the widget level in terms of comets. Plasticity is defined as the ability of an interactive system to withstand variations of context of use while preserving quality in use where quality in use refers to the ISO definition. Plasticity is not limited to the UI components of an interactive system, nor to a single platform: adaptation to context of use may also impact the functional core, it may have an effect on the nature of the connectors, and it may draw upon the existence of multiple platforms in the vicinity to migrate all or portions of the interactive system. A new reference framework that structures the development process of plastic interactive systems is presented to cover these issues. The framework is then applied at the granularity of widgets to provide the notion of a comet. A comet is an introspective widget that is able to self-adapt to some context of use, or that can be adapted by a tier-component to the context of use, or that can be dynamically discarded (versus recruited) when it is unable (versus able) to cover the current context of use. To do so, a comet publishes the quality in use it guarantees, the user tasks and the domain concepts that it is able to support, as well as the extent to which it supports adaptation.

show abstract

Section: Comets and The State Of The Artmentioning

confidence: 99%

“…We keep in mind the issue of legacy systems [20] and the need for integrating multimodality as a means for adaptation [10].…”

Section: Comets and The State Of The Artmentioning

confidence: 99%

Towards a New Generation of Widgets for Supporting Software Plasticity: The ”Comet”

Calvary

Coutaz

Dâassi

et al. 2005

Engineering Human Computer Interaction and Interactive Systems

View full text Add to dashboard Cite

show abstract

“…The AUI approach is similar to research that separates the interactor portion of a user interface into abstract and concrete components [6]. With such separation, different concrete input and output mechanisms can be used depending on user preferences, available resources or the context of the interactor.…”

Section: The Aui Modelmentioning

confidence: 99%

Abstract User Interfaces: A Model and Notation to Support Plasticity in Interactive Systems

Schneider

Cordy

2001

Interactive Systems: Design, Specification, and Verification

View full text Add to dashboard Cite

Abstract. This paper introduces the Abstract User Interface (AUI) model and notation for specifying abstract interaction in interactive software systems with graphical, direct manipulation user interfaces. The AUI model is aimed at improving the plasticity of an interactive system. An interactive system is considered to be plastic when it is easily adaptable to concrete user interface styles. To support plasticity, an AUI specification defines the interaction between input, output and computation in terms of the abstract elements of the user interface: a relation we refer to as abstract interaction. Concrete characteristics of the user interface, such as events, callbacks and rendering, are deliberately factored out so that the abstract interaction relation can be exposed. Clearly defining the abstract interaction ensures that consistent interaction semantics is maintained independent of changes to the concrete user interface. To demonstrate the AUI concept, a range of user interface styles are presented for a single AUI specification of a drawing tool, and examples of commercial applications are presented.

show abstract

“…By context of use [2], we hereby refer to the combination C of a user U working with a platform P in a given physical environment E: C = <U,P,E>. Although the adaptation in general and the plasticity in particular both consider the three aspects of this context definition, it is noteworthy to observe that the P aspect is the most frequently and extensively researched area (among them are [3], [4], [6], [8], [9], [11], [14][15][16][17][18], [20]): the platform is probably the facet which affects the UI the most immediately and concretely. This is challenging since a UI which was designed for a given platform in mind may no longer fit another one with extended or reduced interaction capabilities if they were not considered before.…”

Section: Introductionmentioning

confidence: 99%

“…The ModelBased UI Development (MB-UIDE) community typically addresses the former aspect by context modeling [2], [4], [14], [17], [20] enriching task and system modeling [6], [15], whereas for the latter, the problem is often characterized as a mapping problem between the models [3], [10], [12], [19]. Thanks to the combination of context modeling and a technique for solving the mapping problem, it is possible to adapt the UI presentation, dialog and/or deployment after a context of use variation [13].…”

Section: Introductionmentioning

confidence: 99%

The Comets Inspector: Towards Run Time Plasticity Control Based on a Semantic Network

Demeure

Calvary

Coutaz

et al.

Task Models and Diagrams for Users Interface Design

View full text Add to dashboard Cite

Abstract. In this paper, we describe the COMETs Inspector, a software tool providing user interface designers and developers with a semantic network in order to control the plasticity of their User Interfaces (UI) at run-time. Thanks to a set of predefined relationships, the semantic network links together various concepts ranging from the final UI (i.e., the UI described in terms of technological spaces) to the concrete and abstract UIs (i.e., the UI respectively described in terms of concrete interaction objects independently of any technological space, and abstract individual components and containers independently of any interaction modality) up to the tasks and concepts of the interactive system. In this way, plasticity can be addressed at four levels of abstraction (task and concepts, abstract, concrete, and final user interface) for forward, reverse, and lateral engineering. The end user exploits the semantic network at run time to adapt his/her UI to another context of use by identifying, selecting, and applying plasticity suitable operations.

show abstract

A Toolkit of Mechanism and Context Independent Widgets

Cited by 10 publications

References 16 publications

Towards a New Generation of Widgets for Supporting Software Plasticity: The ”Comet”

Towards a New Generation of Widgets for Supporting Software Plasticity: The ”Comet”

Abstract User Interfaces: A Model and Notation to Support Plasticity in Interactive Systems

The Comets Inspector: Towards Run Time Plasticity Control Based on a Semantic Network

Contact Info

Product

Resources

About