The goal of this milestone is to have the system finished, polished, and ready to turn over to the customer.
Most of the instructions for this milestone are the same as in the previous milestones. In particular, you must follow these instructions documented in the Milestone 1 & 2 Instructions documents:
As always, don’t forget to rotate presenter duties so each team member gets to present at least once.
Your team must create a commercial-style video of your software, and a README.md file that acts as a “title page” for your project. The commercial video is mainly to provide a “short and sweet” overview of the software you created for the course. The video must meet the following grading criteria:
The focus of video should be on the goals of the software and how it fulfills them. Thus, you should adhere to the following:
The README.md file should be placed in the top-level folder of your repo, so it is displayed on the repo’s landing page in GitHub. The README should display the following in a pleasing fashion (not necessarily in this order):
See the Above and Beyond Points document for A&B points associated with the creation of the video commercial and README file.
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., “/misc/user_stories.docx”). Feel free to leave additional explanations/instructions as sub-bullets.
# Milestone 3 - Instructions to the Instructors
- Team: xxx (Team Name)
- GitHub Repo URL: xxx (URL)
- Commercial Video URL: xxx (URL)
- Demo Video URL: xxx (URL)
- Git Tag for Demo Video Version of Code: xxx (Tag Name)
## File Locations in Repository
- Milestone 3 Individual Assignment Outcomes: xxx
- Who-Did-What Document for Demo Video: xxx
- Up-to-Date Feedback: xxx
- Up-to-Date Plan and Design Artifacts:
- Requirements specifications and their statuses: xxx
- Prioritization and Schedule of Requirements Implementation: xxx
- Architectural design: xxx
- Database design (if system will have a DB): xxx
- Risks and their statuses: xxx
- Quality assurance plan: xxx
- Feedback management plan and setup: xxx
- Collaboration plan: xxx
[ ] Demo video and who-did-what document
[ ] Mentor must have seen demo (live or video)
[ ] Tagged code in VCS
[ ] Up-to-date plan and design artifacts
[ ] Mentor must confirm requirements (and possibly others)
[ ] Up-to-date feedback collection, plans to handle, and outcomes
[ ] Mentor must sign off on
[ ] Individual assignment outcomes
[ ] Instructions to the instructors, submitted to eCourseware dropbox
[ ] Public interactive demo session
[ ] New! Video commercial and README.md (see instructions above)
[ ] Teammate evaluations
Mentors: Please indicate your approval of the following items—but ONLY if you agree 100% with the statement for the item.
If you have ANY disagreement, do not give your approval. Instead, provide the team with feedback, and have them resolve whatever issue is preventing your approval.
[ ] New! I have seen the project’s GitHub landing page (i.e., README) and the commercial-style video for the project embedded therein.
[ ] I have reviewed the final demo of the software, and I have provided the team any feedback I had.
[ ] I have reviewed the requirements specifications, and they are up to date and consistent with my wishes.
[ ] I have reviewed any other plan or design artifacts that I wish to see, and I approve of them.
I have reviewed the team’s feedback management system, and …
[ ] All the feedback I have given them is accounted for.
[ ] I agree with all the team’s plans for handling the feedback.
[ ] I confirm that all outcomes are accurate to the best of my knowledge.
[ ] New! The team has delivered the software to me, and I have received everything that I need from them.