CS 176 - Introduction to Computer Science II
Knowing any language imperfectly is very little better than not knowing it at
--- Lord Chesterfield, Letter to his son
5 April 1754
Table of Contents
This is the second course in a two course sequence on introductory programming
and computer science. See the
CS 176 course catalog
entry for more information.
The prerequisite for this class is
CS 175, Introduction to
Computer Science I.
The class meets in Howard Hall 530 on Tuesdays from 10:00 a.m. to 11:15
a.m. and on Thursdays from 10:00 a.m. to 12:15 p.m. Class meets in Howard Hall
526 on Tuesdays from 11:15 a.m. to 12:15 p.m. There will be class on 3 and 5
The course objectives are to build your skills in program design and
implementation. At the end of this course, you should know
- the C++ features and mechanisms that support classes, arrays, files, and
- design techniques for planning out programs
- implementation techniques for writing programs
R. Clayton, Howard B-13, firstname.lastname@example.org, 732 263 5522. Office
hours are on Tuesdays and Thursdays from 2 to 3 p.m. in my office. I'm also
usually happy to talk to you any time you can catch me; setting up an
appointment is recommended, see my
schedule for available times.
The final grade is a weighted average of test scores and programming assignment
- Lab Assignments.
- Lab assignments will be given in the lab (Howard Hall
526) during lab time (Tuesdays, 11:15 a.m. to 12:15 p.m.). You will have an
hour to finish the assignment. You will work in groups of two on the lab
assignments; see the lab assignment page for more information.
Lab assignments will be given whenerver there isn't a lab or design test
scheduled. There will be five lab assignments total; see the syllabus for details.
- Lab Tests.
- Lab tests will be given in the lab (Howard Hall 526) during
lab time (Tuesdays, 11:15 a.m. to 12:15 p.m.). You will have an hour to finish
the test. You may use your text and class notes; you may not consult with your
colleagues. There will be four lab tests total; see the syllabus for the lab-test
- Design Tests.
- Design tests will be given in class (Howard Hall 530)
during the first hour of class (10:00 a.m. to 11:00 a.m.). You may use your
text and class notes during the test; you may not consult with your
colleagues. There will be four design tests total; see the syllabus for the
- Projects will be handed out in class and will be due two weeks
from the time they're handed out. There will be six projects total; see
the syllabus for the project schedule.
- Quizzes will be given at the start of class, and you'll have
fifteen minutes to finish them (that is, quizzes will be given from 10:00
a.m. to 10:15 a.m.). Quizzes will be scheduled on a day-to-day basis based on
the instructor's whim (that's right - they're pop quizzes). You may use your
text and class notes during the test; you may not consult with your colleagues.
There will be six quizzes total.
- Final Exam.
- The final will be a two-hour exam, given at a time and date
yet to be determined in a room yet to be determined. You may use your text and
class notes during the exam; you may not consult with your colleagues. There
will be one final exam; see the syllabus for the time, date, and location.
The usual grade ranges are in effect:
All grades are kept with one digit of precision to the right of the decimal
point and 0.05 rounded up. No grades are adjusted to a curve; that means, for
example, that 89.9 is always a B+, never an A-.
|90 ||<=||A-||< 95|
|83.3||<=||B ||< 86.6|
|80 ||<=||B-||< 83.3|
|73.3||<=||C ||< 76.6|
|70 ||<=||C-||< 73.3|
|60 ||<=||D ||< 70|
|F ||< 60|
There is one required textbook for this course:
C++ How to Program, third edition, by the Deitels
Harvey and Paul, Prentice Hall,
2001; with errata.
You should feel free to send me e-mail. Unless I warn you beforehand, I'll
usually respond within a couple of hours during the usual work days; if I don't
respond within a day, resend the message.
Mail relevant to the class will be stored in a
archive. If your message is of general interest to the class, I'll store it,
suitably stripped of identification and along with my answer, in the archive.
If you're reading this on paper, you can find the class home page at
make the class notes, assignments, and tests available off the syllabus; you should
get in the habit of checking the home page and syllabus regularly.
People who need assistance or accommodations above and beyond what is usually
provided in class should contact the University's ADA/504 coordinator to get
those needs met. See me or the
Disability Services page
for more details.
I have no class attendance policy; you may attend class or not as you see fit.
However, I hold you responsible for knowing everything that goes on in class;
"I wasn't in class for that." is not an acceptable excuse for a wrong
answer, or for giving no answer at all.
My attendance policy applies only to lecture attendance; it does not apply to
other kinds of attendance which may be required for the course. Repeated
failures to meet the attendance expectations set for tests, meetings, projects,
labs or other forms of course work will have a bad influence on your grade.
Monmouth University does have a class attendance policy, which you can find
in the Academic Information chapter of the Student Handbook. To the extent
that I need to keep the record straight, I will take attendance. Attendance
lists, however, are entirely for the University's benefit; I will make no use
of them in grading.
I deal with suspected cheating by failing first and asking questions later.
Although cheating has many forms, I generally consider cheating to be any
attempt to claim someone else's work as your own; also, I consider both the
provider and the user of the work guilty of cheating. See the chapters on
Academic Information and the Student Code of Conduct in the Student Handbook
for more details.
Complaining about Grades
I recognize and encourage a student's sacred right to complain about their
grade. There are, however, a few rules under which such complaining should
take place, and those students who don't follow the rules will be less
successful in their complaints than those students who do follow the rules.
First, the only complaint that matters is that something got marked wrong when
it was actually right. When you come to complain, be prepared to present, in
explicit detail, what it is you did and why you think it's right.
Second, complaints about a particular test or assignment are only valid until
the next test or assignment is due; after that point the book is permanently
closed on all previous test or assignment grades.
Assignments must be turned in by their due date; assignments turned in after
their due date are late. You should contact me as soon as possible if you need
to negotiate a due-date extension. The longer you wait to negotiate, the less
likely it is you'll be successful; in particular, you have almost no chance of
getting an extension if you try for one the day before the due date, and you
have no chance of getting an extention on the due date.
A late assignment is penalized five points a day for each day it's late. I use
a 24-hour clock running from midnight to midnight to measure days; note this
means that an assignment handed in the day after it's due is penalized ten
points: five for the day it was due and five for the next day.
There may occasionally be a conflict between taking a test and doing something
else, particularly among those working full time. If you're going to be out of
town, or on jury duty, or whatever, on a test day, let me know beforehand and
we'll discuss a make-up test.
A make-up test must be scheduled to be taken by the date of the test following
the missed test (or the final exam if you miss the last test). If a missed
test is not made up by the time of the next test, you get a zero for the missed
There will be only one make up given per missed test. If more than one person
misses the same test, those people will have to coordinate among themselves to
pick a mutually agreeable date for the make up.
An on-line course based on
A page of C++ resources.
This page last modified on 12 October 2001.