Cohesion
Whether the things inside a boundary belong together and change for the same reason.
Nothing written here yet
This topic is part of the curriculum but has no questions, cards or glossary entries so far. The rest of Architecture Fundamentals may still cover what you are looking for.
Neighbouring topics
Architecture Fundamentals
General material on what solution architecture is and what an architect is accountable for.
Requirements to Constraints
Turning stated requirements into the constraints that actually bound a design.
No content yetFunctional vs Non-Functional
Behaviour versus quality of behaviour, and why only the second constrains structure.
No content yetArchitectural Drivers
The small subset of requirements whose change would force the structure to change.
No content yetQuality Attributes
Availability, latency, throughput, security, cost — expressed as testable scenarios.
No content yetArchitecture Principles
Durable agreed rules that rule options out, stated with rationale and implications.
No content yetCoupling
How much one component must know about, or change alongside, another.
No content yetModularity
Composing a system from parts that can be understood and replaced independently.
No content yetSeparation of Concerns
Organising so that a change to one concern touches one place.
No content yetAbstraction & Encapsulation
Hiding mechanism behind contract, and protecting invariants by owning state.
No content yetArchitecture Styles
System-level organising shapes, and how they differ from problem-level patterns.
No content yetEvolutionary Architecture
Designing for guided incremental change rather than for correctness on day one.
No content yetFitness Functions
Automated checks that an architectural characteristic still holds.
No content yetArchitecture Documentation
What to write down, at what altitude, and what nobody will ever read.
No content yetConway's Law
Systems mirroring the communication structure of the organisation that builds them.
No content yetTrade-off Fundamentals
Why every architecture is a set of purchases, and how to state what you gave up.
No content yetTechnical Constraints
Existing estate, skills, licences and platforms as inputs rather than obstacles.
No content yetArchitecture Roles
Solution, enterprise, domain and platform architecture, and where each is accountable.
No content yetReference Models
Shared conceptual frames — layering, tiers, viewpoints — and their limits.
No content yet