ID: S202512221259 Status: school Tags: Avans 2-1 LU1, Checklist

avans 2-1 LU1 POC Checklist

Critical Issues to Address

1. Presentatie van technologisch onderzoek (20/50)

• Clarify tech stack criteria: Explain WHY each framework choice is suitable, not just “I wanted to learn it”

  • Document clear, defensible criteria for each framework decision
  • Provide detailed justification (performance, scalability, ecosystem, etc.)
  • Make it “Google-able” - cite sources and industry best practices

• Explain the Onion Architecture: Currently missing from code and documentation

  • Implement onion architecture layers in the codebase if not present
  • Document the architecture visually (diagram)
  • Explain each layer (Presentation, Application, Domain, Infrastructure)
  • Show how it’s reflected in your actual code structure

• Document MongoDB relationships: Implicit relations need to be explicit

  • Create an ER diagram or schema documentation
  • Visually show all relationships in MongoDB
  • Document which relations are embedded vs. referenced
  • Justify design choices for data structure

• Define additional research questions

  • Go beyond provided questions
  • Explain how they influenced your decisions
  • Show critical reflection on framework choices vs. alternatives

• Make presentation interactive and inspirational

  • Add visuals, diagrams, live demos
  • Tell the “why” behind decisions, not just “what”

---

2. Full-stack Realisatie (35/50)

• Add extra functionality beyond requirements
  • Define new features clearly in requirements
  • Implement additional features that go beyond the basic spec
  • Present and explain these additions in your presentation

---

3. Testen (0/40) - URGENT

• Create Unit Tests (5+ required)
  • Test business logic components
  • Aim for at least 80% code coverage on backend
• Create Integration Tests
  • Test happy flow (positive scenario)
  • Test unhappy flow (error scenarios)
  • Use a traceability matrix linking tests to requirements
• Create System Tests (5+ with Postman)
  • Test endpoints with various inputs
  • Document test cases
• Create UI Tests (2+ automated happy flows)
  • Automate frontend tests
  • Integrate into CI/CD pipeline
• Create Test Plan Document
  • Include traceability matrix (requirements → tests)
  • Document all test cases
  • Be able to explain test logic clearly
• Achieve 80%+ code coverage
  • Both frontend AND backend
  • Generate coverage reports

---

4. CI/CD (12/20)

• Improve current CI/CD pipeline
  • Ensure automatic testing on every build
  • Ensure release branch triggers automatic deployment
  • Document what happens during failed states
• Add independent deployment
  • Frontend deployable separately from backend
• Add Rollback functionality
  • Implement ability to revert to previous versions
• Containerize MongoDB
  • Run MongoDB in a container within your cloud environment
  • (Currently using MongoDB Atlas - move to containerized solution)

---

5. MongoDB-integratie (20/40)

• Expand data validation
  • Add validation for ALL fields (not just required ones)
  • Validate data types, formats, ranges, etc.
• Improve error handling
  • Add robust error handling throughout
  • Handle edge cases and invalid inputs gracefully
• Add advanced queries
  • Create complex queries matching your functional requirements
  • Document which queries serve which requirements
  • Use aggregation pipelines where appropriate

---

Priority Order (Tackle First)

1. Testing (0/40) - This is worth 40 points and currently has ZERO
2. Presentatie (20/50) - Document onion architecture and clarify tech decisions
3. MongoDB relationships (part of Presentatie) - Document schema visually
4. CI/CD improvements (12/20) - Add rollback and containerized MongoDB
5. MongoDB validation (20/40) - Add comprehensive data validation
6. Extra functionality (Full-stack) - Add and document new features

---

Submission Checklist

• All documentation files written (architecture, schema, research)
• Tests written and integrated into CI/CD
• Code refactored to match onion architecture if needed
• Presentation prepared with visuals and demo
• README updated with all technical details
• All 5 rubric areas addressed with evidence

---

References