×
  • Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
 

Short introduction to Domain Driven Design & Model Driven Development

by Software Architect/Developer at TigerTeam ApS on Mar 10, 2010

  • 2,386 views

Using Domain Driven Design and Model Driven Development together to create a lean architecture

Using Domain Driven Design and Model Driven Development together to create a lean architecture

Statistics

Views

Total Views
2,386
Views on SlideShare
2,371
Embed Views
15

Actions

Likes
6
Downloads
141
Comments
2

5 Embeds 15

http://www.slideshare.net 8
http://pgonyan.blogspot.com 4
http://pgonyan.blogspot.com.es 1
http://www.slashdocs.com 1
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via SlideShare as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

12 of 2 previous next

  • jeppec Jeppe Cramon, Software Architect/Developer at TigerTeam ApS Thanks for your comment :)

    It's true, that this approach works just a well with a text (DSL) based approach to describing the domain.
    The more complex the domain, the more I believe that Visual models benefit the description of the domain. I've experienced this on quite a few projects already. It's easier to see the complex interrelations between aggregates in a visual model, than in a textual hierarchical description. Even though it might sound odd, even the fairly 'ugly' UML class diagrams have worked very well with non-technical personnel and given a good enough foundation for communication.

    Using the code directly as a model is an idea that I've used quite a lot too, but it's IMO less suited for domain and service models. The more expressive the language (XText/Ruby/Groovy/Scala/etc.) the better, when it comes to using Code as the Model :)

    We're in the process of open sourcing the tool, and during that transition a renaming from xxxxMDSD would definitely be in place :)
    3 years ago
    Are you sure you want to
    Your message goes here
    Processing…
  • cyriux martraire cyrille, Software Developer at Arolla Interesting presentation about an interesting tool, MDD sure gains a lot of relevance when aware of DDD. However I have the feeling that in this code generation approach most of the value comes not from the model being visual, but rather from using pre-canned patterns such as Temporal Object or other Hibernate-specific usage idioms.

    Looks like as opposed to other tools you go much further than code templates and use smarter meta-model-based wizards to generate the code for each pattern, and I think this is a good thing!

    I'm still not fan of the code generation part of MDD, I prefer using code directly as a model, but I'm glad to see tools getting much better like Tiger MDSD ('MDSD' hard to remember to me by the way). Cheers
    3 years ago
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Short introduction to Domain Driven Design & Model Driven Development Short introduction to Domain Driven Design & Model Driven Development Presentation Transcript