8
Atkinson a MDD (Model Driven Development) supporting infrastructure must define: 1. The concepts available for creating models and the rules governing their use 2. The notation to use in depicting models 3. How the models elements represent realworld elements, including software artifacts 4. Concepts to facilitate dynamic user extensions to model concepts, model notation,and the models created from them 5. Concepts to facilitate the interchange of model concepts and notation, and the models created from them 6. Concepts to facilitate user-defined mappings from models to other artifacts, including code MDD, no MDA 1. Metamodelos 2. Sintaxis concreta 3. Transformaciones

9
Mellor a set of OMG standards that enables the specification of models and their transformation into other models and complete systems. MDA = estándares para MDD Pueden haber otras técnicas para MDD

10
Bichler el objetivo de MDA es to define a standardized approach to software development based on models. Each phase within a software development process generates additional informations which need to be added to the model by a suitable transformation. These transformations should be supported by tools in order to facilitate process execution and increase the accuracy of the transformations. Aproximación estándar para MDD

11
Selic MDDs defining characteristic is that software developments primary focus and products are models rather than computer programs. En el mismo trabajo destaca que if models end up merely as documentation, they are of limited value, because documentation all too easily diverges from reality. Consequently, a key premise behind MDD (Model Driven Development) is that programs are automatically generated from their corresponding models. MDD, no MDA Es imprescindible la generación automática

12
Agrawal MDA propone que en el proceso de desarrollo de software models are created for capturing not only requirements, but also designs and implementations. The models are not merely artifacts of documentation, but living documents that are transformed into implementations. Con MDA los modelos no son sólo documentación, capturan: Requisitos Diseño Implementación

13
Czarnecki define MDA como an initiative by the Object Management Group (OMG) to define an approach to software development based on modeling and automated mapping of models to implementations. The basic MDA pattern involves defining a platform independent model (PIM) and its automated mapping to one or more platform- specific models (PSMs). La transformación debe ser automática 1 PIM -> 1..n PSM

14
Gardner la principal diferencia de MDA con el uso anterior de los modelos conceptuales es quethe models are the key part of the definition of the software system. Rather than the models being handed over to programmers to implement, all or much of the structure and behavior of a system is captured in models, which are automatically transformed into code (and other platform artifacts). Knowledge of the platform is encoded into transformations, which are reused for many systems rather than redesigned for each new system. Además, destacan que in MDA, automated transformations play a key role. Transformaciones necesitan ser automáticas No es necesario generar toda la aplicación

15
Varró according to MDA, software development will be driven by a thorough modeling phase where first (i) a platform independent model (PIM) of the business logic is constructed from which (ii) platform specific models (PSMs) including details of the underlying software architecture are derived by model transformations followed by (iii) an automatic generation of the target application code. Los PSM describen la arquitectura software La generación debe ser automática

16
Weis using MDA, developers create a platform-independent model. A platform-specific model is derived from the PIM to target a specific technology such as Corba, Enterprise JavaBeans, or.NET. Model transformation bridges the gap between the PIM and PSM. In the worst case, developers must manually perform this transformation, and theyll likely think that the PIM decreases their productivity. So, an automatic transformation from a PIM to a PSM is needed. Es necesario automatizar las transformaciones PSM = Tecnología específica

Sobre el proyecto

Feedback

To ensure the functioning of the site, we use cookies. We share information about your activities on the site with our partners and Google partners: social networks and companies engaged in advertising and web analytics. For more information, see the Privacy Policy and Google Privacy &amp Terms.
Your consent to our cookies if you continue to use this website.