Project Proposal

(2 pts, due Mar 17)

Make sure everyone in your team approves of the proposal. Then, only one member needs to submit the PDF of your proposal into the Project Proposal Sakai assignment as described below:

Project Name, Participants, and Workflow

Give the project a good name, and include emails and roles of participants in as much detail as possible. Document how will you work collaboratively on the project. For example, are you going to have weekly meetings outside class? When?

Project Abstract

Include 1-3 paragraphs explaining your project. This abstract should focus on the goal of the project from a user’s perspective rather than the underlying implementation methods you will use.

Project Design

List the underlying technologies and design methods in as much detail as possible. For example, which software, IDEs, packages and modules are you expect to use? What functions are you expecting to create? What is your programming logic?

Project Milestones

List as many verifiable milestones as possible between now and the completion of the project. Identify incremental features. The goal is to work on a project that will allow incremental development. Try to be realistic and stick to them. Also, for the more ambitious projects, try to have a less ambitious but functioning system early on so that if you fall short of your goals you will still have something to show for it.

Reference Material

It is always in your best interest to use code from others whenever possible. If you will be using or modifying significant amounts of code from a third party, mention it here. Standard libraries/imports need not be mentioned, but if it requires a separate download is should be. It is acceptable to read code from others for ideas and syntax, but if you claim you wrote a particular function, you MUST document if any significant portion of it came directly from another source. Also, for projects that require data, you must mention the source of the data.