Course Info

CIS 122 Intro to Programming and Algorithms, Fall 2010
TR 2-3:20, STB 146
CRN: 11948

Instructor: Eric David Wills, Ph.D.
Office: 156 Deschutes
Hours: M 10-11, T 12:30-1:30, WF 12-1, R 1-2
eric@cs.uoregon.edu

GTF: Sohan Akolkar
Office: 233 Deschutes
Hours: MW, 2-3, F 1-2
sakolkar@cs.uoregon.edu

GTF: Yaniv Ovadia
Office: 232 Deschutes
Hours: TR 11:30-12:30, F 2-3
yovadia@cs.uoregon.edu

Course Objectives

Introduce procedural and Object-Oriented (OO) programming.
Gain practical experience writing C++ code.
Gain practical experience using an Integrated Development Environment (IDE).
Encourage further interest in Computer Science.

Textbook

Introduction to Programming with C++, 2ed., Y. Daniel Liang, Prentice Hall, 2010. Custom edition for the UO ISBN 978-0-558-37139-5; Regular edition ISBN 978-0-13-609720-4. Custom edition contains Ch. 1-7, 9-10, and 13-15 of the regular edition.

Software

Microsoft Visual C++ 2008 Express, which is on the CD included with the textbook. MSVC is also installed on the Klamath and McKenzie PC lab computers. MSVC is also is available for free download from Microsoft.

MSVC is not available for Mac OS X. CodeBlocks, Aquamacs, Eclipse, and XCode are options for OS X, although details and support are beyond the scope of this course.. An option for Intel Macs is running Windows using the Parallels desktop or Boot Camp.

See the document Setting Up your Home Computer for 122.

Grading Policy

Programming Projects:	30%
Final Project:	20%
Midterm Exam:	25%
Final Exam:	25%

Grades will be posted on Blackboard.

Missed Exam Policy

Students must contact the instructor PRIOR to missing an exam to schedule a makeup exam. Makeup exams will only be scheduled following an exam in cases of documented emergencies.

Late Project Policy

Projects submitted after the due date/time are considered late and will not be graded. Late assignments will only be graded in cases of documented emergencies.

Plagiarism

Discussion of course material and collaboration with other students is encouraged but each student must write/type and submit his/her own solution. Your code and proofs (if applicable) should never contain sections which are identical to the submission of another student, past or present. Submitted work must be entirely that of the student(s) whose name(s) appear(s) on the submission and not solicited in any way from others. Violation of these policies can result in automatic failure of the course.