M06 Final Deliverables

Due Date: Monday May 3, 2026, Wednesday Apr 28, 2026

The culmination of the project involves deploying a fully functional DAIS system accessible through both interfaces, accompanied by a detailed technical report, a demo video, and an in-class presentation and Q&A session.

Goals:

  • Deployed system accessible via chat and batch interfaces.
  • Final technical report (approx. 10–15 pages).
  • 5–10 minute demo video.
  • In-class final presentation and Q&A.

Deliverables:

  1. Ensure your final code is committed and merged into the uat branch of your project repository.
  2. Upload the following files to iCollege:
    1. Technical Report (PDF) — approx. 10–15 pages covering the full project lifecycle.
    2. Demo Video — a 5–10 minute recorded demonstration of your system covering the same content as the in-class presentation:
      • Briefly cover the motivation and solution (what the DAIS solution does)
      • Brief overview of system architecture and implementation details; highlight the elements that are unique to your solution
      • Demo of the document processing pipeline, batch evaluation, and interactive user interface. Use the cooking-show time-lapse: show starting the program in one window and the running program in another
      • Discuss performance improvements based on the evaluation
    3. In-Class Presentation (PPTX or PDF) — slides for your final presentation.
  3. Deliver an in-class final presentation and Q&A session covering the same content as the demo video:
    • Briefly cover the motivation and solution (what the DAIS solution does)
    • Brief overview of system architecture and implementation details; highlight the elements that are unique to your solution
    • Live (or recorded) demo of the document processing pipeline, batch evaluation, and interactive user interface
    • Discuss performance improvements based on the evaluation

Milestone Document:

GoalRequirements
Deployed DAIS SystemDescribe the deployed system: How are the chat and batch interfaces accessed? What improvements from prior milestones are reflected? Include instructions on how to access and run the system.
Technical ReportProvide a comprehensive written report covering the full project lifecycle: problem definition, system design, data pipeline, evaluation methodology, results, and conclusions.
Demo VideoRecord a 5–10 minute demo video covering: (1) motivation and what the DAIS solution does, (2) system architecture and implementation details with emphasis on unique contributions, (3) demo of the document processing pipeline, batch evaluation, and interactive user interface, and (4) performance improvements based on the evaluation.
In-Class PresentationPrepare a final presentation with the same scope as the demo video — motivation and solution, architecture and unique implementation details, live (or recorded) demo of the pipeline/batch/UI, and performance improvements from the evaluation. Be prepared for Q&A.

Evaluation:

#CriterionDescriptionPoints
1Deployed DAIS SystemA fully functional DAIS system is deployed and accessible through both the chat and batch interfaces. The system reflects all improvements from prior milestones and is stable enough for live demonstration.40
2Technical ReportA comprehensive written report covering the full project lifecycle — problem definition, system design, data pipeline, evaluation methodology, results, and conclusions — is well-structured, clearly written, and accurately reflects the system as built.40
3Demo VideoA 5–10 minute recorded demo video briefly covers the motivation and what the DAIS solution does, gives an overview of the system architecture and implementation details (highlighting unique contributions), demonstrates the document processing pipeline, batch evaluation, and interactive user interface, and discusses performance improvements based on the evaluation.20
4In-Class PresentationThe in-class presentation mirrors the demo video — motivation and solution, architecture and unique implementation details, live (or recorded) demo of the pipeline, batch evaluation, and interactive user interface, and performance improvements based on the evaluation. The team handles Q&A with depth and clarity.20