Experiments in Model Driven Composition of User Interfaces

Occello, Audrey; Joffroy, Cédric; Déry-Pinna, Anne-Marie

doi:10.1007/978-3-642-13645-0_8

Cited by 9 publications

(12 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, the PLACID framework [8] achieves dynamic UI service composition based on task planning, while it respects preconditions and post-conditions for all tasks. In the same vain, the Alias [16] framework considers web services that come with their UIs. Designers are responsible for composing the logical parts of the services and defining the interactions between these services and their UIs, while the Alias framework undertakes the composition of their UI parts.…”

Section: Service-oriented Architecturesmentioning

confidence: 99%

Yeti

Karuzaki

Savidis

2015

Proceedings of the 7th ACM SIGCHI Symposium on Engineering Interactive Computing Systems

View full text Add to dashboard Cite

As applications become larger, building their UI is getting harder. While a lot of research focuses on new ways of building UIs, little work focuses on reusing existing UI components to automatically compose large-scale interfaces. This paper introduces Yeti, an automatic UI composer for desktop and android applications written in Java, that adopts a task-driven discipline where task hierarchy denotes component containment and control. We propose the notion of globally unique task identifiers to avoid task naming confusions across components and repositories. To enable applications set mandatory control aspects for the retrieved UI components, we introduce required APIs as part of task definitions. Yeti emphasizes the composition of reusable coarse-grained UI components rather than automatic UI creation from scratch, so no lowerlevel specifications are deployed. Retrieved and composed components can be directly handled inside application logic via the application-defined APIs and the generic component interface required for all components. This programmingoriented approach allows UI programmers to deploy Yeti as a software library, while it enables the mix of composed UI parts with manually coded ones. To validate our system and demonstrate its deployment, we present an example application created from existing components.

show abstract

Section: Service-oriented Architecturesmentioning

confidence: 99%

Yeti

Karuzaki

Savidis

2015

Proceedings of the 7th ACM SIGCHI Symposium on Engineering Interactive Computing Systems

View full text Add to dashboard Cite

show abstract

“…describe UI in order to deal with sub-parts of former UI. The description of an UI both involves (1) description of its structure (like UIML [1], ALIAS [7], UsiXML [5] or MARIA [8]) and (2) the spatial positioning of these components (like in different layouts used in the UI toolkits).…”

Section: Related Workmentioning

confidence: 99%

“…To manipulate applications in order to compose them, there are currently three main approaches: (i) the composition could be triggered by the functional part as in [7], (ii) the composition could be triggered by the users' goals (i.e. tasks) as in [8] and (iii) the composition could be triggered by the UI as in [4].…”

Section: Related Workmentioning

confidence: 99%

OntoCompo: A Tool to Enhance Application Composition

Brel

Déry-Pinna

Renevier-Gonin

et al. 2011

Human-Computer Interaction – INTERACT 2011

Self Cite

View full text Add to dashboard Cite

Abstract. Mash-ups emerged through the web 2.0 to juxtapose several applications and use them together. The next step after juxtaposition is the composition of existing applications to build a new one. A solution of this being born need is the reuse of parts from formers applications. To perform this composition and reuse in an easy and comfortable way, we propose a tool based on several extensions of selection to help the developer during his composition.

show abstract

“…We classify works related to UI compositions according to their approach: an "X" in the Table 1 means that corresponding work explicitly takes into account this part. X X Scenarios [12] X X SOAUI [9], ALIAS [6], Transparent Interface [13] X X…”

Section: Related Workmentioning

confidence: 99%

“…The SOAUI approach [9] derives web service composition into UI composition, by searching the best-fitting UI in a repository for each service and then UI composition. The aim of [6] is to deduce the UI composition from the FC composition.…”

Section: Related Workmentioning

confidence: 99%

Application Composition Driven by UI Composition

Brel

Renevier-Gonin

Occello

et al. 2010

Human-Centred Software Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. Ahead of the multiplication of specialized applications, needs for application composition increase. Each application can be described by a pair of a visible part -the User Interface (UI) -and a hidden part -the tasks and the Functional Core (FC). Few works address the problem of application composition by handling both visible and hidden parts at the same time. Our proposition described in this paper is to start from the visible parts of applications, their UIs, to build a new application while using information coming from UIs as well as from tasks. We base upon the semantic description of UIs to help the developer merge parts of former applications. We argue that this approach driven by the composition of UIs helps the user during the composition process and ensures the preservation of a usable UI for the resulting application.

show abstract

Experiments in Model Driven Composition of User Interfaces

Cited by 9 publications

References 13 publications

Yeti

Yeti

OntoCompo: A Tool to Enhance Application Composition

Application Composition Driven by UI Composition

Contact Info

Product

Resources

About