Week 13 Part VI · Final Architectural Defense 🎤 Student Project Presentation 3 · Final
Final Student Presentations
Instructor lesson plan: final presentation session and oral defense.
Learning objectives
- Demonstrate a complete enterprise .NET application.
- Defend architecture, use cases, design patterns, security, integration design, documentation, and optional AI integration.
- Reflect on tradeoffs, risks, and future extensions.
Tools this week
architecture documentADRsquality evidencefinal slidesrepository tag
🎓Lecture · 2 hours
| 0:00-0:15 | 15 min | Final synthesisConnect the semester arc: domain, API, persistence, architecture, patterns, security, integration, AI integration. |
| 0:15-0:40 | 25 min | Architecture review checklistWhat a reviewer should be able to find in the repository and documentation. |
| 0:40-1:05 | 25 min | Quality and maintainability reviewCode structure, naming, dependency direction, integration boundaries, and known limitations. |
| 1:05-1:15 | 10 min | Break |
| 1:15-1:40 | 25 min | Oral defense preparationHow to answer why this design, why this pattern, and what would change next. |
| 1:40-2:00 | 20 min | Course closureHow the skills transfer to capstone and industry work. |
Final defense questions.Why did you choose this architecture style?
A strong answer connects the choice to use cases, team size, change risk, persistence needs, and testability.
Which pattern would you remove if the project stayed small?
A strong answer names ceremony and explains what benefit would no longer justify its cost.
Key takeaways.- Architecture is a set of defended tradeoffs.
- Quality evidence and documents are part of the submitted system.
- Maintainability is visible in the repository structure.
📚Reading & resources
- Team architecture document Final source of truth for the submitted design.
- Team ADRs and quality evidence Evidence for decisions and quality claims.
🎤Student Project Presentation · 2 hours
The full practice slot is given to Student Project Presentation 3 · Final. Teams present the complete working system, final architecture, main design decisions, enterprise patterns, security and validation mechanisms, integration design, documentation, optional AI integration, and lessons learned.
What each team presents.- Complete working system and final architecture walkthrough.
- Main design decisions, implemented enterprise patterns, and use-case coverage.
- Security, validation, integration boundaries, quality evidence, and documentation.
- Optional AI integration, including boundaries, evaluation, and risks.
- Short oral defense with questions to any team member.
Final deliverables
- Source code repository and tagged release.
- Running application instructions, database schema and migrations, API documentation.
- Architecture document, ADRs, design pattern explanation, quality evidence, final slides.
- AI tool use note and optional AI integration design.