ABSTRACT

Model-Driven Engineering . . . . . . . . . . . . . . . . . . . . . 1114

Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116

Metamodel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116

Transformations and Mappings . . . . . . . . . . . . . . . . . 1117

MDE for Plastic User Interfaces . . . . . . . . . . . . . . . . 1117

Functional Decomposition for

Plastic Interactive Systems . . . . . . . . . . . . . . . . . . . . . 1118

Models for UI Plasticity . . . . . . . . . . . . . . . . . . . . . . . . 1119

M2-tasks and M2-concepts . . . . . . . . . . . . . . . . . . 1120

M2-Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121

The Models in Action . . . . . . . . . . . . . . . . . . . . . . . . . 1121

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123

Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124

References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124

Human-computer interaction (HCI) and Software Engineering (SE) are like two old friends with different backgrounds: they share values but use them differently. Both domains address the design and development of useful and usable systems and are concerned with “requirements analysis,” “incremental and iterative design,” as well as “quality assurance.” However, they address these problems with different development processes, different notations, and different priorities. For HCI, the human is the first-class entity in all phases of development. For SE, the final objective is a running system developed at minimal cost and delivered in time, while satisfying contractual specifications. The user is, at best, involved at the very beginning of the process, and hopefully at the very end of the project for summative evaluation. However, to avoid or correct wrong design decisions, this is too little and too late. Even in the early stages of development, functional requirements and quality goals are rarely the result of a close collaboration between HCI and SE specialists.