- HLD
- LLD
- C4
- DDD
Session booking system for coaches
An example of the complete documentation set a development team, or a vendor answering an RFP, receives. The domain comes from my product Gymme; the scope matches package E.
- C4 diagrams: context and containers
- module dependency graph and event flow
- Calendar module class diagram: aggregates, value objects, domain service, ports
- sequence scenarios: booking, cancellation, session completion
- architecture decision records (ADR) and non-functional requirements
The document shows what a technology-independent system design looks like: from the business context, through the split into modules and their dependencies, to one module detailed down to classes and scenarios. It is the same format you receive in package E, and the same one a team can start development from without guessing.