2007
DOI: 10.1109/mic.2007.74
|View full text |Cite
|
Sign up to set email alerts
|

Understanding UI Integration: A Survey of Problems, Technologies, and Opportunities

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
100
0

Year Published

2009
2009
2017
2017

Publication Types

Select...
5
4

Relationship

1
8

Authors

Journals

citations
Cited by 131 publications
(100 citation statements)
references
References 6 publications
0
100
0
Order By: Relevance
“…One of the main contributions of mashups is the introduction of novel practices, enabling integration of available service and data at the presentation layer, in a component-based fashion -an aspect that so far has been scarcely investigated. Few papers, indeed, discuss and motivate the so-called UI-based integration [10,15,41] as a new component-based integration paradigm, which privileges the creation of fully-fledged artifacts, also equipped with UIs; this is in addition to the traditional service and data integration practices that, instead, mainly act at the logic and data layers of the application stack. In this direction, this article highlights how interactive artifacts can be composed by reusing the presentation logics (i.e., the UIs) and the execution logics of self-contained modules, the so-called Actionable UI Components, providing for the visualization of data extracted from data sources and for data manipulation operations through task-related functions.…”
Section: Resultsmentioning
confidence: 99%
“…One of the main contributions of mashups is the introduction of novel practices, enabling integration of available service and data at the presentation layer, in a component-based fashion -an aspect that so far has been scarcely investigated. Few papers, indeed, discuss and motivate the so-called UI-based integration [10,15,41] as a new component-based integration paradigm, which privileges the creation of fully-fledged artifacts, also equipped with UIs; this is in addition to the traditional service and data integration practices that, instead, mainly act at the logic and data layers of the application stack. In this direction, this article highlights how interactive artifacts can be composed by reusing the presentation logics (i.e., the UIs) and the execution logics of self-contained modules, the so-called Actionable UI Components, providing for the visualization of data extracted from data sources and for data manipulation operations through task-related functions.…”
Section: Resultsmentioning
confidence: 99%
“…In particular JOpera is focused on the integration logic layer of a mashup, and only provides limited support for building the user interface layer, where multiple widgets should be composed: in the case study, the construction of the user interface was "concentrated" within a single task of the workflow. An example of a complementary composition tool focused at the user interface layer [3] is Mixup [36].…”
Section: Discussionmentioning
confidence: 99%
“…Whereas mashups have been positioned as composition done at the userinterface layer [3], the goal of this paper is to apply the notion composition to RESTful services independently of the user interface of the resulting application. Thus, considering the recursive property of software composition 1 , we argue that composing a set of RESTful services should result in another RESTful service, which can later be consumed by the user interface of a mashup application, or also be invoked by other composite RESTful services.…”
Section: Introductionmentioning
confidence: 99%
“…Mashups can be seen as composition applied at the User Interface (UI)/Presentation layer [57], where a fully integrated UI is built out of reusable widgets applied to different data 612 sources. Mashups do not emphasize on the reusability of the composition, but only the ease with which it can be built [58].…”
Section: Restful Apis and Mashupmentioning
confidence: 99%