CS5430 Project: Phase I Deliverable (Spring 2013)

The deliverable for this phase is a relatively short document that describes the system your group will build. This document serves two purposes.

• It allows the course staff to check that what you plan to build is a sensible system and is sufficiently (but not overly) ambitious for a course project. Where there are obvious problems, we will ask questions or make suggestions about how to proceed. If there are severe problems then we may invite you to submit a revised document, which we will also review.

• It defines what you will be building and establishes the baseline against which your system will be evaluated. If, in the end, you don't deliver a project with your stated functionality then your grade will suffer. However, you will not receive a higher grade for implementing more functionality than is specified in this document.

Your Phase I deliverable should be submitted to CMS as a .pdf, .txt, .doc or .docx. Use 10 point font or larger, "single" line spacing, and at least 1 inch margins. The entire document should be at most 2 pages (single-sided) and likely will be a lot shorter. A document that does not follow these standards will be returned unread to its authors for re-formatting and receive a grade deduction. (Success in life depends, to a surprising degree, on knowing when to follow instructions and then following them.)

CMS provides a way for you to define your group. Be advised that each group member must take an action in creating a group, and your group cannot submit anything through CMS until the group has been created.

Structure your document as follows.

Title: A short descriptive title for your system. (A cute title that is not descriptive will not receive full credit.)

Group: The list of group members. Give the full name and netid for each.

System Description: A couple of paragraphs describing what the system will do (but not how that functionality will be achieved).

Role of Cryptography: A paragraph explaining how cryptography will be used in the proposed system.

Role of Human Identity: A paragraph describing how the identity of a human user will effect the data or operations that user can perform using your system.

Implementation Target: Explain what programming language will be used and what operating system(s) it will run on, etc.

We will evaluate your Phase I submission against criteria listed below.

• Whether the document you submit contains the required sections and each section contains the required content.

• Whether the description of functions and features is clear and complete.

• Whether the system is making sensible use of cryptography and has a credible need to authenticate human users.

• Whether a reasonable implementation target been selected.

Clarity and correct American or British language style and usage counts throughout, just as it does in the real world. So non-native speakers are urged to have somebody critique their prose.