Final Project
The final project will give you a lot of flexibility to design a really cool web application in a team of 2-3 students.
The project will center around improving transportation in the ROC. We'll be using data provided by the Rochester Transit Authority (RTA) for the base project and then whatever you can imagine for the rest (with some TBA technical requirements). We hope to invite some of the RTA folks into class to learn about what you've done, so be creative!
Start thinking about what you'd like to do for your project. Assignments leading up to the final project will give you a base project that has bus routes on Google Maps. You'll likely plot some realtime data - see OneBusAway for inspiration.
The first deadline will be a short (one page) proposal of what you'd like to do for your project, and a list of the team members.
Requirements
While the focus and content is largely up to you (although we'd like you to integrate transit in some way), you will be required to include at least 5 of the following 10 components in your project. You can choose to include more, but you'll be graded on the 5 that you choose and the overall quality of the project.
- Use a Server-Side Framework - use a technology other than HTML/CSS on the server.
- Database - use a database to store and retrieve information.
- AJAX - use AJAX to turn your web pages into dynamic web applications.
- Web Service - use an external web service, mashed up with your own application to create something even better.
- Multimedia - integrate sound or video into your web application to make a richer experience (no, embedding a YouTube video of Rick Astley doesn't count).
- Make an API - make an API so that other developers can use your web site as a service empowering even cooler web creations.
- Design & Evaluate - think carefully about how users will use your site, design a great interface, and evaluate it with real people.
- Accessibility - all projects should be designed in an accessible way, but be particularly clever in exposing information or resources in an inclusive way to count this component.
- Go Mobile - create a version of your project designed to go mobile.
- Server-Side Processing - do processing on the server to prepare for user requests in advance.
Timeline
Project Proposal Due - 2/15/2010
One page outline of what you plan to do, who's on your team, and which of the 5 components you expect to include.
Project Madness - 3/24/2010
In class, each team will be given 2.5 minutes to state their idea, show a mock-up, and sell their idea. You'll be cut off at 2.5 minutes so practice! You can also create a video presentation instead if you'd like.
Project Report - either 4/28/2010 or during Finals Week
Each team will be given 5-10 minutes to explain what they did and show their prototype. Afterwards, they'll be a short period for questions from a panel of distinguished judges (right now just Kyle, Zhuan, and Jeff).