CS112 – Intro to Computer Programming (Summer 2008, M/W 1:30-4:10, R-A111)


Catalog description

This course introduces the use of computer programming as a problem-solving tool. Topics in procedural programming include expressions, control structures, simple data types, input/output, graphical interfaces, testing, debugging, and programming environments.


Qualification for MATH 113 or MATH 108 on the MATH placement test offered through the Testing Center or a grade of C or better in MATH 105.


Dr. Heishman

Office: ST2 (Rm. 469)  n  E-Mail: rheishman@cs.gmu.edu  n  Telephone: 703-993-1543

Office Hours: M/W (12:15 - 1:15) or by appt.


Python Programming, for the absolute beginner (2nd ed.) by Michael Dawson

© 2006 Thomson Course Technology


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

Blackboard: https://gmu.blackboard.com/webct/logon/20147487001  

Email / Blackboard

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


500 points total: 5 Labs (20%), 5 Quizzes (5%) Class Participation (10%), 2 Programming projects (30%), Midterm Exam (15%), Final Exam (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.)


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. 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. Lab assignments may be discussed (e.g., algorithms, development strategies, etc.) with other students, but code may not be shared (labs assignments are strictly independent efforts unless specified otherwise by instructor).


Programming projects are considered individual efforts, therefore no sharing of code and/or discussion of algorithms or 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 by instructor. 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.