CS 211    Object-Oriented Programming (All Sections – Spring 2008)


Catalog description

Continues focus on problem solving, testing, debugging and introduces object-oriented programming. Topics include classes, inheritance, packages, collections, exceptions and polymorphism. Examples in the course may include the use of basic data structures.


Grade of C or better in CS112


Dr. Ric Heishman – Office: ST2 (Rm. 469), E-Mail: rheishman@cs.gmu.edu,

Telephone: 703-993-1543, Office Hours: M/W (1330–1445), T (1730–1900) or by appt.


Java Software Solutions: Foundations of Program Design (5th ed.)

by John Lewis & William Loftus, © 2007 Pearson Education


CS faculty site: http://cs.gmu.edu/~rheishman/

WebCT site:     https://webct41.gmu.edu/webct/public/home.pl

Email / WebCT

Students must use GMU email system for all correspondence with instructor. Email must use the following subject format: CS211-00x : Student Name. Failure to adhere to this policy will result in returned emails. All assignments will be submitted via WebCT.


500 points total: 10 Labs (20%), 5 Quizzes (5%) Class Participation (10%), 4 Programming projects (24%), Independent Research Paper (6%), Exams: midterm (15%), final (20%). Final grades will be calculated as follows:


¨    A- (³ 450 pts.), A (³ 460 pts.), A+ (³ 490 pts.)             ¨    D  (³ 300 pts.)

¨    B- (³ 400 pts.), B (³ 410 pts.), B+ (³ 440 pts.)             ¨    F  (< 300 pts.)

¨    C- (³ 350 pts.), C (³ 360 pts.), C+ (³ 390 pts.)


Students are responsible for reading and understanding all assigned material (in text, on Internet, etc.), which may or may not be covered explicitly in class. Readings must be completed prior to the assigned lecture. Questions and clarifications regarding material should be presented in class or during instructor/GTA/UTA office hours.


Lab attendance is required. Quizzes (unannounced) will be administered during lab sessions. Students must attend and participate in the lab for which they are registered unless prior permission is granted by lab GTA. Missed labs result in zero credit for all assignments/quizzes administered during that session (no make-ups). Extra credit assignments may be negotiated in cases involving legitimate (documented) absences.


Programming projects are considered individual efforts, therefore no sharing of code and/or discussion of problem solution is allowed with anyone except lab GTA or instructor.

Late submissions

All assignments must be submitted by the deadline to be considered for full credit. Late lab assignments will not be accepted. Late projects will be tolerated, but are subject to a penalty of 20% per day. No assignment will be accepted for credit after last class meeting.

Contested Grades

Contesting of grades on any/all submissions must be requested within one week of the itemÕs return. No changes will be considered subsequent to that deadline.


Exams are closed book/notes unless specified otherwise. Appropriate documentation (as determined by instructor) and requisite permissions required for make-up exam requests.

Honor Code

All students are expected to abide by the GMU Honor Code. All class-related assignments are considered individual efforts unless explicitly expressed otherwise (in writing). Review the university honor code and present any questions regarding the policies to instructor.