Give the project a good name, and include emails and roles of participants in as much detail as possible. You are free to work with people doing projects in other classes, but be specific about who will be involved in the project and their level of involvement.
Document how you will work collaboratively on the project. Weekly meetings outside class, when? If using version control software, a mailing list, or a wiki, provide the link so others can potentially help.
Project Abstract:
Include 1-3 paragraphs explaining your project. Consider a short “executive summary” that can be used when you post the PDF. This abstract should focus on the goal of the project from a user’s perspective rather than the underlying implementation methods you will use.
Please provide at least one figure/visual demonstration/screenshot with an appropriate caption.
Project Design and Milestones:
List the underlying technologies and design methods in as much detail as possible, e.g. which programming languages, APIs, modules, server-side configurations, and client-side hardware/software you expect to use.
List as many verifiable milestones as possible between now and the completion of the project. Identify incremental features. The goal is to produce a project that will allow incremental development.
Related projects:
Please list and provide contrasting detail for at least two related tutorials, approaches, or sites accessible online. You don’t have to do something new, but aim to be unique if possible. Differentiate approaches that are commercial vs freely available as well as those that are closed vs. open source.
Project Name, Participants, and Workflow: