Core Principles for Software Architects
Core principles are the design ideas that keep code and systems changeable. SOLID guides class design, coupling and cohesion describe how tightly parts depend on each other, and domain-driven design organises software around business concepts with a shared language and clear boundaries between contexts.
Stage: Architecture Foundations · Part of the Software Architect roadmap · Last reviewed 19 November 2026
What to learn in Core Principles
- Apply the single responsibility and dependency inversion principles to a design
- Spot high coupling and low cohesion in a module
- Describe a bounded context and a ubiquitous language
- Model an aggregate with a single consistency boundary
- Draw a context map showing relationships between contexts
- Know when SOLID rules are bent for simplicity
Core Principles interview questions
What is a bounded context in domain-driven design?
A bounded context is a boundary within which a domain model and its terms have one consistent meaning. The same word, such as customer, may mean different things in billing and support, so each context has its own model and explicit integration points.
What do coupling and cohesion mean?
Coupling is how much one module depends on the details of another, and cohesion is how closely the responsibilities inside a module belong together. Good designs aim for low coupling between modules and high cohesion within them.
Where Core Principles fits in the Software Architect roadmap
Core Principles belongs to the Architecture Foundations stage (intermediate level), which takes about 5 hours. What architects actually do.
Other units in this stage
Back to the full Software Architect roadmap