I came accross the accronym MDSE today on infoq, and the information I could find what quite unclear and the description was full of buzzwords :MDSE is about enabling software engineers to work at a level of abstraction where requirements, architecture and design information is maximally ordered (in terms of information entropy) and preserved. (Call this the design work product). Further, MDSE should provide engineers with the means to verify and validate their designs primarily terms of their design work productAnd apparently, everyone is doing it: (from the article again)Were at the dawning of the age of MDSE. In the next 5  10 years we will see a significant shift towards MDSE, to the extent that I believe that by the end of this period perhaps 60  80% of software will be designed using model based techniques. I would like to have a concrete, buzzword-free description of what MDSE is. Is it drawing UML boxes and generating code with it, like they did in the 90s with Rational Rose? (while were at it, if anyone has an example of software generated using those techniques, I would really like to see a concrete example).
What exactly is model driven software engineering (MDSE)?
methodology
model driven software engineering (MDSE) is the marketing promise of software tool manufacturersthat soon significant parts of software can be generated out of software-models.The interview partner in the article you are refering to , Robert Howe is a tool manufacturer (see http://www.verum.com/ for details)But against tool manufacturer-s promises mdse has not become mainstream yet.The hybris internet shop system is a working example of MDSE: you as a software developper maintain xml-model-files (*-items.xml)and codegenerators/interpreters generate db-modell/java-code for persistence/guis out of it. If you need an additional attribute just add it to the xml-model and after the generator/interpreter has done it-s job you can use the attribute to implement the business logic.