[ Home | Syllabus | Progress Map | Search | Help | Lectures | Glossary]

Syllabus for CS 250 (WEB Version)

SYLLABUS

FOR REGISTERED CS250 WEB STUDENTS: Please read and sign the course agreement and bring it to Dr. Wild's office ASAP.

Objectives: Upon successful completion of this course, the student will have gained an increased understanding of problem solving techniques in software systems. Students will be introduced to recommended methods of program design, development, and implementation. Methods of decomposition, abstraction, and problem solving techniques will be presented. Students will be provided with a working knowledge of  Object-Oriented Design and Programming.. The role of experimentation in Computer Science will also be discussed. This course is based on the C++ language and introduces UNIX and X windows and associated tools to the students.

Laboratory: CS 250 UNIX lab  is a co-requisite for this course. Students who are not registered for one of the sections of the lab will not be allowed to remain registered in CS 250.

Attendance: For the Fall 1998 - the Lab portion of CS250 is NOT on the Web: You are expected to attend a regular lab section!
Also You must attend the lecture classes to take the required tests - there will be no web based testing for the Fall  (see syllabus below).
Because of the traditional lecture course is also being given this semester, you are welcome to attend at any time (if seats are available).
The material given in both the web course and the lecture course is essentially the same. However the web course offers personalized tracking of your progress and easy reference to material covered in CS150. Also there are a number of innovative features that will be available and about which we would appreciate your comments (both positive and negative).

Late/Missing Work: If a course project assignment is not turned in on the due date or tests are missed, they will receive a grade of zero unless prior permission has been given by the instructor.

Please note that the due dates for assignments are designed to allow more than enough time to complete the assignment. Occasional hardware failures are a fact of life in the computing field. Unless unusually severe or prolonged, such problems are not cause for a due date extension. Similarly, the 48 hours before an assignment due date invariably feature heavy competition among students for the available computing resources. Such competition is never an acceptable reason for requesting an extension. Budget your time accordingly!

Cheating: Everything turned in for grading in this course must be your own work. The instructor reserves the right to to question a student orally or in writing and to use his evaluation of the student's understanding of the assignment and of the submitted solution as evidence of cheating. Violations will be reported to the Honor Council for consideration for punitive action. However, it is entirely appropriate seek and give assistance on procedural matters (such as how to send e-mail, how to run the debugger, how to send files from a home PC to a UNIX workstations). If there is any question on whether a particular behavior is appropriate, the student is encouraged to seek guidance from the instructor.

Grading:

Schedule: (approximate)
You can access the lecture notes as the become available (usually the morning of the class by selecting the lecture below).
But if that fails you can always go directly to the lectures by following this link

Back to Top

Copyright chris wild 1998.
For problems or questions regarding this web contact [Dr. Wild].
Last updated: December 02, 1998.