title: What makes my code DDD (domain-driven design) qualified?
body: <p>I'm new to DDD and am thinking about using this design technique in my project.</p>
  
  <p>However, what strikes me about DDD is that how basic the idea is. Unlike other design techniques such as MVC and TDD, it doesn't seems to contain any ground breaking ideas.</p>
  
  <p>For example, I'm sure some of you will have the same feeling that the idea of root aggregates and repositories are nothing new because when you are was writing MVC web applications you have to have one single master object (i.e. the root aggregate) that contain other minor objects (i.e. value objects and entities) in the model layer in order to send data to a strongly typed view.</p>
  
  <p>To me, the only new idea in DDD is probably the </p>
  
  <ul>
  <li>"Smart" entities (i.e. you are supposed to have business rules on root aggregates)</li>
  <li>Separation between value object, root aggregate and entities.</li>
  </ul>
  
  <p>Can anyone tell me if I have missed out anything here?
  If that's all there is to DDD, if I update one of my existing MVC application with the above 2 new ideas, can I claim it's an TDD, MVC and DDD applcation?</p>