Syllabus: CS 112 – Intro to Computer
Programming
(Fall
2011 – Lecture Sections 001, 002, 003, 005)
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. |
Prerequisite |
C or better in MATH 104, MATH 105 or
MATH 113, or specified score on math placement test |
Corequisite |
CS 101 (waived for non–CS majors) |
Professor
Contact Information |
Dr. Mark Snyder Office: Engineering Rm. 5346 Email: msnyde14@gmu.edu Office Hours: T (2 - 4 PM) or by
appt. |
Textbook |
The Practice of Computing Using
Python by William Punch & Richard Enbody © 2011
(An eText version is available) |
Course
Materials |
BlackBoard (courses.gmu.edu)
– All assignments must be submitted (per published deadlines) via BlackBoard. |
Email |
Students must use GMU email system
for all correspondence with professor (using the following email subject format:
CS112_00x_NAME |
Grading |
500
points total: 105 pts: 7 Programming
Assignments (21%) (drop lowest of 8)
40 pts:
4 Quizzes (8%) (drop one lowest of 5) 35 pts: Class Participation (7%) 120 pts: 2 Programming
Projects (24%)
75 pts: Midterm Exam (15%) 125 pts: Final
Exam (25%). Final course grades are calculated as
follows:
B+ (>= 440 pts.) B (>= 410 pts.) B- (>= 400 pts.) C+
(>= 390 pts.) C (>= 360 pts.) C- (>= 350 pts.)
D (>= 300 pts.) F (<
300 pts.) |
Class
Participation |
Students are expected to attend and
actively engage in both lecture and lab sessions. Three absences (total, lectures
and labs combined) are excused without question. Additional absences require
acceptable documentation. Students must arrive on time to log participation
for a lecture or lab session. Take notes – a significant portion of the
information disseminated during classroom sessions are not delineated on
slides. |
Class
Policies |
Students are expected to arrive at
lecture and lab sessions on time. On rare occasions when tardiness is
unavoidable, enter the classroom quietly and sit in the rear to avoid disruption
of class proceedings. Show courtesy to your fellow students and to the
lecturer conducting the session. |
Lecture |
Students are responsible for reading
and understanding material referenced in class schedule, which may or may not
be explicitly covered during lecture. Readings must be completed prior to
lecture. Questions and clarifications regarding material should be presented
in class, during professor/GTA/UTA office hours or via Blackboard
discussions. All electronic devices must be turned off or silenced 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 except for excused absences). 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 8 lab grades will be dropped from the overall
class grade calculation. Late lab programming assignments will not be accepted.
Programming assignment specifications (e.g., algorithms, techniques, syntax,
etc.) may be discussed verbally with other students, but code may not be
shared. All resources used in the assignment must be listed in the code
header. Sharing of code or use of code from any unapproved resource
constitutes an Honor Code Violation. When in doubt – ask. |
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 final exam. Projects may not be discussed with anyone other than
the instructor, GTAs, UTAs and Peer Advisers. Acceptable references are
restricted to those expressly listed in the project specification. Use of any
unapproved resource constitutes an Honor Code Violation. Review the CS
Honor Code Policies and the CS
Statement on Academic Integrity. When in doubt – ask. |
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, or after the final exam meeting. |
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.
We take this policy very seriously and it is rigorously enforced. All
class-related assignments are considered individual efforts unless explicitly
expressed otherwise (in writing). Students should also review and understand
the CS
Honor Code Policies and the CS
Statement on Academic Integrity. Any questions regarding these policies
should be discussed with the professor. |
Learning
Disabilities |
Students with a learning disability
or other condition (documented with GMU Office of Disability Services) that
may impact academic performance should speak with professor ASAP to discuss
accommodations. |