3 ms·

Absolutely. Model-driven development and related paradigms like domain-driven design are still in use in almost any area of business software development. Domai

Absolutely. Model-driven development and related paradigms like domain-driven design are still in use in almost any area of business software development. Domain-driven design in particular has become quite popular again in recent times and I don't see it going anywhere anytime soon. The thing is: You have to do it right to reap the rewards. Especially in larger companies it's unfortunately not uncommon to encounter all-encompassing models with hundreds (or even thousands) of entities / classes. That kind of model not only doesn't help with developing software faster and more cost-efficiently but even has an adverse effect. In order to benefit from model-driven development you have to think in terms of the various business functions (sales, HR etc.), the boundaries between those functions and models which are specific to their respective subdomain.

ziikutv 10y ago
Yeah. I was told it leads to rapid development.... disagree. Just making a project in class i found it to Beverly tedious jumping between diagrams. Much rather prefer code.
- BjoernKW 10y ago
  Nah, rapid application development for the most part is a pipe dream. It works for contrived school examples and default CRUD interfaces but as soon as you need custom logic or user interface behaviour it breaks down pretty rapidly. However, rapid application development isn't the main benefit of these approaches. Their main point is getting a better understanding of the business domain you're operating in.
- UK-AL 10y ago
  DDD is basically more of a code first MDD. It's still very much in vogue. I do like DDD, the idea that you have a project that is completely focused on solving the business issues. Then the infrastructure/technology concerns simply plugin into that model. Gives you flexibility on changing technologies more easily, and well designed domain model can give you a serious business advantage.

ziikutv 10y ago

Yeah. I was told it leads to rapid development.... disagree. Just making a project in class i found it to Beverly tedious jumping between diagrams. Much rather prefer code.

BjoernKW 10y ago
Nah, rapid application development for the most part is a pipe dream. It works for contrived school examples and default CRUD interfaces but as soon as you need custom logic or user interface behaviour it breaks down pretty rapidly. However, rapid application development isn't the main benefit of these approaches. Their main point is getting a better understanding of the business domain you're operating in.
UK-AL 10y ago
DDD is basically more of a code first MDD. It's still very much in vogue. I do like DDD, the idea that you have a project that is completely focused on solving the business issues. Then the infrastructure/technology concerns simply plugin into that model. Gives you flexibility on changing technologies more easily, and well designed domain model can give you a serious business advantage.