today I want to share with you DDD in one schema.
So, when I first time tried to grasp what is DDD, I heard Bounded context, domain model, Entity objects, Value objects, etc.
Then I started to read "Domain-Driven Design: Tackling Complexity in the Heart of Software" of Eric Evans and initially was lost in his terms.
After a while I was lost what goes in what. After re-reading I've got the point.
Enterprise application can have some vocabulary. It can be one, or more. But if it has more then one vocabulary, it can be useful to separate those vocabularis by the definition bounded context.
Each bounded context can have it's own Domain model.
Each domain model can have entity objects and value objects. And so on. In order not to loose in all of this I've made for myself following schema:
Arrows goes from parent set to child sets: