HCI 594

Spring 2014

Craig Miller

Project Links

Project Proposal

Due Friday April 18

Requirements

The project proposal should be a report that contains the following information:

  • An overview of the project including needed context
  • A summary of the project's goals
  • An ordered list of proposed methods (e.g. interviews, usability tests) with stated goals
  • A proposed project-related activity that involves the class
  • A detailed schedule of methods, milestones and deliverables

Goals for milestones will vary depending on the project. However, a typical project will have at least one data collection completed by milestone 1, work based on data completed by milestone 2, and revisions completed for the project presentation.

The proposal should clearly indicate how the project will satisfy the project requirements. In addition, milestones should be specific enough to determine if the project is one schedule. However, note that schedule changes are allowed but will need to be documented on future reports. Refer to the course schedule for identifying milestone dates.

Chosen methods should be appropriate for their stated goals. The schedule for the methods should also be appropriate. For example, a survey is not recommend before preliminary research on users has been conducted.

The report has no required format. However, the proposal should be organized so that the required information can be easily found and assessed. Typically the overview and goal summary can be 1 to 2 (single-spaced) pages. The schedule can be tabular and might take one page. In addition, you will probably want to elaborate on the goals for particular milestones or deliverables, which may take additional space. Overall, the proposal will generally be less than 5 pages.

Submission

The design document should use a common presentation format, ideally PDF. Submit the file using the D2L online submission site.

Grading

The capstone proposal is worth 20 points. A rubric for the proposal will be available with the D2L dropbox.