Model-Driven Development
dc.contributor.author | Pastor, Oscar | |
dc.contributor.author | España, Sergio | |
dc.contributor.author | Panach, José Ignacio | |
dc.contributor.author | Aquino, Nathalie | |
dc.date.accessioned | 2018-01-05T19:53:19Z | |
dc.date.available | 2018-01-05T19:53:19Z | |
dc.date.issued | 2008 | |
dc.description.abstract | The model-driven architecture (MDA) paradigm is well-known and widely used in the field of model-based software development. However, there are still some issues that are problematic and that need to be dealt with carefully. In this paper we present a metaphor that explains how MDA grows in complexity as problems faced become more difficult or “wicked”, and how a method designed to be powerful, flexible and MDA-compliant can eventually become, in effect, a “jigsaw puzzle”. This jigsaw puzzle is not merely the result of having a collection of methodological “pieces” with routes across them, but also arises as a result of the criteria underlying the MDA abstraction layers. We compare MDA to other research fields such as human-computer interaction, model management and method engineering, and we use as an example the OO-Method, a software development method based on MDA-compliant model transformations. We focus on a methodological piece that is conceived to allow the specification of interaction requirements by means of interface sketches. These sketches are supported by a task model that serves as a sound basis for formalisation and allows the application of model transformation in order to obtain subsequent models. A case study illustrates the requirements capture method together with the software development process defined by the OO-Method. The whole process presented in the case study represents one of the possible routes that can be followed when developing a software system with the OO-Method. | |
dc.identifier.pissn | 1432-122X | |
dc.identifier.uri | https://dl.gi.de/handle/20.500.12116/9748 | |
dc.publisher | Springer-Verlag | |
dc.relation.ispartof | Informatik-Spektrum: Vol. 31, No. 5 | |
dc.relation.ispartofseries | Informatik-Spektrum | |
dc.title | Model-Driven Development | |
dc.type | Text/Journal Article | |
gi.citation.endPage | 407 | |
gi.citation.publisherPlace | Berlin Heidelberg | |
gi.citation.startPage | 394 |