CS 250 Computer Programming and Problem Solving - FALL 1998 

[ Home | Syllabus | Notes | Glossary | CS250 WEB Version Home Page | Project Page | Final Study Guide]

SYLLABUS

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:   is a co-requisite for this course. Students who are not registered for one of the sections of CS 250 lab will not be allowed to remain registered in CS 250.

Attendance: Attendance at classes is not generally required, but students are responsible for all material covered and announcements made in class. Consequently, if you are going to miss class, be sure to get notes, handouts, etc., from another class member. Class notes and other information will be available at the following WebSite: http://www.cs.odu.edu/~cs250.

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)

Back to Top