Recent Changes - Search:

Home

Is the Laser up?

People

Publications

Calendar

Projects

Spring 2012

Older Courses

Fall 2011

Spring 2011

Fall 2010

Spring 2010

Fall 2009

Spring 2009

Fall 2008

Spring 2008

Fall 2007

HOWTOs

edit SideBar

FPProp

Home Assignments Lecture Blog Resources Project Discussion Group

91.301 Organization of Programming Languages
Prof. F. Martin

Out: April 15, 2009
Due: April 27, 2009

Final Project Proposal

In this assignment, you will produce a plan for your OPL final project.

Please note: Electronic submissions are preferred to paper-based ones (though both are acceptable). If you are submitting electronically, any standard file format is acceptable (e.g., MS Word, MS PPT, OpenOffice equivalents, PDF).

Please submit to assignment 301-fpprop (Final Project PROPosal). Make sure to include your real name or CS username in the filename of your project document! E.g., I might submit a document named fredm-opl-proposal.doc. To submit it, use the following (e.g.):

  submit fredm 301-fpprop fredm-opl-proposal.doc

Guidelines

The final project is worth 25% of your overall class grade, so it should represent a significant work effort.

Here are the things that will make a high-quality project:

  • explicit connection to ideas that were introduced in the course
  • explicit connection to some outside piece of technology (e.g., images, sound, networking, database, etc)
  • an interesting overall concept
  • something that you personally are interested in and care about
  • a writeup that explains what you accomplished
  • demo that lets people (or yourself) interact with your project

The Proposal

The proposal itself is a written document that explains what you are going to do. It should:

  • include a description of what you intend to build
  • describe any proof-of-concept work you have already accomplished
  • have at least one diagram illustrating the major technology pieces of your proposed project
  • discuss your motivations for the project (how you came to select it, what makes it interesting to you, what you hope to gain from working on it)
  • include a schedule of work, for the 21 days starting with Wed Apr 22 (final project is due with in-class demo on Wed May 13)
  • be 3 to 5 pages in length

Here is an example of an excellent proposal. Please take a look at it.

You may wish to start project in earnest work before you turn in the proposal next week. The last 3 weeks of warm-up assignments were intended for that. In any event, it would definitely make sense to do some proof-of-concept work over the next week and use that as the basis of your proposal.

In short: You should be proposing something that you have high confidence that you can achieve.

Grading

The following rubric will be used to evaluate the final project itself. The percentages given are percent of overall class grade, so they total 25%.

5% quality of the proposal document itself (see above for what it should include)
5% degree/quality to which project makes use of concepts taught in the course (please be explicit about this in the project writeup)
5% innovation and creativity in overall concept, including integration with other technologies (please do explain what is interesting about it)
5% quality of final writeup document
5% quality of in-class demonstration of project (with accompanying poster—this will be assigned)

Please note that this week's assignment is to produce the proposal. This assignment alone with worth 5% of your class grade.

Edit - History - Print - Recent Changes - Search
Page last modified on April 21, 2009, at 05:55 PM