Theory
a Bounded Context is a semantic contextual boundary. This means that within the boundary each component of the software model has a specific meaning and does specific things.
Remember that a Bounded Context is where a model is implemented, and you will have separate software artifacts for each Bounded Context.
In Practice
- I think this translates to having separate ubiquitous language docs. With each doc separated by the bounded context.
- Keep your artifacts (docs & diagrams) anywhere you can have multiple people work on one file, plus the ability to leave comments.
- eg confluence, notion, google docs
- Bear your audience in mind - who’s reading/maintaining these ubiquitous language docs?
- What other bounded contexts do you have to interact with? A way to think about this is Team Interaction Modeling with Team Topologies
- Event storming for domain modelling
- miro/figma boards for domain modelling.