2006
DOI: 10.1007/11752707_14
|View full text |Cite
|
Sign up to set email alerts
|

Solving the Mapping Problem in User Interface Design by Seamless Integration in IdealXML

Abstract: Abstract. The mapping problem has been defined as the way to map models involved throughout the development life cycle of user interfaces. Model-based design of user interfaces has followed a long tradition of establishing models and maintaining mappings between them. This paper introduces a formal definition of potential mappings between models with its corresponding syntax so as to create a uniform and integrated framework for adding, removing, and modifying mappings throughout the development life cycle. Fo… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
11
0
1

Year Published

2006
2006
2019
2019

Publication Types

Select...
4
4
1

Relationship

3
6

Authors

Journals

citations
Cited by 26 publications
(12 citation statements)
references
References 26 publications
0
11
0
1
Order By: Relevance
“…This multilevel approach is quite new. Existing model-based tools which generate several UI versions for multiple platforms adopt a totally different approach: either they generate code starting from a description at the tasks and concepts level [9] (which offers little or no control over the layout and structure of the final interface), or they require a distinct CUI to be specified for each target platform or for each family of target platforms [1] (which demands more work from the designer and offers no guarantee of consistency between the different UI versions). In contrast, our approach requires only one specification, which can be given at any level of detail desired while taking advantage of the information specified at higher levels of abstraction if this is available.…”
Section: Discussionmentioning
confidence: 99%
“…This multilevel approach is quite new. Existing model-based tools which generate several UI versions for multiple platforms adopt a totally different approach: either they generate code starting from a description at the tasks and concepts level [9] (which offers little or no control over the layout and structure of the final interface), or they require a distinct CUI to be specified for each target platform or for each family of target platforms [1] (which demands more work from the designer and offers no guarantee of consistency between the different UI versions). In contrast, our approach requires only one specification, which can be given at any level of detail desired while taking advantage of the information specified at higher levels of abstraction if this is available.…”
Section: Discussionmentioning
confidence: 99%
“…(7) hybrid approach. (8) other approaches: there are other approaches, such as XSLT [15], that doesn't fall in any of the previous categories, but they are also commonly used in model transformation.…”
Section: Designing User Interface Adaptationmentioning
confidence: 99%
“…Our proposal is to add Awareness Requirements (AR) to a task (Fig. 2c) by using mappings [7]. An AR is the representation of an awareness information requirement for a specific case or context (RC) which accesses a selected group of instances from the awareness data source (awDataSource, awSet).…”
Section: Awareness Requirement Representationmentioning
confidence: 99%