c m s c 311
f a l l 2 0 0 2
Due Wednesday, Sept. 18, 11:59 PM (just before midnight)
Late Due Date Wednesday, Sept. 25, 11:59 PM (just before midnight)
Posted: September 6, 2002
Read this section frequently to check for updates/corrections/clarifications to the projects. There will be some, because the project description is rather rough right now. However, the methods should be more or less correct.
Please note that *all* programming projects in this course (including this one) are to be done independently or with the assistance of the instructional staff of this course only, unless otherwise specified IN PRINT by official webpages.
Please review the policies outlined on the class syllabus concerning the use of class computer accounts and concerning the University's Code of Academic Integrity. The instructors of this course will review the programs submitted by students for potential violations of the Code of Academic Integrity and if it is believed that a violation has occurred it will be referred to the Office of Judicial Programs and the Student Honor Council.
Hardcoding is considered a violation of academic integrity
Only one person should submit the project, and have all the names on it. Suppose a project allows teams of 2. The two people can work together on a team, and code on the same project. However, teams are expected not to communicate with other teams. Thus, you should treat each team like an "individual" when it comes with helping other teams.
The project is sufficiently short to be done individually. So, you do not have to work in teams.
Should you work in teams, you should try pair programming. In this case, both of you agree to code side-by-side. One person types, the other person looks it over. After a while, you switch off. By discussing what you will do, you will avoid bugs, and hopefully code quicker.
To do this:
To change your finger information, type:
You should ONLY change your name. Please have your first
and last name as you are registered in the system. For example,
if you are registered as "Samir Khuller", please use "Samir Khuller"
rather than "Sammy Khuller" or "Biff Khuller", even if you prefer
to be called "Biff".
Ignore the parts that ask you for your phone number, office, etc. Just hit return, and don't fill anything in.
In addition, you will probably also want to change your password.
Notice the unusual spelling of "passwd".
This will ask for your original password, then your new password, and the new password again. If you use "ssh", it may take a day or so to take effect (it might work right away though). If you use "telnet", the changes should be immediate.
Implement the methods. You may add helper methods, if you want.
You may use STL or any other features you want, provided it compiles and runs under either cxx or g++. A driver will be provided, so you can submit.
See the class syllabus for policies concerning email
Last Modified: Wed Jun 5 10:38:37 EDT 2002