 |
CSC 215 |
|
Specifics |
Brief description
This is a beginning course in programming. It assumes no previous
programming experience. However, it helps if you're familiar with
the Windows '95 environment. The language used is C++ and the
preferred package is Microsoft Visual C++, version 5.0. More about
this package will be explained in class.
Textbook
The text will be Problem Solving with C++: The Object of Programmming, by
Walter Savitch (Addison-Wesley, 1996).
Topics
The following list indicates the order in which to read various
sections of the textbook. We will probably spend one class (i.e.,
three hours) on each. Note that this sequence is not carved
in stone. Depending on how the quarter goes, we may add or omit
material.
- Chapter 1, Introduction to computers and C++ programming
- Chapter 2, C++ basics
- Chapter 3, Procedural abstraction
- Chapter 4, Functions for all subtasks
- Chapter 12 (only sections 1 and 2), Recursive functions
- Chapter 5, I/O streams
- Chapter 7, More flow of control
- Chapter 9, Arrays
- Chapter 6, Defining classes
C++ assignments
Most of the assignments will involve writing C++ programs. You may use any
C++ compiler available to you. If you use one in the lab, I recommend
Visual C++, version 5.0. A brief tutorial
on using Visual C++ to create and run programs is available.
Grading
The course grade will be based 50% on weekly homework problem sets,
20% on the midterm, and 30% on the final exam.
Office hours
My office hours will be:
- Monday, 4pm to 5:30pm, 723 CS&T Center
- Tuesday, 4pm to 5:30pm, 723 CS&T Center
- by appointment (send me e-mail)
My office hour rant
I hold office hours specifically so that students have a time when
they know I'll be in and available to answer questions. Please
make use of my office hours! One of the resources you get when
registering for a course is a chance to talk to the instructor one on
one. Students often discover that even a brief chat about an
assignment they're having trouble with will often clear up that (and
other) problems, allowing them to proceed and complete the
assignment.
In fact, you should stop by whenever you have a question. My teaching
is not limited to the classroom. I have found that some the best
teaching (and learning) happens when a student comes in to see me.
My office hours are posted above but I want to make it clear that I'm
also available outside of those hours. The best way to see me then is
to send me e-mail (rogers@cs.depaul.edu) or call me
(312-362-8334) and arrange for meeting time. You can also try
dropping by. If I'm in and not busily preparing for a class, I will
be more than happy to see you.
Policy on plagiarism and cheating
Students may discuss assignments with one another in general terms.
For example, you may discuss general strategies for attacking a
problem. But you may not work together when writing the
solution. I know it may sometimes not be clear what is considered
permissible cooperation and what is considered cheating. If you are
not certain, please discuss it with me.
A corollary is that if you are having trouble getting started on an
assignment, please come in and see me or send me e-mail (see my
discussion about office hours above). Students often find that even a
brief chat will clear up quite a few problems.
Students may not collaborate in any way on exams.
Activities that are clearly cheating include (but are not limited to):
copying another person's work on a programming project, homework
assignment, or exam; using any reference not authorized by the
instructor on a programming project, homework assignment, or exam.
The penalty for cheating is an F in the course. Also, the appropriate
dean will be informed in writing of cheating incidents and will be
advised that students assigned an F for cheating should not be
permitted to receive a W for the course.