OOPSLA/GPCE: Best Practices for Model-Driven Software Development
Pavilion B
Monday, 8:30, full day | 7 | · | 8 | · | 9 | · | 10 | · | 11 | · | 12 | · | 13 | · | 14 | · | 15 | · | 16 | · | 17 | · | 18 | · | 19 | · | 20 | · | 21 |
Jorn Bettin, SoftMetaWare, New Zealand
Ghica van Emde Boas, independent consultant, The Netherlands
Aditya Agrawal, Vanderbilt University, USA
Markus V?lter, independent consultant, Germany
Jean B?zivin, University of Nantes, France
http://www.softmetaware.com/oopsla2004/mdsd-workshop.html
In recent years we have seen the Object Management Group (OMG) endorse the value of model-driven approaches to software development. The focus of the OMG's Model-Driven Architecture initiative is on standardization of notations and on tool interoperability. In keeping with its traditional reluctance to standardize methodologies, the OMG offers little in terms of methodological support for model-driven software development.
Model-Driven Software Development (MDSD) is a new software development paradigm for distributed project teams involving 20+ people, with roots in software product line engineering, which is the discipline of designing and building families of applications for a specific purpose or market segment.
The relationship between MDSD and software product line engineering can be compared to the relationship between Component Based Development and Object Technology: One builds on the other.
What sets MDSD apart from classical software product line engineering is the emphasis on a highly agile software development process. MDSD provides the scalability that is not inherent in popular agile methodologies such as Extreme Programming.
|
