What is Domain Driven Design?

When a company faces big projects, perhaps with a lot of complexity in terms of analysis and implementation, it can cause potential problems such as misunderstanding business processes or, even worse, developing a software solution that will not satisfy business requirements.

What are the goals of Domain Driven Design?

The main goals that DDD seeks to satisfy originate from the book ‘Domain Driven Design tackling complexity in the heart of software’ written by Eric Evans in 2003. As its name suggests, Domain Driven Design tackles complex problems rather than smaller, less complex ones. When it comes to modeling small domains, Domain Driven Design may not be the best approach to use.

One of the book’s main goals is to outline how to develop software based on evolving a business model. This model is a representation of the structure, activities, processes, actors, and interactions that there are in a company. Depicting parts of a company can be achieved by drawing diagrams; for example, it is possible to use UML. Additionally, domain and technical experts must regularly interact throughout the process of building such a model.