Project Milestone 3: Alpha

Due: Wednesday, April 6, 10:00 pm through CMS.
Presentation: Friday, April 8.

Complete another project sprint and ship the latest increment of your system to the course staff. Your alpha milestone should exhibit some completed security functionality, though of course we don't expect all your security functionality to be finished.

In this and future deliverables, you will be increasingly evaluated on the quality of the system you deliver. Note that we were quite lenient with system and code quality in the prototype deliverable.

Submission

Submit a PDF containing your updated Requirements Document. As in Milestone 2, the document should contain your personnel, system purpose, threat analysis, security goals, essential security elements, and system backlog (both completed and uncompleted items). All of these should continue to be updated throughout the project.

Your group might have been asked during your prototype presentation to include a new section in your Requirements Document with information peculiar to your system and its security. If so, make sure to include that information in your updated document.

Also submit a zip file containing the source of your system. Include a plain text file named "README" in root of your source detailing how to compile and execute your system on our own machines.

Presentation

Your group will present your system to the course staff on Friday, April 8. All members of your group should plan to be present. Details on times and locations will be announced later.

The presentation and demo will proceed essentially as in Milestone 2. However, the alpha presentation will be scheduled for an hour-long slot. Expect to give a talk of around 10–15 minutes, a longer demo, and have a longer Q&A session.

Testing: As part of your talk, discuss your approach to testing your system. You might discuss your test plan, test cases, code coverage, etc.

Code Reviews: Your presentation will include a code review. We will spend significantly longer on that code review than we did during your prototype presentations. The readability of your code matters, including documentation and simplicity of code.

You should submit your sprint report (through CMS) on the same day as your presentation.