Blog overview 2009

It’s the end of the year again. Like last year I want to give you quick overview of this year’s content. But first I want to thank you for the useful discussions we had in the comments and on twitter. I hope you enjoyed reading my articles as much as I enjoyed writing them. I wish you all the best for 2010 and hope we can keep sharing knowledge!

Top 10 posts

Based on the number of page views each
article on my blog had this year I have created the following top 10
list:

1. 15
   reasons why you should start using Model Driven Development
2. 5
   types of Model Driven Software Development
3. What
   every architect should now know about the Service Component Architecture
   (SCA)
4. MDE
   – Model Driven Engineering – reference guide
5. DSL
   development: 7 recommendations for Domain Specific Language design based
   on Domain-Driven Design
6. SOA
   is dead; long live Model-Driven SOA
7. A
   Framework for Model-Driven SOA
8. 8
   reasons why Model-Driven Development is dangerous
9. Model
   Driven Engineering tools compared on user activities
10. Architecture
    requirements for Service-Oriented Business Applications

I didn’t take the time of publishing
into account when looking at the statistics. So, articles posted more
recently are less likely to show up in the top 10, unless they are very
popular. In this context it is remarkable that the number 1 article
is my most recent one!

Blog summary for 2009

January

• MDE
  – Model Driven Engineering – reference guide:
  my attempt to given an overview of most of the concepts and terms used
  in the field of model driven software development.
• 10
  Misperceptions and challenges of Model Driven Development
• SOA
  is dead; long live Model-Driven SOA:
  a reaction on the SOA is dead discussion at the start of this year.
  Conclusion: SOA isn’t dead, but we need to develop SOA solutions in
  a model driven way.

February

• Roles
  in Model Driven Engineering:
  an overview of the new roles in software development when moving to
  a model driven approach.
• Model
  Driven Engineering tools compared on user activities: what’s the difference between a DSL tool
  and a Model Driven Software Factory? How to categorize some well-known
  tools?

March

• What
  every architect should now know about the Service Component Architecture
  (SCA): an overview of SCA.
  The standard and how to use it.
• Microblog:
  news and articles on Model Driven Engineering
• 5
  types of Model Driven Software Development:
  using a metaphor I explained five different model driven software development
  approaches.

April

• The
  Science of Model-Driven SOA:
  a short overview of two recent scientific publications researching a
  framework or methodology providing end-to-end guidance and assistance
  to refine and transform business models created by business experts
  into IT models and then to IT implementation.

May

• DSL
  development: 7 recommendations for Domain Specific Language design based
  on Domain-Driven Design:
  in this article I have tried to document my experience in desiging DSLs.

June

• A
  Framework for Model-Driven SOA:
  my first attempt in defining a framework for Model-Driven SOA. What
  models and transformation do we need and why?
• 8
  reasons why Model-Driven Development is dangerous: is MDD the silver bullet? Of course not.
  You need to be aware of its limits. This article gives an overview of
  8 potential dangers or pitfalls of MDD.

July

• 6
  questions to Maarten Steen, experienced researcher in the field of Model
  Driven Engineering

August

• A
  metaphor for Model Driven Engineering:
  my favorite metaphor for explaining MDE / MDD to the business.

September

• From
  Process Design to Process Automation:
  the slides of my talk at BPM2009.

October

• Modeling
  an organization using Enterprise Ontology:
  introducing Enterprise Ontology. A formal method to model organizations.
• An
  Enterprise Ontology based approach to Model-Driven Engineering: an overview of my thesis which presents an
  approach to MDE based on Enterprise Ontology: Model-Driven Enterprise
  Engineering.
• Architecture
  and Engineering in Business Engineering:
  software built by people who understand the business and who are able
  to express that knowledge in formal models.

November

• 10
  things you should know about Model Driven Development: an overview of my talk at the Devnology community
  day. An introduction to MDD with some highlights of more advanced topics.
• 15
  reasons why you should start using Model Driven Development: why MDD? What are the advantages of MDD,
  MDE, MDA or other model-driven related acronyms?

December

• This post.