Sources and further reading
The books, papers and standards this article draws on, grouped by subject, with what each one supports.
Domain-Driven Design
Domain-Driven Design: Tackling Complexity in the Heart of Software
Strategic design, bounded contexts, the ubiquitous language, knowledge crunching, context mapping, hands-on modellers and refactoring towards deeper insight.
Implementing Domain-Driven Design
The practical development of Evans's strategic patterns.
The workshop technique for discovering context boundaries.
Replacing a legacy system one context at a time.
Scrum and its scaling frameworks
One product, one Product Goal, one Product Backlog, one Product Owner, and teams of typically ten or fewer.
Manifesto for Agile Software Development
The shared roots of agile and DDD, and the call for a sustainable pace.
The Nexus Integration Team, here working on the context map.
Requirement areas with Area Product Owners, aligned here with bounded contexts.
Cited among the scaling frameworks.
Cited among the scaling frameworks.
Teams and communication
The Mythical Man-Month
Communication paths that grow faster than the team, and Brooks's law.
Conway's law, and why choosing team boundaries is choosing the architecture.
Cognitive load as a limit on what a team can own, and the inverse Conway manoeuvre.
Safety and regulation
IEC 62304: Medical device software, software life cycle processes
Software safety classes A, B and C, documented architecture, software items and interfaces, and software of unknown provenance (SOUP).
ISO 14971: Application of risk management to medical devices
Identifying hazards, estimating risks and verifying controls.