Document Your Domain

In the following chapters, we’re going to go through the life cycle of creating an application from scratch. We won’t be writing any application code, but we will be documenting the important steps with diagrams. I’ve written the chapters roughly in the order I would go about each step in my professional career, but you may find a slightly different order works for you. To start off, we’re going to create a domain model. Domain modeling is the primary way of determining the important aspects of a business. It’s usually created collaboratively by engineering, product, and business stakeholders to ensure all major parts of the business are aligned on what the domain model looks like. That makes it a good candidate for diagramming. By documenting your domain models with a diagram, that domain model is going to come to life and is more likely to be practiced. Furthermore, due to the ease of Mermaid, it’s possible to create a draft of the domain model in real time when discussing with col- leagues in a meeting. I recommend reading Domain-Driven Design: Tackling Complexity in the Heart of Software [Eva03] if you’re keen to learn more about DDD. Once you’ve got to grips with domain modeling, it’s going to make your life so much easier. There will be moments during domain modeling where suddenly it all comes together, everyone is on the same page in terms of their understanding of the landscape, and everyone is speaking the same language. <a href="https://medium.com/pragmatic-programmers/document-your-domain-8a1365dc10ae">Click Here</a>