CS253

CS253: Software Development with C++

Fall 2010

Syllabus

Syllabus

ClassCS253: Problem Solving with C
LectureBSB 103, MWF 3:00–3:50PM
RecitationCSB 215, R01: Fri 9:00–9:50AM, R02: Thu 1:00–1:50PM, R03: Thu 11:00–11:50AM
sign up for only one recitation section
Last DropSeptember 8, 2010
Last WithdrawOctober 18, 2010
Required TextC++ for Java Programmers Mark Allen Weiss, ISBN 013919424X
 (Make sure that you get the book by Weiss—there’s another book with the same title by somebody else.)
Optional TextProgramming / Principles and Practice Using C++ Bjarne Stroustrup, ISBN 0321543726
  
InstructorJack Applin <his-last-name@CS.ColoState.Edu>
Office HoursCSB 246; see my calendar
  
GTAErin Nagoshi <her-last-name@CS.ColoState.Edu>
Office HoursCSB 120; Wednesday: 1ᴘᴍ-2ᴘᴍ, Thursday: 5ᴘᴍ-6ᴘᴍ, & Friday 10ᴀᴍ-12ᴘᴍ (Please note! These times may change!)
TaskValue
Recit week 2–151% each
Homework 01%
Homework 1–65% each
Quiz 1–35% each
Midterms 1–213% each
Final exam14%
Letter GradePoints
A≥90
B≥80
C≥70
D≥60
F<60
I will not cut higher than these points, but I may cut lower.


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

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:

Policies

Policies on cheating, plagiarism, incomplete grades, attendance, discrimination, sexual harassment, and student grievances are described in the Student Information Guide. In addition this class adheres to the policies set in the current CSU General Catalog.

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.

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.

Modified: 2010-08-29T09:50

User: Guest

Check: HTML CSS
Edit History Source
Apply to CSU | Contact CSU | Disclaimer | Equal Opportunity
Colorado State University, Fort Collins, CO 80523 USA
© 2015 Colorado State University
CS Building