Administrative Policies for PROST Spring 2001

Lectures and Reading Assignments

Attending lectures is completely voluntary. The lectures and the assigned text are intended to be complimentary. The reading assignments are also voluntary.  Both are strongly recommended.  However, since there is no exam, there will be no questions on this material.  If you are just out for a grade, then you probably do not need to bother with either.  However, I do consider this material an essential part of the course and if you do not work through it, you will really be missing out.  I will also attempt to have several  guest speakers talking about topics that are intended to broaden your understanding of software development and programming style. Exact dates and topics for these invited talks will be announced during the course.

Finally, note that lectures will be conducted in English. Feel free, however, to ask questions in Swedish. Also, if there are technical terms that you do not know, please do not hesitate to ask.


There will be a course newsgroup where you can feel free to post any questions you might have about the course material or project assignments. These questions should be fairly specific. Both your questions and the answers to them will be posted for all to see. Never be embarassed about asking questions. Remember: The only stupid question is the one you do not ask! Please check the newsgroup frequently. You never know what interesting questions and answers you might find. Details on how to use the newsgroup will be announced shortly.

Feel free to come and talk to me (Rand) about any problems you might be having.

Project Assignments

You will be divided into groups of 2 and assigned one of the following programming projects (by the course management):
  1. Data Base Management System (tool for constructing, viewing and maintaing data bases).
  2. Spreadsheet Tool.
  3. Word Processor.
  4. Drawing Program.
  5. Personal Organizer
In each case you will be expected to show your tool in action in a convincing way.  I strongly suggest that you go out and look at existing tools to get some ideas about functionality and documentation.  Here is your chance to do it right!  When deciding how extensive your program should be (i.e., its scope), you must consider the following question:  What is the essential functionality of the application.  By essential functionality I mean those functions that make your application what it is and without which you could not really use the name.  For example, you could hardly call your application a word processor if it did not allow the user to cut and paste text.  Part of the exercise is to identify this essential functionality in a reasonable way.

Your programs will be implemented in Java.

During the course you will be expected to "hand in" the following documents:

  1. Requirements Analysis (pdf version of the lecture slides describing the required document) - due Friday, March 30
  2. Design Document - due Monday, April 9
  3. Implementation Document - due Monday, May 7
  4. Final Report - Friday, May 18
We will not accept printed copies of these documents.  All documents must be prepared either as html documents that can be read in a web browser or as PDF files.  In each case, these files must be in your public directory so that we can look at them.  To "turn in" a document, you will e-mail the address of the document to one of the four reviewers listed below.  Your reviewer is determined by your Group Number as specified on the team assignments page.  Feedback on your work, if any, will be sent to you by e-mail.

Groups 1 - 5:  Karim Oukbir
Groups 8 - 12  Joel Brynielsson
Groups 6, 7, 13 - 15  Rand Waltzman

E-mail must be time stamped 1700 on the date due.

You must be prepared to demonstrate your code by Monday, May 14.  There are labs scheduled between 9AM and 2PM on that Monday.  That is where we will have the demonstrations.  We will try to get you all in then.  If not, there will be some extra time scheduled during the week.  These times will be announced later.


There is no tenta for the course.

Final Grade

The final course grade will be computed as follows:

First, your final final project must be acceptable in order to pass the course.  This means both the written report and the demonstration that you will be required to give.  An acceptable report or an acceptable demonstration alone will not do it.

Second, assuming that your final project is acceptable, your grade will be determined by the number of written assignments (see Assignments section above) that you got in on time and passed according to the following schedule:

0 or 1 passed  -->  3
2 passed  -->  4
3 passed  -->  5