Winter 2001-2002

Overview

In this lab, you will modify your program from lab 4 to use a hash table (developed in lab 5) to store the dictionary instead of the STL set.

Procedures

Simply do what is explained in the overview above. Once this has been accomplished, you may modify your program as much as you like. You are not required to use the hash table or the set in your final implementation. However, if you choose to do this, you must justify the changes you made and be prepared to demonstrate the hash table version if asked.

Remember that extra credit will be awarded to the team that produces the best wordsearch game by the beginning of the week 10 lab. The best game will be determined by a class vote during the last class meeting in week 10.

Lab report (due 11:00pm, Thursday, February 14)

Please use this XML template as a starting point for your report. Your report should include:

• A brief description of what you learned, a discussion of the differences observed between your set and hash table implementations and any special features your program has.
• A discussion of how you worked together as a team.
• 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:
  • Design
  • Coding
  • Debug (before you think it's working)
  • Test (after you think it's working)
  • Documentation
  • Other
• Sample program results for lab6a.txt and lab6b.txt. Please use 285msoeloginL6.txt as the filename (be sure to change msoelogin appropriately).
• You should create a zip file, named 285msoeloginL6.zip (fix msoelogin) containing the results file and all of your project files. (I should be able to unzip the file, load, compile, and run your program.) To save space, please delete the Debug and/or release subdirectories before zipping up your project.

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.

Your grade will depend on quality of design, clarity of code and documentation, as well as whether your program produces the correct results. If you have any questions, consult your instructor.