CS112 – Intro to Computer
Programming (Spring 2010 –
Lecture Sections 001 & 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 |
Satisfaction of prerequisites for MATH 113 |
Instructor |
Dr. Heishman / Office:
Engineering (Rm. 5343) / Email: rheishma@gmu.edu / Phone: 703-993-1543 Web: cs.gmu.edu/~rheishma
/ Office Hours: T (2-4 PM), W (4:30-6:30 PM), R (1:30-2:30 PM)
or by appt. |
Textbook |
Python
Programming, for the absolute beginner (2nd ed.) by Michael Dawson |
BlackBoard |
http://courses.gmu.edu - All assignments must be submitted
(per published deadlines) via BlackBoard. Class
schedule, materials, assignments, grades and other relevant documents are
available here. |
Email |
Students must use GMU email system for all correspondence with instructor. Email must use the following subject format: CS112-00x(Name) (Failure to adhere to this policy will result in returned emails). |
Grading |
500 points total: 8 Labs (21%), 5 Quizzes (8%), Class
Participation (7%), 2 Programming Projects (24%), Midterm Exam (15%), Final
Exam (25%). Final course grades will be calculated as follows: |
|
-
A+ (>= 490 pts.), A (>= 460 pts.), A- (>= 450 pts.)
- D (>= 300 pts.) -
B+ (>= 440 pts.), B (>= 410 pts.), B- (>= 400 pts.)
- F (< 300 pts.) -
C+ (>= 390 pts.), C (>= 360 pts.), C- (>= 350 pts.) |
Participation |
Students are expected to attend and actively engage in both
lecture and lab sessions. |
Lecture
/ Readings |
Students are responsible for reading and understanding material
referenced in class schedule, which may or may not be explicitly covered in class.
Readings must be completed prior to the assigned lecture/lab. Questions and
clarifications regarding material should be presented in class, during
instructor/GTA/UTA office hours or via Blackboard discussions. All electronic devices must be turned off during lecture. |
Lab |
Students must attend and participate in the lab section for which they are registered, unless prior permission is granted by lab GTAs. 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 5 quiz grades will be dropped from the overall class grade calculation. |
Programming Assignments
|
Lab programming assignments are due one week from the start time
of the specific lab section in which they are assigned. The lowest of the 10
lab grades will be dropped from the overall class grade calculation. Late lab
programming assignments will not
be accepted.
|
Programming Projects
|
Assignments must be submitted by the deadline to be considered
for full credit. Late projects will be tolerated, but are subject to a
penalty of 20% per day (measured in 24-hour increments from time
of deadline). No assignments of any type will be accepted for credit after
last class meeting or deadline. |
Contested
Grades |
Contesting of grades on any/all submissions must be requested
within one week
of the item's return. No grade 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 and
scantron sheets 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). Lab
assignments (e.g., algorithms, techniques, etc.) may be discussed with other
students, but code may not be shared. Projects may not be discussed with anyone
other than the instructor/GTA/UTAs. Acceptable
references are restricted to those expressly listed in the assignment/project
specification. Review the university honor code and discuss any questions
regarding the policies with instructor. |
Learning |
Students with a learning disability or other condition (documented with GMU Office of Disability Services) that may impact academic performance should speak with instructor ASAP to discuss accommodations. |