✅ Demo video report, including who-did-what part
✅ Up-to-date versions of your user stories, definitions, and model-class design
Your team must create a GitHub release of your source code. The release must follow these instructions.
Your team must submit a video demo and accompanying report. Your video and report must follow these instructions.
Your team may optionally produce a commercial-style video. Your commercial must follow these instructions. Note that the team members who create this video are eligible for A&B points.
For this session, each team will operate a demo booth. One member of your team (the “demo-booth operator”) must run the booth, providing visitors with an interactive demo of your team’s software. The remaining members of your team will circulate about the other booths, acting as visitors. The interactive demo must meet the following grading criteria:
Clearly explain your project to visitors. Assume that visitors have never seen your project before. Thoroughly and clearly explain what problem your project solves and how it does so.
Display the team’s work in the best possible light. Use presentation techniques discussed this semester to present your team’s software in an engaging and compelling way. Also, think about the best way to set up your booth. What equipment will you need? Extra monitors?
Allow visitors to use your project. This is an interactive demo, which means that visitors should be allowed to try out your project if time allows.
Time limit. The demo must be no more than 7 minutes long.
Note that demo-booth operator is an A&B eligible role.
Your team’s user stories, definitions, and database design diagram must all be kept up to date, and the latest versions must be submitted as part of the milestone. These artifacts will be graded using the previously provided rubrics. Note that your team’s wireframes do not need to be kept up to date.
All work contributed to the project must follow the process described in the Project Workflow Instructions document. This process includes full task planning and outcome reporting.
At the end of each iteration, each team member must provide a review of each other team member. Instructions and forms for performing these teammate evaluations will be communicated by email near the end of the iteration.
The grade for each development milestone has a team component and an individual component.
Important! Beware of the following rules that have severe penalties if not followed:
Follow the Workflow: You must follow the workflow such that all your individual work is submitted as pull requests (PRs) and the PRs you submit are clearly work done by you. You will earn 0 points on any milestone (includes both team and individual grade components) that doesn’t follow this rule.
Below are each of the grading items for this milestone, along with their weights. If an item is not submitted at all, 0 points will be awarded for that item.
Scored out of 100 possible points.
Additional deductions: