International audienceReusing and composing pieces of software is a common practice in software engineering. However, reusing the user interfaces that come with software systems is still an ongoing work. The Alias framework helps developers to reuse and compose user interfaces according to the way they are composing new systems from smaller units as a mean of speeding up the design process. In this paper we describe how we rely on Model Driven Engineering to operationalize our composition process

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.

No abstract

No abstract

International audienceWith the adoption of MDE, application evolution is facilitated. Instead of modifying each deployed version, the application is modified only once at the model level and then regenerated for each platform. On the other hand, to manage application complexity, models are partitioned and then integrated together to form larger ones. However most of modeling approaches use an integration mechanism based on merging existing models that makes it difficult to manage application evolution in a modular and incremental way. As an alternative, we propose the Collaborative Component Based Model approach (CCBM) that leverages software components principles and focuses on the specification of how models collaborate with each other. This paper presents how the proposed approach contributes to integrate and manage change of models incrementally by preserving defined collaborations during the whole life-cycle of an application, from initial, very loosely specified interactions, through step-wise refinements, to the final concretization to a component implementation