What is Model-Driven Development?
Model-driven development, or MDD, is one approach to the creation of computer programs. The focus of MDD is on writing, testing, and implementing the computer program as quickly as possible. Generally, this approach of model-driven development will also attempt to complete the task as efficiently and with as little cost as possible. One of the characteristics of model-driven development is that multiple developers may be employed to work on the same end product. In order to speed up the process of creation the software programs, each developer in the project may take on specific tasks associated with writing the program and testing the results. This can allow persons with specific areas of expertise to contribute to the project, while leaving more mundane tasks to other project members that lack the same level of expertise or background. Producing a finished product through this collaborative method is thought to be a more efficient use of time and resources, as everyone involved perfo
Would you build a house without a blueprint? Complex ideas and constructs require a level of abstraction (a picture) to describe them effectively and efficiently. Models of our systems are built today to provide a graphical “picture” of the business, the design of the system, and the implementation of the system. These models provide the picture needed to express the overall vision and criteria for the system we are building. Model-Driven Development (MDD) uses the model, or the design, to make the development of applications and systems faster and easier. MDD provides a more flexible systems development environment through models. Models are faster to create, edit and maintain compared to code, and they are also able to improve the quality of that code by removing human error associated with the application of patterns and templates to generate common code around common solutions. Removing these redundant tasks from the team, MDD allows the team to focus on the alignment between Busin
“Extreme Programming”, “Agile Modeling”, “Model-driven software development”, “Model-driven architectures”, “Agile Development”, “OMG’s MDA”. These catch-phrases are currently the topic of much discussion in the software development world. Some software methodologists say that modeling should drive the whole process. Some say modeling should be only done informally, and that models should not be kept for future use (i.e., that they are temporary artifacts produced during development). How useful is modeling? When should it be done? Can modeling be demonstrated to provide business value? Can architectures be developed using “agile” or XP approaches? What makes an approach agile, and what makes agile approaches advantageous? Can model-driven approaches be agile? Can we quantify the benefits of agile approaches? These are all questions currently receiving a lot of attention in the software development world. This workshop solicits papers on any of these, or related topics, especially pape
How effective is it? What is a model-driven architecture (MDA) architecture? How can models be used to support agile development of systems? Topics and Motivation “Extreme Programming”, “Agile Modeling”, “Model-driven software development”, “Model-driven architectures”, “Agile Development”, “OMG’s MDA”. These catch-phrases are currently the topic of much discussion in the software development world. Some software methodologists say that modeling should drive the whole process. Some say modeling should be only done informally, and that models should not be kept for future use (i.e., that they are temporary artifacts produced during development). How useful is modeling? When should it be done? Can modeling be demonstrated to provide business value? Can architectures be developed using “agile” or XP approaches? What makes an approach agile, and what makes agile approaches advantageous? Can model-driven approaches be agile? Can we quantify the benefits of agile approaches? These are all qu
