Syllabus

Class

CS253: Problem Solving with C++

Lecture

Clark C 142, MWF 11:00–11:50ᴀᴍ

Recitation

CSB 215: R01: Fri 9:00ᴀᴍ, R02: Fri 2:00ᴘᴍ, R03: Mon 12:00ᴘᴍ

Last Drop

September 7, 2011

Last Withdraw

October 17, 2011

Required Text

C++ for Java Programmers Mark Allen Weiss, ISBN 013919424X (be sure to get the book by Weiss—there’s another book with the same title)

Optional Text

Programming / Principles and Practice Using C++
Bjarne Stroustrup, ISBN 0321543726

Instructor

Jack Applin <his-last-name@CS.ColoState.Edu> (email tips)

Office Hours

CSB 246; see my calendar

GTA

Amin Sobhani <his-last-name@CS.ColoState.Edu>

Office Hours

Linux Lab; Mon 4:00–5:00ᴘᴍ, Wed 8:00–10:00ᴀᴍ, Thu 1:00–2:00ᴘᴍ

Overview

The purpose of this class is twofold:

1. Learn C++, which will partition the class into three sections:
   • Non-object-oriented C++
   • Object-oriented C++
   • Templates and the STL
2. Learn the tools of a professional programmer, including:
   • make
   • debuggers
   • valgrind
   • efence
   • programming styles (imperative, event-driven, object-oriented)
   • source control systems
   • coding standards

Grading

Your scores are available via RamCT. The GTA grades everything. If you don’t like your score, talk with the GTA first, then to the instructor if you still disagree. Homework is submitted & graded online. Quizzes are returned in class.

Conduct in Class

Don’t distract the students. I don’t insist that you pay attention, but you must allow others to participate. This means:

• Do not distract others with conversation.
• Do not distract others with your phone.
• Do not distract others by reading the newspaper.
• Do not distract others by using your laptop in front of the class.
• If you snore, I will wake you up.

Policies

Policies on cheating, plagiarism, incomplete grades, attendance, discrimination, sexual harassment, and student grievances are described in the Student Information Guide. All other matters follow the policies set in the current CSU General Catalog, and in the CS Dept. Code of Conduct.

You may not copy or use, all or in part, someone else’s work. You may not give your work, all or in part, to someone else for any reason. It is your responsibility to keep your work private from all others. You may not collaborate to produce one product turned in multiple times. You may not use work done in a previous semester by someone else.

You MAY discuss assignments but the work you turn in must be your own. You have crossed the line if you start comparing someone else’s work to your own (or vice versa). You have crossed the line if you cannot explain/understand the work you submit. “I copied it from the internet” is not an explanation.

NOTE: The Computer Science Dept. often runs similarity detection software on completed assignment program code. This software is quite sophisticated and can detect duplicated code among one or more programs with an astoundingly high resolution.