CS 211 – Class Syllabus

CS 211 – Object-Oriented Programming (Summer 2009)

Course Outcomes	• An understanding of basic object-oriented (OO) programming concepts and principles. • An ability to apply basic OO 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 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.
Prerequisite	Grade of C or better in CS112
Instructor	Dr. Heishman •• Office: Engineering (Rm. 5343) •• rheishman@cs.gmu.edu •• Telephone: 703-993-1543 •• M/W (3 - 4 pm) or by appt.
Textbook	Java Software Solutions: Foundations of Program Design (6^th ed.) by John Lewis & William Loftus, © 2007 Pearson Education
Websites	CS faculty site: http://cs.gmu.edu/~rheishman/ •• BlackBoard site: http://courses.gmu.edu
Email / Blackboard	Students *must* use GMU email system for all correspondence with instructor. Email *must* use the following subject format: CS211-B01 : Student Name. Failure to adhere to this policy will result in returned emails. All assignments will be submitted via Blackboard unless otherwise specified.
Grading	500 points total: 6 Labs (20%), 5 Quizzes (8%) Class Participation (7%), 2 Programming projects (20%), Independent Research Paper (10%), Exams: midterm (15%), final (20%). Course grades calculated as follows: • A⁺ (≥ 490 pts.), A (≥ 460 pts.), A^- (≥ 450 pts.) • B⁺ (≥ 440 pts.), B (≥ 410 pts.), B^- (≥ 400 pts.) • C⁺ (≥ 390 pts.), C (≥ 360 pts.), C^- (≥ 350 pts.) • D (≥ 300 pts.), F (< 300 pts.)
Lecture	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. Laptop use is not permitted during lecture.*
Labs	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 of the quiz grades will be dropped. Lab assignments are due one week* from the start time of the lab in which they were assigned (unless otherwise specified by instructor). The lowest of the 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 (*labs assignment submissions are strictly independent efforts unless specified otherwise by instructor*).
Projects	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	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.
Learning Disabilities	If you have a learning disability or other condition that may affect academic performance (that is documented with the GMU Office of Disability Services), talk with me ASAP to discuss accommodations.