Reresher-Domain Driven Design

10. Group modelling Technique.
12. representation and actual relationships between context and their models.
13. number of objects that should be responsible for communication between a pair of contexts.
16. Object which is immutable and has no conceptual identity.
17. language between developers and Domain experts.
18. Bundle of related objects which are treated as a single unit from the client.
20. encapsulates the logic of data persistence.
21. Intersection of two contexts.

1. Linguistic boundary.
2. logical agreement and dependence.
3. any actions on the domain.
4. pattern used to create independent domain context maps.
5. pattern to create Objects to access or abstraction.
6. layer, which is between 2 different systems that don't share the same semantics .
7. partitioning of a larger system to bring the core domain to the fore.
8. an operation to read .
9. root of the related objects bundle.
11. reference objects, which are primarily defined by its identity
14. layer which encapsulates the business logic
15. an operation that intentionally creates impact.
19. consistency rules that must be maintained whenever data changes.