Link Details

Link 303491 thumbnail
User 283378 avatar

By johaan
via theenterprisearchitect.eu
Published: Nov 26 2009 / 05:49

Model Driven Development, why should you use it? This article gives 15 reasons why you should start using Model Driven Development.
  • 15
  • 4
  • 3908
  • 0

Comments

Add your comment
User 388907 avatar

MCII replied ago:

-4 votes [show comment] Vote down Vote up Reply
User 512515 avatar

ramses010 replied ago:

0 votes Vote down Vote up Reply

What a strange reply. It looks like you didn't even read the article. There are many very good reasons to use MDA. Please read something first before adding comments.

User 201742 avatar

shantanu_k06 replied ago:

2 votes Vote down Vote up Reply

I absolutely don't believe that carefully-prepared laundry list. MDA puts the programmer totally out of control and makes the learning curve incredibly steep for someone new joining the team. Not only does it make the code base unwieldy, you also get locked into a certain tool set that mostly won't integrate with your IDE. I am telling this from experience.

User 283378 avatar

johaan replied ago:

1 votes Vote down Vote up Reply

>MDA puts the programmer totally out of control and makes the learning curve incredibly steep for someone new joining the team.
In my experience this is not the case. See also my comment on the article about the roles in an MDD project team.

> you also get locked into a certain tool set that mostly won't integrate with your IDE
A lot of the current MDD tools are based on Eclipse and integrate seamlessly with Java programming.

User 203717 avatar

chudak replied ago:

0 votes Vote down Vote up Reply

Blah blah blah. There's no silver bullet. Your secretary can't write an enterprise application no matter how much you want this to be the case.

User 283378 avatar

johaan replied ago:

0 votes Vote down Vote up Reply

There's indeed no silver bullet. That's why the article also points to other articles talking about the dangers / challenges of MDD.

> Your secretary can't write an enterprise application no matter how much you want this to be the case.
Agreed. You will need some affinity with IT, you will need training for the MDD tool. The only point the article makes is that you do not have to be a specialist, e.g. a database expert, or to have knowledge about Spring (or other frameworks). You use models, and the plumbing is done by the MDD tool.

User 393686 avatar

RawThinkTank replied ago:

0 votes Vote down Vote up Reply

POJO + MDD

No damn xml, scripts, configuration files, learning new twisted methods of doing things


POJO POJO POJO POJO POJO POJO POJO POJO POJO POJO POJO POJO

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java