And this is as much as I have to say about model driven development for now.
I hope this short intro can be helpful to a beginner in this topic or to show someone interested in it what options this approach has to offer.
Because model driven development is first of all about the approach, not about the tooling, it is about way of thinking about the problem - in models first.
It forces you to structure your thinking.
It exposes this thinking to other people.
It forces you to define ubiquitous language (DDD, anyone?).
It creates a foundation for basically any discussion with other people.
It creates enforceable documentation.
And this list could go on and on. I could easily write 5-10 more points, but I think you get the point.
Yes, model driven development is not magic.
Yes, it is not a silver bullet.
But in my 20 years of professional software engineering experience, this is as close to a silver bullet as it gets.