Core vs Supporting vs Generic Subdomains
This generated surface maps a learner-facing curriculum unit to its canonical source routes.
Curriculum surface
- Open learner-facing unit
- Curriculum path:
content/curriculum/production/semester-10-capstone/module-01-domain-analysis-architecture-design/concepts/cluster-02-domain-discovery/05-identifying-core-supporting-generic-subdomains-primary.md - App:
production - Semester:
semester-10-capstone - Module:
module-01-domain-analysis-architecture-design - Unit kind:
concept - Curation level:
module_curated
Learning objectives
- Explain Core vs Supporting vs Generic Subdomains as the work of turning a real problem domain into explicit boundaries, constraints, and architectural decisions instead of vague project ambition.
- Use Core vs Supporting vs Generic Subdomains to make the capstone direction defensible: what problem is being solved, what scope is excluded, and which tradeoffs matter most.
- Use
api-design-patterns,clean-architecture,fundamentals-of-software-architecture,learning-domain-driven-designto connect the learner-facing explanation to domain analysis, architecture sketches, requirements framing, and decision rationale.
Prerequisites
- Comfort with architecture, system design, and making tradeoffs explicit before implementation begins.
Source books
api-design-patternsclean-architecturefundamentals-of-software-architecturelearning-domain-driven-design
Source routes
Api Design Patterns
- /books/api-design-patterns via
API Design Patterns
Clean Architecture
- /books/clean-architecture via
Clean Architecture
Fundamentals Of Software Architecture
- /books/fundamentals-of-software-architecture via
Fundamentals of Software Architecture
Learning Domain Driven Design
- /books/learning-domain-driven-design via
Learning Domain-Driven Design
Supporting curriculum routes
- /architecture/semester-07-architecture-ddd/module-03-domain-driven-design-bounded-contexts/concepts/cluster-01-strategic-design-foundations/01-domain-subdomain-bounded-context-three-level-split-primary via
S7 M03 -> Domain / subdomain / bounded context: three-level split,S7 M03 → Domain / subdomain / bounded context: three-level split - /architecture/semester-07-architecture-ddd/module-03-domain-driven-design-bounded-contexts/concepts/cluster-01-strategic-design-foundations/02-core-supporting-generic-subdomain-classification-primary via
S7 M03 -> Core/Supporting/Generic subdomain classification,S7 M03 → Core/Supporting/Generic subdomain classification - /architecture/semester-07-architecture-ddd/module-03-domain-driven-design-bounded-contexts/concepts/cluster-05-ddd-in-practice/15-architecture-to-context-alignment-services-per-bounded-context-primary via
S7 M03 -> Architecture to context alignment: services per bounded context,S7 M03 → Architecture to context alignment: services per bounded context
External enrichment
- C4 Model (
official_docs_companion) - Useful when the learner needs a concrete, lightweight way to communicate capstone architecture and system boundaries clearly. - arc42 Documentation (
optional_deep_dive) - Provides a fuller architecture-documentation template for capstone teams that need more rigor around decisions and structure.
AI companion modes
- Explain simply
- Socratic tutor
- Challenge my understanding
- Diagnose my confusion
- Connect forward / backward
Source-of-truth note
This teaching unit is learner-facing guidance assembled from canonical book routes plus prior curriculum surfaces. Use the listed source books as the primary conceptual spine for Core vs Supporting vs Generic Subdomains, and use the supporting curriculum routes to reconnect earlier learner-facing explanations when needed.