Towards Method Engineering of Model-Driven User Interface Development
Model-driven user interface development environments and their associated methodologies have evolved over time to become more explicit, flexible, and reusable but they still lack to reach a level that allows tailoring a method to the reality of software d
- PDF / 458,049 Bytes
- 14 Pages / 430 x 660 pts Page_size
- 113 Downloads / 210 Views
bstract. Model-driven user interface development environments and their associated methodologies have evolved over time to become more explicit, flexible, and reusable but they still lack to reach a level that allows tailoring a method to the reality of software development organizations and their projects. In order to address this shortcoming, method engineering provides strategies to define and tailor software engineering methods. They should address any usability concerns, which are primordial for the integration of model-driven user interface development methods in the competitive reality of software organizations. To address the issues of explicitly defining a flexible method, we defined a strategy based on method engineering for model-driven user interface development that uses usability goals as a starting point. With the application of this strategy, we aim to help method engineers executing the method with more efficiency when defining or tailoring methods and facilitate the application of model-based user interface development methods in software organizations. Keywords: model-driven user interface development, methodologies, method engineering, business process modeling, usability.
1 Introduction Any development method or methodology, whether it is generic or specific for User Interface (UI) for instance, is usually decomposed into three related axes: 1. Models that capture different facets of the future interactive application. 2. An Approach which governs the actions conducted on the various models. 3. Software that supports executing the approach based on the models. On the one hand, substantive efforts have been devoted to the definition and the usage of models, and extensive development of support software has been achieved. On the other hand, the approach aspect has received less attention over the past decades. Even though, there are many User Interface Development (UID) methods that use task models as a starting point to elicit user requirements and more precisely understand user cognition in order to make UIs more usable. Such a growing interest for models is due to the need to provide a more systematic approach to UID. Professionals working in systems development usually follow a defined software development process, and when it comes to UID, many professionals do their activities M. Winckler, H. Johnson, and P. Palanque (Eds.): TAMODIA 2007, LNCS 4849, pp. 112–125, 2007. © Springer-Verlag Berlin Heidelberg 2007
Towards Method Engineering of Model-Driven User Interface Development
113
more empirically because there is still resistance to the application of usability methodologies in software organizations [26], such as resource constraints and lack of knowledge about usability are the factors that most influence professionals. But, a formal UID method requires efficiency to be integrated into software development organizations. Model-based UID comes as a solution to improve efficiency by reusing models, reducing development efforts, among other benefits [3]. To make model-based UID methods a
Data Loading...
