General Project Information

Most of the information on this lab project can be found here.

Specific Instructions

The following instructions are specific to CS-183 section 2:

• 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. The design work will be done in groups (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 design report should be in hardcopy form and brought to class on Monday, May 3. The final report and optional report should be submitted electronically following the Electronic submission guidelines. (You may wish to consult the sample report before submitting your report.) Be sure to keep copies of all your files, in case something gets lost. It may be wise to keep a diskette backup as well.
  • Design report (due 9:00am, Monday, May 3) 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 9:00am, Monday, May 10)
    • Updated design report, narrative report, and time log.
    • Documented source code for your complete program.
  • Final report revisions (optional, due 5:00pm, Friday, May 14)
    • 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 May 10, 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 and submission guidelines
  • Technical quality
  • Design documentation
  • Internal documentation (comments)
  • Program clarity (formatting, etc.)
  • Narrative report and time log
  • Program demonstration and time log
  • Spelling and 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 created by Dr. Christopher C. Taylor and is based heavily on material developed by Dr. Mark J. Sebern.