CS 3302 (Winter 1998) Class Project

There will be a team-based class project. Here are the broad parameters:

You will complete the implementation of a useful software package in Java.
You will do requirements analysis with a real customer, using state-of-the-art requirements discovery techniques. You will probably not understand the application area very well and the customer will want to change his mind about features.
You will plan the project and analyze the risks in your plan, developing contingency plans if necessary. You will be responsible for holding to your plan. (This does not mean that you can't re-plan at any time if that is necessary.)
You will design an object-oriented solution to the customer's problem and will be expected to document that design and keep to it.
You will apply stringent quality assurance techniques in the development of your solution and will test it thoroughly.
You will get frustrated but will have a lot of fun.

Grading team projects is always an issue of concern to students. Course grading criteria are dealt with in the FAQ.

Tell me more about the project

The application is described in the Customer Requirements outline. This is a vague statement of need and is totally inadequate as a problem specification from which you can design and implement a solution. (You will be responsible for writing such a document yourselves.) However, it should be a good starting point for thinking about the customer's requirements.

Tell me more about the development process

You will follow the methods described in the textbook. Where there is a choice of methods, you will either be told which to use or you will be required to make an informed decision that you can justify if asked. Other guidelines will be provided in the course handouts.

Go back to 3302 home page.

Colin Potts

potts@cc.gatech.edu