University of Virginia, Department of Computer Science
CS655: Programming Languages, Spring 2001

Manifest: Thursday 22 March 2001
Tuesday, 26 MarchProject Proposal
If you have settled on a project idea, you should turn in Project Proposal on Tuesday containing:
  1. Description of the problem - what will we (meaning the programming languages community) know after you have finished the project that we don't know now? Motivate your project and explain why it is interesting.
  2. Related Work - this doesn't need to be complete yet, but enough to show the problem is relevant and interesting. You should make sure to relate the related work to your project - why is it relevant to what you want to do?
  3. Research Plan - concrete description of what you plan to do including a schedule with concrete milestones.
  4. Evaluation - description of how will you decide if the project is successful.
If you have not yet found a idea for a project, send me an email before midnight Monday explaining the directions you are thinking about, and what you are doing to try and find a good project idea. You will not need to turn in a proposal on Tuesday, but will negotiate with me to turn in a proposal at some later date.

If you have an idea, and its not a good idea, take a nap instead of implementing it.
Alan Kay's Third Law


Read before Tuesday (handed out last time):

Read before Thursday 29 March:

Think Java. Write new applications in Java. Rewrite legacy apps with Java.

Don't upgrade or downgrade. Sidegrade instead to a Java desktop device. Don't get hit with the PC's massively negative ROI.

I don't understand why anybody would be programming in anything other than Java.

Scott McNealy, Open Finance (a Sun publication), Spring 1997.

CS 655 University of Virginia
Department of Computer Science
CS 655: Programming Languages
David Evans