Project Description

Last modified: Oct 6, 5:43 pm

• A one-paragraph explanation of the motivation for the project. Projects must be designed to solve real problems, since otherwise requirements discovery would not be possible.
• A one-sentence description of the goal of the project.
• The name and email address of each team member.
• The name of the requirements commissioner. The requirements commissioner may not be a member of the project team, since that would change the nature of the requirements discovery process in ways that would not be characteristic of real applications.
• A list of required capabilities. These are the capabilities that are envisioned as necessary in the first complete release of the user interface that is being designed (regardless of whether three prototype iterations will be sufficient to explore them all).
• A list of additional capabilities that might be included in the first complete release of the interface if time allows, or might be considered for incorporation some subsequent release.
• Identification of an available source for any materials (database entries, images, sound files, etc.) that will be needed to demonstrate the capabilities of each iteration of the user interface as it is being developed.

The project description should be turned in by creating a project Web page (on WAM or elsewhere), linking to the project description from it, and sending the URL for the project Web page to the professor and the TA by email before the beginning of class on the date indicated in the syllabus.