Syllabus: CS 310 Computer Science III, Fall 2002

Course Content

Course topics include, but are not limited to the following:

• Introduction to the Standard Template Library
• C++ features: inheritance, polymorpism, abstract classes
• Heaps and heap sort
• Hashing
• Trees - AVL trees, B-trees, Red-Black trees
• Recursive sorting algorithms
• Graphs

Prerequisites: Grade of C or better in CS 211.

• C++ Syntax and Semantics, Makefiles, and Unix
• Abstract Data Types and C++ Classes
• Big-O Notation for algorithm analyses
• Static and Dynamic Memory Allocation
• Recursion
• Simple Data Structures: Linked Lists, Stacks, Queues, Binary Trees
• Software Reuse with Templates
• O(N2) Sorting Algorithms

Textbooks

• Required: Data Structures and Program Design in C++ Kruse, Robert L. and Rybe, Alexander
• Required: C++ Primer, Lippmann and Lajoie
• Required: STL Programming from Gound Up, Schildt
• Required: Mythical Man-Month: Essays on Software Engineering, Brooks
• Recommended: Just Enought Unix, Anderson

WebCt

Grading: Percentages within the ranges given will be determined by individual instructors.

• Programming 40-50%
  You will be given 3 or 4 data structure oriented programming assignments, which may be weighted differently. These are to be individual efforts, meaning that no code sharing or discussion of problem solutions with anyone except me or the TA. You may not incorporate code written by others, such as can be found on the Internet or any of the numerous CS books. Documentation is required.

  You will be given credit only for code that works. This means that you should code and test functions as you write them, not code the whole thing and then try to get it to work.
  You may develop programs using any computer system you have available. If you plan to program at home, it is recommended that you download the cygwin environment from RedHat. The URL is sources.redhat.com.cygwin. Follow the install link. If you are running linux on your computer, you can down-load the current release of GNU GCC from http://gcc.gnu.org/. Please note, however, that submitted projects must run on the g++ compiler available on osf1, unless otherwise specified by your instructor. Students must have an account on osf1.gmu.edu.
  You are expected to backup and submit/resubmit your program as you get different pieces working. The submit program keeps the last 2 versions you submit. Failure to do this may result in your getting a zero on a program instead of partial credit if last minute problems occur. Note that accidently deleting your program, having problems connecting, problems compiling, etc., will not be accepted as excuses. It is important that you not touch your programs once you have done your final submission: If there are submission problems, consideration for credit will only be given if it can be verified that the programs were not changed after being submitted.

  You will have approximately 3 weeks to do each project. Late programming assignments will be penalized 10 points per day. No extra credit points, when available, will be given to late projects. Individual requests for extensions will not be granted. Once grades are posted, students have one week to contest the grade--beyond that the grade will not be changed.
  

• Homeworks and Quizzes 0-15%
  Some assignments may involve some programming but will be less intensive than the regular programming assignments. Assignments will not be accepted late; No-makeup quizzes are allowed.
  

• Midterm(s) and Final 40-50%
  You must have a written excuse (doctor's note, for example) to miss an exam. You must pass the Final to get a C or above in this course. Once a test is returned, you have one week to contest the grade-- beyond that the grade will not be changed. Note that the week starts when a test is returned to the class, which may or may not be when you choose to pick yours up.
  

• IncompleteA request for an incomplete (IN) will only be considered in the final quarter of the course (all assignments up to and including the 3rd project must have been turned in and no additional work on these will be accepted). Request must be made in writing, accompanied by a note from a doctor or employer and applicable contact information.

Projects

• Project 1          How to create makefile that produces multiple executables          Grade point distribution
• Project 2          Updated to include Part 2 and a sample Print function --10/3         Sample run with mountain data
• Project 3          Updated 10/23           bitset tutorial           Extra Credit options
• Project 4           Grading and Extra Credit option

  Honor Code

  You are expected to abide by the honor code. Programming assignments are individual efforts and may be checked for cheating by any available means. Cheating cases will be referred to the Honor Committee. Any student found guily of an Honor Code violation will receive an F in the course. Students are expected tp be familiar with:

  • GMU HonorCode
    
  • CS Honor Code Policy
  • GMU Responsible Use of Computing Policy

  Instructors

  Prof. Rahul Singh
  Office: S&T II, Rm. 229, Phone: 703 993-3176;
  Office Hours: Tues: 4:30pm - 6:30pm, Thurs: 5:00pm - 6:00pm
  email: rsingh9@cs.gmu.edu
  
  Prof. Kevin Mayo
  email: Kmayo@cs.gmu.edu
  
  Prof. Tucker Maney
  Office: S&T II, Rm. 469
  Office Hours: See Home Page
  email: maney@cs.gmu.edu
  
  

  Teaching Assistants

  TAs of Other 310 Sections Students can seek help from the TAs of other sections during their respective office hours. However, each TA will always serve the students of his/her own section first. On the other hand, the TA of another section is obliged to help you during office hours if there are no students from his/her section. TAs of other sections are not obliged to reply to your emails.

  TAs a(nd UPAs if funding permits) have been instructed to restrict the time they spend with any one student to 10 minutes if other students (from any class) are waiting. Students seeking assistance from a TA or UPA are expected to bring a hard copy of their code. If the code compiles but doesn't run correctly, students are expected to bring a typescript of a debugging session.

  • Section 1: Zhongji Tao        email:ztao1@gmu.edu
    Office Hours: Wed: 7:30-9:30pm, Thur: 2:30 - 4:30pm ST 2 -Rm 365 Note: Zhongji's office hours will start the week of Sept 3rd.
  • Section 2: Billy Wagner        email:wwagner@gmu.edu
    Office Hours: Wed: 1:00pm - 3:00pm, Thur: 4:30pm - 6:30pm, ST 2 -Rm 365
  • Section 3: Naveen Nallannagari        email:nnallann@gmu.edu
    Office Hours: Mon: 10:30 - 12:30am, Thur: 4:30 - 6:30pm, ST 2 -Rm 435
  • Section 4: Jin Liu        email:jliu6@gmu.edu
    Office Hours: Tues: 7:30pm - 9:30pm, Fri: 3:00pm - 5:00pm, ST 2 -Rm 365

  Undergraduate Peer Assistants

  • Ed Velez, evelez@gmu.edu
    
  • Victor Semenov, vsemenov@gmu.edu Office Hours: 3-5pm Thursdays.

  Important Dates

  • First class: Aug 26
  • Drop deadline without tuition liability: Sept 4
  • Add deadline: Sept 10
  • Drop deadline: Sept 27
  • Columbus Day Break: Oct 14th (Monday classes meet on Tuesday)
  • Thanksgiving Recess: Nov 27-29
  • Last day of class: Dec 7
  • Final Exam Period: begins Dec 10