CS112 – Intro to Computer
Programming (Spring 2009 –
Section 002)
Course
Outcomes |
- An ability to use procedural
programming language concepts including expressions, decision statements,
simple data types, boolean logic, input/output,
loop constructs, and procedures. - An ability to combine
programming techniques to solve problems of varying degrees of difficulty - An ability to refine computer
programs through testing and debugging to ensure proper operation. - An ability to find and
understand programming language documentation to learn new information needed
to solve programming problems. |
Prerequisite |
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. |
Instructor |
Dr. Heishman ð Office: ST2 (Rm. 469) ð E-Mail: rheishman@cs.gmu.edu ð Phone: 703-993-1543 Office Hours: M/W (10:15
– 11:15, 12:00 – 1:00), W (6:00 – 7:00) or by appt. |
Textbook |
Python
Programming, for the absolute beginner (2nd ed.) by Michael Dawson |
Websites |
CS faculty site: http://cs.gmu.edu/~rheishman/ ð Blackboard: http://courses.gmu.edu
|
Email /
Blackboard |
Students must
use GMU email system for all correspondence with instructor. Email must
use the following subject format: CS112-002 : Student Name (Failure to adhere to this policy will result in returned emails).
All assignments will be submitted via Blackboard. |
Grading |
500 points total: 10 Labs (18%), 5 Quizzes (8%) Class
Participation (10%), 3 Programming projects (24%), Midterm Exam (15%), Final
Exam (25%). 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.) |
Readings |
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. |
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 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 (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 algorithms or 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 |
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. |