This is the second article in a series that covers the contents of a training I developed (and taught) for over 7 years now. The training covers software design, using the Domain Driven Design approach as it’s basis.

This is the first article in a series that covers the contents of a training I developed (and taught) for over 7 years now. The training covers software design, using the Domain Driven Design approach as it’s basis. Why I chose Domain Driven Design is explained in a seperate article.

This morning I spent some time in Steven Kelly’s tutorial on Planning for Success in MDD at the CodeGeneration conference. Steven provided us with his views and input on how to plan for introducing Model Driven Development - using numbers to convince management and engineers, but also looking at the soft and organisational side of things.

Ever since I came across WebDsl, almost three years ago, I’ve been wanting to use it for at least one of the web sites I maintain (four at the moment, with a fifth underway). However, since so far I’ve relied on the services provided by hosting providers, I’ve been stuck in the world of MySql and PHP, where as WebDsl targets Java and Seam platforms. A mismatch if ever there was one. During CodeGeneration 2009 I asked Eelco Visser whether there were plans for extending WebDsl into the PHP domain. He indicated that there were ideas, but no concrete plans. Up till now, that is how things stayed - the project’s focus was more on extending the language and providing proper development tool support then switching to different platforms.

Who hasn’t heard stories about managers who don’t have a clue what their engineers, architects or quality officers are trying to achieve? And who has tried to go over their manager’s head to try and fix the problem that way? Out of frustration, or to strenghten their own position, like this lady? I know I did, on a few occasions, and in one case I actually did it - be it without much success.