Your project proposal is your first good opportunity to get feedback from course staff on your project idea. You should tell us who is in your project group, what site you plan to build, with what technologies you will build it, and why your idea is cool. Your goal is to describe your project to us and convince us that it is appropriate technologically and an appropriate size for this course.
Writing your proposal should not be an onerous task; the proposal should be short (~1 page). For most projects the proposal should be just prose, but you can include simple wireframe sketches if you think they will help describe your ideas. Projects should be interactive -- typically from a web browser -- and must store and retrieve data at a web server. You may use technologies other than those we've covered in class, but your proposal should justify your choice if you do not use traditional web and servlet technologies.
Ideal projects are scalable in size. Even the best-planned projects run into technical difficulties, project partners get sick, OS comes due, etc. Once you have a basic project idea, you should think about how you might scale the project to be bigger or smaller as necessary. What features can you cut? What features are critical? If the project might be too small, how can you make it bigger? (Hint: the Web is a good platform for collaborative interactions.)
Please submit your proposal by committing a .txt, .pdf, .ps, .html, .doc, or .docx file to your trunk/project-proposal directory. You and your partner(s) may hand in a single copy of the proposal to one of your repositories.
Last updated: Thu Sep 27 13:38:31 -0400 2012 [validate xhtml]