Enterprise MDA Workbench
15 reasons why you should start using Model Driven Development I have written a lot about model driven software development approaches from different perspectives. For example from a domain specific language design perspective, an integrated modeling approach for SOA perspective, etc. I also have tried to give you a balanced view on MDD by talking about the things to know before starting with MDD and by discussing some potential dangers of MDD. You would say that if someone asked me for the advantages of Model-Driven Development I would just send him a link…
LeGenieLogicielLesModelesEtLesProcedes.pdf (Objet application/pdf)
Markus Voelter has defined model driven development as “a software development approach that aims at developing software from domain-specific models. Domain analysis, meta modeling, model-driven generation, template languages, domain-driven framework design and the principles of agile software development form the backbone of this approach.” MDD is quickly moving from a novel concept to a pragmatic business necessity in large corporations. Strategic Objectives and Advantages of Model Driven Development | Javalobby
Model-driven architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models. Model-driven architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001. Overview The model-driven architecture approach defines system functionality using a platform-independent model (PIM) using an appropriate domain-specific language (DSL). Model-driven architecture
Recently a colleague asked me if model driven software development (MDSD if you like acronyms) is really faster than traditional development. The question is hard to answer because that really depends on the specific set of tools you use, the abilities of your team and so on. Is Model Driven Development Faster? « The Software Chef
7/22/2003 - An independent case study released by Compuware (NASDAQ: CPWR) and conducted by The Middleware Company revealed a 35 percent productivity gain for organizations employing a model-driven architecture (MDA) development approach. The significant gain was measured by comparing the MDA approach against a leading, code-centric, integrated development environment (IDE). “We came into this study as skeptics; we left as believers,” said Salil Deshpande, CEO of The Middleware Company, a leading, independent Java research and consulting organization. “MDA has real world legitimacy as a fast, productive, accurate and consistent approach for developing enterprise applications.” Model-Driven Architecture Leads to Productivity Gain of 35%
8 Reasons Why Model-Driven Approaches (will) Fail Model-driven software development is gaining more and more interest nowadays. Acronyms starting with MD are invented from day to day. To mention a couple of them: MDA, MDE, MDD, MDSD, MDSE.
Introduction à MDA par la pratiqe - Club d'entraide des développeurs francophones L'usage de la plate-forme Eclipse permet une manipulation aisée, ainsi que des transformations comme nous allons le voir dans la partie suivante. Toutefois, la création de modèle par le biais de Java annoté n'est pas la plus intuitive. Il est possible de créer des modèles EMF pour Eclipse à partir de l'outil Rational Rose, encore faut-il en disposer. Pour palier à ce manque, nous allons utiliser Poséidon, qui est un outil puissant et disponible - ce qui n'est pas la moindre de ses qualités - gratuitement dans une version Communauté. Il permet de mettre à profit l'un des aspects qui a fait le succès de UML : les représentations graphiques des différents diagrammes. Nous allons voir comment il est possible de créer, de manière simple et intruitive, un programme à l'aide de la version Communauté de la plate-forme Poséidon.