CS183 -- Lab 4: Debugging



->Courses
->CS183
-->Homework
-->Examples
-->Quiz 1
-->Lab 1
-->Lab 2
-->Lab 3
->Lab 4
->Electronic Submission
->MSVC++ Info
->STL Info
->MFC/GUI Info
->Tentative Schedule
->Course Policies

[Courses]
[Rich][Home][Rich]
[PHome]

Fall Quarter 2001

Overview

The purpose of this lab is to develop stronger debugging skills.

Acknowledgement

This lab was developed by Dr. Chris Taylor.

Problem Statement

We developed a simplified version of the STL list class in lecture. You should develop a strategy for thoroughly testing the class. You should document and fix any errors that you uncover.

The simplified list class has two helper classes that are required. You will need to download the following files: NodeI.h, NodeI.cpp, IteratorLI.h, IteratorLI.cpp, ListI.h, and ListI.cpp. In addition, you will need to create a test program that will reveal any mistakes in the implementation of the list class or the helper classes.

Logistics

You should select a partner for this assignment. The two of you should work closely together in designing your test program and debugging the code. (I would suggest that you work together rather than splitting up the tasks. In doing so, I think you will find it easier to uncover problems and talk through solutions to your problems.) If you are unable to find a partner, please let me know as soon as possible so that I can find one for you. Each pair should submit one report.

Lab report (due 11:00pm, Thursday of week 10)

The lab report should consist of the following:

  • A list of all of the errors you found in the implementation provided to you.
  • A brief discussion describing the most difficult or interesting error you uncovered and what you did to correct it.
  • A summary of your activity log indicating how much time you spent on the assignment. In addition to the total time spent on the project, please report the time in the following categories:
    • Designing your test program
    • Coding your test program
    • Debugging errors in the provided code
    • Writing report
    • Other
  • Any suggestions you have for how the lab could be improved.
  • The Documented source code for your program. You should also include the six provided source files clearly indicating any changes that you made to them.

As with any report you submit, correct spelling and grammar are required. In addition, your 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.

If you have any questions, consult your instructor.

© 2001 Dr. Christopher C. Taylor Office: CC-27C Phone: 277-7339 Last Updated: October 31, 2001
I am responsible for all content posted on these pages; MSOE is welcome to share these opinions but may not want to.