Project Milestone 1: Requirements

Due: Wednesday, February 16, 10:00 pm through CMS.
Presentation: Friday, February 18.

Prepare a Requirements Document that contains the following two parts:

• Part I: Functional requirements
• Part II: Security requirements

This will be a living document: you will continue to update it in the remaining milestones of the project. It is also a critical document, because your final system will be evaluated, in part, by the course staff against your requirements.

Personnel

The beginning of your Requirements Document should identify your group members (including names, netids, and emails) and your Project Manager.

In addition, you should now identify one person as your Requirements Lead; this shouldn't be the same person as your Project Manager. The Requirements Lead is responsible for

• maintaining the Requirements Document throughout the project,
• keeping the group focused on requirements throughout development,
• reprioritizing requirements as necessary,
• deciding whether implemented functionality satisfies a requirement, and
• being the final arbiter of requirements questions inside the group.

Submission

Submit a single PDF file containing your Requirements Document.

Presentation

Your group will present your requirements to the course staff on Friday, February 18, in Upson 4124 (Dr. Clarkson's office). A signup sheet for time slots will be posted outside UP 4124 after class on Friday, February 11. Your presentation will last 30 minutes. All members of your group should plan to be present.

Your presentation will proceed in two phases and will be evaluated against the following criteria. In the first phase, you will give an uninterrupted talk of 15 minutes using Powerpoint slides. When it comes to slides, less is more: use short, telegraphic phrases, and use figures instead of text where possible. Rehearse your presentation well, because the time limit will be enforced, and the quality of your talk counts. The talk may be given by one member of your group, or you may "tag team." Your talk should give us an overview of your Requirements Document, including your system purpose, the most important functional requirements, your threat analysis, and the most important security requirements. You should also clearly explain how you are covering the "Essential Security Elements."

In the second phase, we will hold a question and answer session of 15 minutes. We ask; you answer. Anything about your Requirements Document is fair game. We may direct questions to any member of your group.