General Project Information

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

Specific Instructions

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

• Three lab periods (weeks 5, 6, and 7) are allocated for this lab project:
  • Week 5 - This lab period is dedicated to the design of the program and classes. The design work will be done in groups (2-3 students) and the client (instructor) will be available to clarify the project requirements.
  • Week 6 - This lab period is dedicated to implementation of the graphical user interface and skeleton of the application. Some work may also be done on implementing the rest of the program.
  • Week 7 - This lab period is available to complete and test the program. Please demonstrate your working program to the instructor during this lab or at another agreed-upon time.
• The lab reports 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 5:00pm, Monday, April 12)
    • List of students who contributed to the design.
    • 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 graphical user interface (buttons, text fields, list boxes).
    • One or more use cases describing operation of the program, including button activations, user entries, and program output.
    • A brief narrative report describing any problems encountered or remaining questions.
    • A project time log 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.
  • Interim implementation report (due 5:00pm, Monday, April 19)
    • Updated design report, narrative report, and time log.
    • Documented source code for your partial implementation.
  • Final project report (due 5:00pm, Monday, April 26)
    • Updated design report, narrative report, and time log.
    • Documented source code for your complete program.
    • Test output.
• 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 test output
  • Spelling, grammar
  • Extra credit
  • Timeliness of submission

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.