[ ] Demo video
[ ] Who-did-what document for the demo video
[ ] Version of your code from the demo video tagged in GitHub
[ ] Up-to-date versions of your user stories, design artifacts, and planning artifacts
[ ] Individual assignments and outcomes
[ ] Instructions to the instructors, submitted to eCourseware dropbox
[ ] Teammate evaluations
Similar to Milestone 1, there are three main deliverables for Milestone 2: a demo video, a collection of project artifacts, and a live demo session—this time in public.
You should refer to the Milestone 1 Instructions document for the detailed instructions regarding what each of these deliverables should include and the criteria by which they will be graded. In particular, see these parts of the document:
Demo Video and Who-Did-What Document: Same instructions as last time (still must be 8–10 minutes in length). Demo video and who-did-what document creator will again be an A&B eligible role.
Project Artifacts: Same instructions as last time, except that now the Git tag must be “milestone2”.
Demo Session: Same instructions as last time, except that now the session will be held in public, and the demo length must be 6 minutes. Demo booth operator will again be an A&B eligible role.
Full task planning and outcome reporting must be part of each iteration and milestone. See the Individual Assignment Specification document for detailed instructions.
Since the way to access the various milestone artifacts may vary from team to team, each team must submit a document containing instructions to the instructors regarding how to access each artifact. This document must be submitted to an eCourseware dropbox by the milestone deadline.
Teams must use the following template. Create a Markdown file (i.e., a text file with the file extension .md), and paste in the template below. Each team should submit only one Instructions-to-the-Instructors file that is shared by all team members. For the file locations, give the file name(s) and location(s) of each item in your team’s repository (e.g., /docs/user_stories.md). Feel free to leave additional explanations/instructions as sub-bullets.
# Milestone 2 - Instructions to the Instructors
- Team: xxx (Team Name)
- GitHub Repo URL: xxx (URL)
- Demo Video URL: xxx (URL)
- Git Tag for Demo Video Version of Code: xxx (Tag Name)
## File Locations in Repository
- Milestone 2 Individual Assignment Outcomes: xxx (File location)
- Who-Did-What Document for Demo Video: xxx (File location)
- Up-to-Date Requirements and Design Artifacts:
- User stories: xxx (File location)
- Sitemap: xxx (File location)
- Class diagram of your model: xxx (File location)
At the end of each iteration, each team member must provide an evaluation of each other team member. Instructions and forms for performing these teammate evaluations will be communicated by email near the end of the iteration.
Below are each of the grading items for this Milestone, along with their point values and weights. If an item is not submitted at all, 0 points will be awarded for that item. The top-level bullets specify grading criteria. The sub-bullets indicate standard deductions for errors in a submitted item. The deduction list below may not be complete because there may be mistakes that we did not expect. The deduction for an unexpected mistake will be assessed at the time it’s discovered and will reflect how severe the instructor thinks the mistake is. If the deductions for a grading item total more than the total points for that item, 0 points will be awarded for the item.
20 points with weight of 30%
20 points with weight of 40%
10 of the 20 Communication points
10 of the 20 Communication points
Overall weight of 30%
10 points with weight of 5%
10 points with weight of 5%
20 points with weight of 10%
20 points with weight of 10%