The material covered in CS132 culminates in a final project, where students work in groups to implement a web application for a client over the course of the semester. Groups typically include four persons with a mixture of designers and programmers appropriate to the project. Projects start a week or two into the semester and continue throughout, with various milestones and reports. The bulk of the design of the project will be done by the end of March, with mostof the project coding being done in April. Projects are due in early May.
We are currently looking for suitable projects for this course!
Please note: A website with static content is not a suitable project. Proposals must have a 'backend' component as well (please refer to the first link for examples of past proposals).
Project sponsors should know what they want done. They should be able to provide their group with appropriate requirements and specifications and any documentation needed to integrate with existing systems. They should be willing to meet with the team or a team representative (in person or by skype, etc.) at least biweekly to ensure the team is on track and to provide the necessary guidance and feedback.
A good project proposal will:
- Briefly state the motivation/purpose.
- Describe typical users and common use case(s).
- Have a clear, bulleted list of minimum requirements.
- Include a rough overview of the technologies required/involved.
- Provide examples (if available).
- Be properly scoped, so as to allow a group of 4 students to do a good job on the project over the course of a semester.
As examples, previous projects included:
- A front end to let spectators provide input regarding music volume and fire status for Waterfire.
- A web site for posting of free cultural events in NYC
- Mobile remote for Shelby.tv
- Food truck locator
- Music player for one or more business locations
- Textbook exchange web site
- Visualizer for Tracelytics
- Web shell for MongoDB
- Polling using text messaging via Twilio
If you would like to submit an application proposal, please fill out this form.
Project submissions should be received before January 25, 2019 to allow us time to review them and get back to you before they are distributed to the students.
Project sponsor should note several things:
- Intellectual Property: Brown's policy is that students own any code they write for a course. Because the sponsor is offering assistance, guidance, and direction, our policy is that sponsors get full, non-exclusive rights to any product produced. Projects can also be specified up-front as open source.
- Obligations: We expect sponsors to provide the students with a well-defined project as well as project direction on a timely basis throughout the semester.
- Working Product: There is no guarentee that the students will conceive the perfect solution or even a workable product. They will be graded on their efforts and you will be asked to provide input into that grading process.
- Continuing Efforts: There is no guarentee of continued development beyond the end of the course by the students involved. If the sponsor wants access to the projects' documentation / code-base or they require the ability of a non-expert to edit, modify, or add content to the site, they should make this clear at the initial meetings with each group and in the project specification.
- Development Timing: Projects will be developed over the course of the semester. Much of the time in February and March will be spent on understanding requirements and designing the front end of the project. Most of the implementation will be done in April and the final demonstration (and sponsor-hand off) will be in early May. Sponsors should not expect a working prototype implementation earlier than mid-April. (Sample web pages and a non-functional prototype will probably be available in March.)