Fundamentals of Computer Science II (CSC-152 99S)


For the remainder of the semester, you will be working on our distributed art auction system. At regular intervals, we will be meeting as a class to discuss particular parts of the system and how they interact.

Clif and I have identified seven key parts of the system.

By Friday, we will assign groups to these projects.

In order to make successful progress on the system, you will need to meet a number of milestones.

By Tuesday, April 20, 1999, you should have a summary of what you expect your portion to do, what classes it will require, and how you your classes will interact with the surrounding classes. For example, ``When the user enters an artists' name in the artist administrator, I will call these methods of these components. The response will be returned to me in this way.

We will discuss these summaries and their implications on Wednesday, April 21, 1999.

By Tuesday, April 27, 1999, you should have a ``skeleton'' for each class you are responsible for building. The skeleton will include the methods headers, their descriptions, and their pre- and post-conditions. You will use stubs for the bodies. Those of you creating GUIs will also need to have the basics built (that is, all the components created and layed-out; the components need not work).

On Wednesday, April 28, 1999, we will discuss these class descriptions and possible GUIs.

By Tuesday, May 4, 1999, you should have a rough implementation of all your classes. Your things should work correctly by themselves.

By Monday, May 10, 1999, your classes should work correctly with the related classes. You will need to coordinate with other groups for testing. We will use lunchtime on Monday to demonstrate the project.

On Friday, May 14, 1999, each group should turn in a four page report on your project. It should summarize the design decisions, give enough information for other people to use your project, and also give enough information for other people to modify your project. Each student is also responsible for a one page report reflecting on the process by which you built the project (what was good, what was bad).


Disclaimer Often, these pages were created "on the fly" with little, if any, proofreading. Any or all of the information on the pages may be incorrect. Please contact me if you notice errors.

This page may be found at

Source text last modified Sun May 9 12:00:31 1999.

This page generated on Sun May 9 12:06:59 1999 by SiteWeaver. Validate this page's HTML.

Contact our webmaster at