The document outlines eleven dogmas of model-driven development, emphasizing the importance of separating domain and implementation concerns to enhance software development. It posits that effective modeling addresses domain issues early and facilitates requirement validation, while also suggesting that implementation can vary across architectures. Key points include the contrast between modeling and implementation languages, and the independence of architecture from specific application domains.

1. Eleven
Dogmas of Model-driven
Development
Rafael Chaves
rafael@abstratt.com - Twitter: @abstratt
http://abstratt.com/blog/

2. I
Enterprise Software is much
harder than it should be, lack
of separation of concerns is to
blame.

3. II
Domain and
architectural/implementation
concerns are completely
different beasts and should be
addressed separately and
differently.

4. III
What makes a language good
for implementation makes it
suboptimal for modeling, and
vice-versa.

5. IV
Domain concerns can and
should be fully addressed
during modeling,
implementation should be a
trivial mapping.

6. V
A model that fully addresses
domain concerns will expose
gaps in requirements much
earlier.

7. VI
A model that fully addresses
domain concerns allows the
solution to be validated much
earlier.

8. VII
No modeling language is more
understandable to end-users
than a running application (or
prototype).

9. VIII
A single architecture can
potentially serve applications
of completely unrelated
domains.

10. IX
A same application can
potentially be implemented
according to many different
architectures.

11. X
Implementation decisions are
based on known guidelines
applied consistently
throughout the application,
and beg for automation.

12. XI
The target platform should not
dictate the development tools,
and vice-versa.