Syllabus: CS 211 – Object Oriented
Programming
(Spring
2012 – Lecture Sections 001/H01, 002, 003)
Course
Outcomes |
- An understanding of basic object-oriented (OO) programming
concepts and principles. - An ability to apply basic object-oriented 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 ability to perform software development in both individual
and team environments. - 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 CS 112 |
Professor
Contact Information |
Dr. Mark Snyder Office: Engineering Rm. 5346 Email: msnyde14@gmu.edu Office Hours: Wed (1 - 4 PM) or by
appt. |
Textbook |
Java Software Solutions: Foundations of Program Design (7th ed.) by John Lewis &
William Loftus, © 2012 Pearson Education |
Course
Materials |
BlackBoard (http://mymason.gmu.edu) – All assignments
must be submitted (per published deadlines) via BlackBoard. GTA/UTA contact information, class
schedule, slides, materials, assignments, grades and
other relevant documents are available on BB. |
Email |
Students must use GMU email system
for all correspondence with professor; no sensitive information may be shared
with non-GMU email addresses. Use the following email subject format:
CS211_XXX_NAME, where: x is your lab section number, such as 203, & NAME
is your name - failure
to adhere to this policy may result in unanswered emails. |
Grading |
500
points total:
25 pts: ( 5%)
Class Participation
50 pts: (10%) Quizzes (6, drop 1) 200 pts: (40%) Programming Assignments
(various weightings) 100 pts: (20%) Two Tests 125 pts: (25%) Final Exam. 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 excused
absences require acceptable documentation. Students must arrive on time to
log participation for a lecture or lab session. Lab exercises must also be submitted, during lab time, in order to get
credit for the day—even if you are not finished. 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 near the entrance 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 the 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, without exceptions. Quizzes
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—traffic is an example of an unexcused
absence!). The lowest of the quiz grades will be dropped from the overall
class grade calculation. |
Programming
Assignments |
Assignments are normally due one week
from the date they are assigned (the specific due date will always be prominently
listed on the specification). Late lab programming assignments will not be
accepted—do not wait until the last moment to submit your work! Turning in the wrong file also amounts to
not turning in your work. Be careful. Programming assignment specifications
(e.g., algorithms, techniques, syntax, etc.) may be discussed verbally with
other students, but code may not be shared, including digitally and orally.
All resources used in the assignment must be properly cited. Sharing of code
or use of code from any unapproved resource constitutes an Honor Code
Violation. When in doubt – ask. We
will follow up on any perceived instances of improper assistance. 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. Again, 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. The first contact should be made with your lab section's GTA
for all quizzes and projects, and with the professor for tests. If you go to
the wrong person first, you will just be asked to go to the correct contact
first. |
Exams |
Exams are closed book/notes, and must
be taken in pencil. 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. 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 the professor ASAP to discuss
accommodations. |
|