Model-Driven Development for End-Users, too!?

iary models in order to bridge the semantic gap between high-level, abstract user requirements and low-level, concrete programs and to support a stepwise refinement process. This development is supported by agreeing on a standardized unified modelling language (UML). In order to cope with different application domains, the UML provides also standardized means (termed stereotypes) to customize the language, ending up with domain-specific (modelling) languages (DSL). The UML is strong in modelling the internal functionality of a software system, but weak in modelling user interface aspects of a system. Thus, with respect to the well-known MVC (Model-View-Controller) pattern, the UML supports the Model aspect, while neglecting the View and Controller aspect. While the model and functionality aspect is of high interest for a software developer, the view and model aspects are of particular interest for end users. Thus, any support for end users in customizing or even changing a software sys...

• Type: Conference
• Year: 2007
• Where: DAGSTUHL
• Authors: Gregor Engels
• Keywords: DAGSTUHL 2007, End Users, Software Engineering, User Interface Aspects, User Interfaces