Model-Driven Development
Model-Driven Development
复制标题
DOI：
10.1007/s00287-008-0275-8
复制
发表时间：
2008-08
影响因子：
--
通讯作者：
Ó. Pastor;Sergio España;José Ignacio Panach;Nathalie Aquino
中科院分区：
文献类型：
--
作者：
Ó. Pastor;Sergio España;José Ignacio Panach;Nathalie Aquino
模型驱动体系结构（MDA）范式在基于模型的软件开发领域是众所周知的，并被广泛使用。但是，仍然有一些问题是有问题的，需要认真处理。在本文中，我们提出了一个比喻，解释了MDA如何增长的复杂性所面临的问题变得更加困难或“邪恶”，以及如何设计的方法是强大的，灵活的和MDA兼容的最终可以成为，实际上，一个“拼图”。这个拼图游戏不仅仅是有一系列方法学“块”的结果，这些块之间有路由，而且也是MDA抽象层下面的标准的结果。我们比较MDA的其他研究领域，如人机交互，模型管理和方法工程，我们作为一个例子，OO方法，一种软件开发方法的基础上MDA兼容的模型转换。我们专注于一种方法，它被认为是允许通过接口草图的交互需求的规范。这些草图是由一个任务模型，作为一个健全的基础，形式化，并允许应用程序的模型转换，以获得后续模型的支持。案例研究说明了需求捕获方法与OO方法定义的软件开发过程。案例研究中提出的整个过程代表了用OO方法开发软件系统时可以遵循的可能路线之一。
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.