- Matthias Bohlen
Course Content of iSAQB® DDD
Agile software development provides an orientation for Domain Driven Design. From the Domain-drive Design the basic concepts, as well as elements of the application domain are modeled, so that the software fits the technicality of the application domain. The Domain-driven Design is independent to the programming language, frameworks, as well as tools, however, there are frameworks and tools that support the approach of DDD or offer an implementation of specific DDD patterns.
Domain Driven Design is characterized by a number of concepts that should be considered in the modeling process. The introduction of a ubiquitous (generally used) language is essential, which is used in all ranges of the software production. It is a language that describes the technicality of the elements of the domain model, classes, methods, and so on. It is described as "A language structured around the application domain, as well as used by all team members to link all team activities to the software."
- Eric Evans: presentation notes from his November 6, 2007 talk at JAOO.
The Parts of The Domain Model
The following parts of the domain model differentiate themselves in the Domain Driven Design:
- Entities (Reference Objects)
- Modules (Modules, Packages)
- Domain Events
- Service Objects (Services)
- Value Objects