Philipp Fehre

since we are not the experts in the domain the software is placed in, we need to gather input from other people who are experts.

How does the user expect the application to behave in the browser?
How does the business workflow work?
What does the user know about the workflow?

business domain expert

research the target audience

Always remember that we, as developers, are the software experts and therefore are the only ones who are able to manage these expectations

Domain-driven designs focus on getting structure in the problem solving process and also provide the right starting point to begin a conversation every stakeholder can be part of.

Domain-driven design now adds a layer on top, which adds abstractions to express business logic and can encapsulate it from the outside interaction.

the idea of removing distractions

This is why working towards a shared understanding between business experts and developers is so important, both sides need to agree on what they expect from a feature, or a piece of software

ubiquitous language of the project, a language shared by all parties involved in the project.