ABSTRACT
Human–computer interaction (HCI) and software engineering (SE) are like two old friends with different backgrounds: they share values but use them differently. 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. There are many reasons for the lack of collaboration between HCI and SE scientists and practitioners: mutual ignorance resulting from educational background, and from there, economic consideration. In SE, usability is considered an intrinsic property of the software product, whereas in HCI, usability is contextual: a system is not intrinsically usable or unusable. In value-centered approaches, software design should start from the explicit expression of an intentional creation of value for a selected set of target contexts of use. The chapter introduces the key objectives and principles of model-driven engineering (MDE) and analyzes the contributions and limitations of MDE to address the problem of user interfaces plasticity.
