CS 211    Object-Oriented Programming (Section 002 – Fall 2008)

Course Outcomes

- An understanding of basic object-oriented programming concepts and principles.

- An ability to apply basic object-oriented principles and techniques in the development of software systems using a specific programming language.

- An ability to effectively develop software systems using both basic command line tools and sophisticated integrated development environments, and to understand the advantages and limitations of each.

- An ability to successfully perform debugging operations and techniques.

- An ability to perform software development in both individual and team environments.

- An understanding of programming-related references/resources available to software developers and the ability to use them effectively – both in ongoing projects and in the acquisition of new technical skills.

- An understanding of how acquired programming skills facilitate success in upper level CS courses and in various professional environments.


Grade of C or better in CS112


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

n  Telephone: 703-993-1543  n  Office Hours: M/W (12:15 – 1:15), T/R (3:00 – 4:00) or by appt.


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

by John Lewis & William Loftus, © 2007 Pearson Education


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

Email / Blackboard

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


500 points total: 10 Labs (18%), 5 Quizzes (8%) Class Participation (9%), 3 Programming projects (24%), Independent Research Paper (6%), Exams: midterm (15%), final (20%). Final course 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.)                                  


Lecture attendance is required. 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, during instructor/GTA/UTA office hours or via Blackboard discussions.


Lab attendance is required. Students must attend and participate in the lab for which they are registered unless prior permission is granted by lab GTA. Quizzes (unannounced) will be administered during lab sessions. Missed labs result in zero credit for quizzes administered during that session (no make-ups). The lowest grade of the 5 quiz grades will be dropped. Lab assignments are due one week from the start time of the lab in which they were assigned. The lowest grade of the 10 lab grades will be dropped. Lab assignments may be discussed (e.g., algorithms, development strategies, etc.) with other students, but code may not be shared (lab submissions are strictly independent efforts unless specified otherwise by instructor).


Programming projects are considered individual efforts, therefore no sharing of code and/or discussion of problem solution is allowed with anyone except lab GTA, UTA 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 (measured in 24-hour increments from time due). 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 by instructor. Appropriate documentation (as determined by instructor) and requisite permissions are required for make-up exam requests. Picture IDs are required to take all exams. Note: A failing grade on the final exam (<60%) will result in a failing grade (F) for the entire course, regardless of performance on other assignments.

Honor Code

All students are expected to abide by the GMU Honor Code. This policy is rigorously enforced. 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.


If you have a learning disability or other condition that may affect academic performance (and that is documented with the GMU Office of Disability Services), talk with me ASAP to discuss accommodations.