CS-183 Project 2: Group Design Project

Dr. Mark J. Sebern

Version 1.3 (5/5/1999)

CS-183 main page

Schedule

Card image files
(cards.zip)

Dr. Sebern's sample "card display" program
(cardtest.zip)

Marcin Polewski's "card display" class and demo program
(demo.zip)

General lab information

Most of the information on this lab project can be found by following this link.

Specific instructions

The following instructions are specific to this section of CS-183:

Three lab periods (weeks 8, 9, and 10) are allocated for this lab project:
- Week 8 - This lab period is dedicated to the design of the program and classes. Attendance at this lab is mandatory, since the design work will be done in groups (preferably 3 students) and the client (instructor) will be available to clarify the project requirements.
- Week 9 - This lab period is dedicated to implementation of the application.
- Week 10 - This lab period is dedicated to demonstrating and testing the program. Each team's program will be tested and evaluated by another team. It is important that all programs be complete and operational by the beginning of this lab period.
The lab reports should be submitted by email to Dr. Sebern. Please keep a backup copy in case your work gets lost in the email system. The lab reports are:
- Design report (due before the start of class on Tuesday of week 9). Note: bring a hard copy of your design report to class so that we can have a design review.
  - List of team members.
  - Description of each class and at least the public portion of each class definition. Note that a full description of each class, attribute, and behavior is required, though this may be in the form of "internal documentation" (comments) in your class definition.
  - Description of the user interface (GUI or text).
  - One or more use cases describing operation of the program.
  - A brief narrative report describing any problems encountered or remaining questions.
  - A project time log (for each team member) indicating the date and times for each project work period, activity for each period (e.g., requirements study, design), and the total amount of time spent on the project. Summaries should be provided by team member and for the team as a whole.
- Final project report (due one hour before the start of lab in week 10)
  - Updated design report, narrative report, and time log.
  - Source code for your complete program.
- Final report revisions (optional, due before 5PM on Monday of week 11, exam week)
  - Updated final report, incorporating any revisions resulting from the evaluation by the test team. (Note that the primary weight in grading will be on the report as submitted by the week 10 deadline, but some adjustment may be made for defect fixes and enhancements submitted in this final revision.)
The project grade will be determined by considering the following factors:
- Meeting specifications
- Technical quality
- Design documentation
- Internal documentation (comments)
- Program clarity (formatting, etc.)
- Narrative report and time log
- Program demonstration and test output
- Spelling, grammar
- Extra credit
- Timeliness of submission
All team members will also complete a peer evaluation form, which will be used as one factor in assigning individual grades.

If you have any questions, or any part of the assignment is unclear, please consult the instructor.

This page was last updated on September 13, 2001; send comments to Mark Sebern.