Model Driven Software Development.
As I understand it it raises the abstraction level of the design to better reflect the domain the software will attempt to run in. That's alot to say in just one sentence.
The communication between the domain experts (customer) and the developers is crucial to make this methodology work. What I want to know is if there is a tool suite or set of best practices that will help in the initial thrust of MDSD? Once the domain is fleshed out what about mapping that model to an ORM (or whatever)?
I am just diving into the realm of MDSD and DSL so any constructive ideas or comments will be appriciated.
If you are developing on Microsoft platforms, you might want to check out Oslo also. There is a nice overview here: http://www.pluralsight.com/community/blogs/aaron/archive/2008/11/03/introducing-quot-oslo-quot.aspx
Here's a ton of links from Chris Sells: http://www.sellsbrothers.com/news/showTopic.aspx?ixTopic=2197
I am not ready to equate Domain Driven Design with Model Drive Development just yet.
You might also want to check out Model Driven Architecture (the OMG MDA) for perspective though probably not much on rolling your own.
A big issue in Model-driven-anything has to do with where the expertise comes from that derives implementations from models and what level maintenance (and debugging) happen at. My test of available books would be how they make the pipeline understandable and how well one can comprehend the path from modeling through deployment and back again.