Tasks Models Merging for High-Level Component Composition

Lewandowski, Arnaud; Lepreux, Sophie; Bourguin, Grégory

doi:10.1007/978-3-540-73105-4_123

Cited by 8 publications

(4 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Model composition is not in the focus of this paper, but it is discussed by many authors in MBD (e.g. [10]). Figure 5 indicates the coupling at the task and domain level that is used in our case study.…”

Section: Coupling Of Core Ui and Extra-uimentioning

confidence: 99%

What can model-based UI design offer to end-user software engineering?

Dittmar

Frey

Dupuy-Chessa

2012

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

View full text Add to dashboard Cite

End-User Programming enables end users to create their own programs. This can be accomplished in different ways, where one of them is by appropriation or reconfiguration of existing software. However, there is a trade-off between end users' 'situated design' and quality design which is addressed in End-User Software Engineering. This paper investigates how methods and techniques from Model-Based UI Design can contribute to End-User Software Engineering. Applying the concept of Extra-UI, the paper describes a Model-Based approach that allows to extend core applications in a way that some of the underlying models and assumptions become manipulable by end users. The approach is discussed through a running example.

show abstract

Section: Coupling Of Core Ui and Extra-uimentioning

confidence: 99%

What can model-based UI design offer to end-user software engineering?

Dittmar

Frey

Dupuy-Chessa

2012

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

View full text Add to dashboard Cite

show abstract

“…Models composition is discussed by many authors in MDE (e.g. by Lewandowski et al (2007)). Its details are not the focus of this paper, but we briefly discuss some advantages and disadvantages of weaving the help UI with the application UI at different levels of abstraction (see figure 3).…”

Section: Weaving the Uismentioning

confidence: 99%

Users need your models! Exploiting Design Models for Explanations

Frey¹,

Calvary

Dupuy-Chessa

2012

Electronic Workshops in Computing

View full text Add to dashboard Cite

End users can ask themselves about the User Interface (UI). Questions arise because users are not designers so both designers and users, have different perceptions of the same UI. Help Systems have naturally emerged to tackle this problem. Most of these Help Systems are predefined, so at design time designers need to anticipate the problems users may find at runtime, which limits the scope of the support. This paper explores Model-Driven Engineering to overcome this limitation: models created at design time are exploited at runtime for providing end users with explanations. Based on Norman's Theory of Action this paper introduces the Gulf of Quality as the distance between the models the designer creates at design time and the mental models the end user elaborates. This concept sets the basis of a Model-Driven method and a supporting architecture for computing explanations for the end user. The method deals uniformly with the UI of the help system and the UI of the application. They can be weaved or not, depending on the model transformations the designer selects. A software architecture is devised and implemented in a running IDE. The feasibility of the approach is shown through two use cases.

show abstract

“…• Works only considering UI composition, either for defining specific toolkit for adaptive UI [9], either based on abstract definition of UI [8,3] or either adopting end-user programming [11], • Works only considering TM composition (composition of two task trees [4]), • Works deriving Tasks in FC composition and later in UI composition, because of generation UI from service annotation [7] or thanks to specific adaptable couple FC-UI [2] or deriving Tasks in UI [12] • And Works considering both FC and UI composition. The main goal in [13] is to maintain a stable UI for using a composition of volatile service.…”

Section: Related Workmentioning

confidence: 99%

Application Composition Driven by UI Composition

Brel

Renevier-Gonin

Occello

et al. 2010

Human-Centred Software Engineering

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

Tasks Models Merging for High-Level Component Composition

Cited by 8 publications

References 5 publications

What can model-based UI design offer to end-user software engineering?

What can model-based UI design offer to end-user software engineering?

Users need your models! Exploiting Design Models for Explanations

Application Composition Driven by UI Composition

Contact Info

Product

Resources

About