# The Domain Model
This method provides a good visualization over a complex world with complex ideas.
The context defines what the team can or wants to work on and what is outside of access. The domains define definable fields of action by clarifying which points belong together and are closely related and what can be viewed separately from one another. Individual domains should have as few interfaces to other domains as possible.
A clear picture of the dependencies on other topics and areas emerges.
One advantage of this method is that it promotes teamwork and forces the individual to keep an eye on the entire process or to deal with it in the first place. This sharpens the individual's view of relationships. Usually, you want to solve a problem as quickly as possible - without further ado, but also without questioning. Writing down the individual steps in the "5 Whys" method requires clear questions and answers.
For example, the facilitator draws a pig and divides its body into several domains (sections), which are body-relevant. The team is then asked to label the respective domains with the specific tasks/topics/processes.
Agile coach/agile master
The entire agile team
Complex topics structured into domains
# See also
IREB Glossary of Requirements Engineering Terminology, Version 1.6 May 2014