I agree some of the templates are the weakness of EA (although I undesrstand it is better in 7.1). Too say they are not the same as MDD->DSL is accurate. By definition MDD is much closer to the specific language you are using. However, all that aside once the import is complete (or your model definition is at the point where you can generate code) the roundtrip enginerring between EA and the language of choice is pretty much automatic.

My problem with this is that kind of defeats the purpose of the model which is to abstract the solution at a higher level to take a look at the overall patterns and architecture.

As for Folwers comments I agreed with him when his article was written 3 years ago. Now I belive the languages and tools have invalidated his arguments against UML PIM.

In order to define a successfull Enterprise LOB you must take into account all architectures that could be helpful to you. At that level a Language Specific modelling tool like a DSL is too close to a given architecture and solution to help. I think the abstraction of UML helps define better applications.

BPML and BPEL are the tools that help define a better busines process. I think EA has done a good job on incorporating those.

The UML PIM Camp vs Model Driven Development
http://martinfowler.com/articles/mdaLanguageWorkbench.html

I am not advocating a ‘skilled business line manager’ changing the architecture with a model on the fly, as the original article that Dave posted suggests MS is aiming for. But at the same time, Im sure you can agree, defining a successful business process ‘model’ is far more important to the success of an enterprise LOB app than the technology that does the work.

Although I like Don and agree he is smart, if you want to talk modeling and quote an authority I am sorry but for me you will have to pick one of the 3 amigos and preferably Grady Bouch. There is one smart dude.

@Jarod

I am not sure where the perception has come from that UML does not allow good round trip Engineering. Take a look at the Enterprise Architect product line from Sparx Systems. Full roundtrip engineering, integration into eclipse and Visual Studio and support for multiple languages and platforms not just .NET. All for under $300 for a Enterprise tool This is UML based and not vendor specific. It provides code generation along the lines of the DSL tools MS has. Very cool.

UML will be changed to WML- Whiteboard Modelling Language

http://msdn2.microsoft.com/en-us/magazine/cc163729.aspx

I hope that these sources are deemed credible enough to read the article with an open mind.

MSML will be vendor specific, and while that is helpful if you only live in a MS world it is not realistic in Enterprise software. That is why I think UML will survive. It is capable of modeling the real enterprise software environment that is not vendor specific.