Week 8 Part III · Architecture and Patterns 🎤 Student Project Presentation 2 · Interim

Midterm Presentations and Clean Architecture

Instructor lesson plan: lecture (2 h) and practice (2 h).

Learning objectives

Explain Clean Architecture dependency rules.
Compare layered architecture, Clean Architecture, and modular monolith structure.
Present a working API, database integration, patterns, and current architecture.

Tools this week

Clean ArchitectureC4 diagramsADRsinterim rubric

🎓Lecture · 2 hours

0:00-0:20	20 min	Clean Architecture mapEntities, use cases, interface adapters, frameworks and drivers.
0:20-0:45	25 min	Ports and adaptersHow external dependencies enter through interfaces and adapters.
0:45-1:10	25 min	Modular monolithFeature modules, bounded contexts, internal contracts, and migration paths.
1:10-1:20	10 min	Break
1:20-1:45	25 min	Architecture decision recordsWriting ADRs that explain context, decision, alternatives, and consequences.
1:45-2:00	15 min	Presentation logisticsDemo order, timing, questions, and repository tag.

Common misconception to confront.

Students often think: Clean Architecture requires many projects and boilerplate.
Set it straight: the core idea is dependency direction. Physical structure should fit project size.

Check for understanding

What must not depend on EF Core?

Domain rules and use-case policy should not depend on EF Core types or configuration.

What belongs in an ADR?

Context, decision, considered alternatives, consequences, and date or status.

Key takeaways.

Clean Architecture protects policy from details.
Modularity can live inside one deployable application.
ADRs make tradeoffs visible.

📚Reading & resources

Clean Architecture Dependency rule and use-case chapters.
Architecture Decision Records Lightweight architecture decision documentation.

🎤Student Project Presentation · 2 hours

The full practice slot is given to Student Project Presentation 2 · Interim. Teams demonstrate a working API, database integration, current architecture, implemented patterns, main workflows, code structure, and open issues.

What each team presents.

Working API demo and database integration.
Current architecture and dependency direction.
Implemented design patterns and main workflows.
Open issues and next steps.

Project integration (this week)

Apply midterm feedback.
Add or revise ADRs for major architecture decisions.
Prepare security and domain-logic work for week 9 and 10.