Computing Science 160
Course Information Sheet
Fall 1997
Sections F9701 F9702
This course is intended to provide
students with an introduction to programming in
C++. The course will focus on developing problem-solving
skills and programming techniques.
An on-line version of this document can be found at
http://malun1.mala.bc.ca:8080/~pwalsh/teaching/160/160.html.
Students are advised to check this web side weekly to
ascertain up-to-date information.
Last updated: Sept 4 1997
Office: Bldg 315 Room 209
Phone: 753-3245 Ext 2363
E-mail: pwalsh@malun1.mala.bc.ca
(Scott Cannon, West Publishing)
Text is available at the MUC Bookstore.
Evaluation:
Seven programming exercises (pex) |
35% |
Three in-class quizzes (3) |
12% |
One Final Examination |
53% |
Grade Conversion: The following scale will
be used but the instructor reserves the right to lower the
numerical score required for a particular letter grade if that seems
appropriate, but the same conversion will
be applied to all persons in the class.
Under no circumstances will the numerical score required
for a particular letter grade be raised.
90-100 | A+ |
85-<90 | A |
80-<85 | A- |
75-<80 | B+ |
70-<75 | B |
65-<70 | B- |
60-<65 | C+ |
55-<60 | C |
50-<55 | D |
<50 | F |
Lecture Outline
Week 1 (text Ch1) |
Introduction |
Week 2 |
Unix and the programming development environment |
Week 3 (text Ch2) |
Selection and Iteration |
Week 4 and 5 (text Ch3 and Ch4) |
Program design using functions |
Week 6 (text Ch5) |
Data types |
Week 7 (text Ch6) |
More control structures and operators |
Week 8 (text Ch7) |
Simple file i/o |
Week 9 (text Ch8) |
Strings |
Week 10 (text Ch9) |
Arrays |
Week 11 (text Ch10) |
Classes |
Week 12 (text Ch11) |
Recursion |
Week 13 (text Ch12 and Ch13) |
Pointers and linked lists |
Week 14 (text Ch14) |
Ethics and course review |
Assigment Submission:
Each assignment has a due date and time and, one or more
assignment identifiers (eg csci160_pex1).
All assignments are to be submitted by e-mail to
csci160@malun1.mala.bc.ca.
Assignments must be received before the due date and time.
In addition, your e-mail must have the assignment identifier
as its subject.
All other methods of submission will not be accepted.
You will receive no credit
for an assignment submission that fails to adhere to this convention.
Guidelines Concerning Fraud
These guidelines concern the type of fraud
where a student presents another's work as
his or her own, or allows another to do so.
- As fraud invalidates the evaluation of a student's progress,
it is the duty of instructors, teaching assistants,
and laboratory assistants to take measures
to prevent fraud and to be vigilant towards symptoms of fraud.
- Students are encouraged to study together.
But, unless the contrary is indicated, submitted work is to
be done by students individually. Students are to collaborate
on submitted work only when this is explicitly permitted
by the instructor. In such a case, the names of
all students who have collaborated on a piece of
submitted work should be indicated on all submitted material.
As in all academic endeavour, due credit must be given to
all reference material. Students should consult the
course instructor if they are not certain which
outside material is appropriate for use in a course.
The collaboration is to involve reasonable effort on the
part of all students involved. In a situation where this
is clearly not the case, appropriate action
will be taken with regard to those students who have
not fully contributed to the collaborative effort.
- In case fraud is detected, credit is withheld
from the work affected. The students involved are
reported to the department chair who may take additional
disciplinary action commensurate with the severity of the
fraud and the past records of the students.
Peter Walsh's Teaching Page