Syllabus: CSC 122, Computer Science II

	Location:	Section A--Julian A040, MWF 1:30-2:35
		Section B--Julian A113, MWF 2:45-3:50
	Home Page:	http://acad.depauw.edu/~bhoward/courses/0203Fall/csc122/
	Professor:	Brian Howard (bhoward@depauw.edu)
	Office:	Julian A220, ph. 658-4120
	Office Hours:	TTh 10-12, 2-4, or by appointment (or when my door is open)

Text:

Carrano & Prichard, ``Data Abstraction and Problem Solving with C++: Walls and Mirrors'', 3^{$\scriptsize rd$} edition, Addison-Wesley, 2002.

Course Description:

(from the Catalog) This course builds on CSC 121 and introduces programming topics such as sets, recursion, and dynamic data types. Data type abstraction and implementation are introduced by studying structures such as lists, stacks, queues, and binary trees. The object-oriented implementation of these structures is emphasized. Tools for algorithm analysis are introduced, and comparisons of functional, object-oriented, and imperative programming paradigms are made. The concept of tradeoffs, i.e., time vs. space, iteration vs. recursion, static vs. dynamic, and imperative vs. functional, recurs as a theme throughout the course.

Grading:

The grade for this course will be based on the following:

• 35%: Programming Assignments
• 20%: Homework and Quizzes
• 20%: Midterm Exam, Monday, September 30
• 25%: Final Exam

  Section A (MWF 1:30)

  Friday, December 13, 8:30-11:30

  Section B (MWF 2:45)

  Monday, December 9, 1-4

Policy Statements:

 

• You are expected to attend all class sessions. However, I expect you to take your own education seriously, so I do not keep formal attendance records. If you miss a class, you are responsible for catching up with the material that was covered and any announcements that were made.
• Homework assignments are due by the start of class, and programming projects are due by 5:00 p.m. on the assigned date. Late submissions will be accepted until the next class time at a penalty of half the grade. Extensions will be considered only by prior arrangement.
• Cheating, plagiarism, submission of the work of others, etc., violates the DePauw policy on academic integrity and may result in penalties ranging from a lowered grade to course failure or expulsion. The policy and discussion of each student's obligations and rights are in the Student Handbook. With respect to this course, no collaboration is permitted on exams or quizzes. You may discuss homework problems and programming assignments with anyone you want (in fact, you are encouraged to do so), but you should not copy another student's work nor permit your work to be copied. The key idea is that you should understand all of the work you turn in, and you should be able to replicate it on your own. If you do not feel that you can replicate the work independently, then it is not fair (to yourself or to others) to submit it as your own work. If at any time you are uncertain what constitutes ``appropriate'' collaboration, it is your responsibility to clarify it with me.
• Programming projects will be graded on style and efficiency as well as correct operation. To develop as a programmer, you are strongly encouraged to do more than the minimum assigned amount of work; the best way to learn good style and common idioms is to read and write lots of code.

Calendar:

Note that there will be no class on Friday, October 4 or Monday, October 7, in addition to the regular University breaks.

Monday	Wednesday	Friday
	Aug. 21	23
26	28	30
Sept. 2	4	6
9	11	13
16	18	20
23	25	27
30: Midterm	Oct. 2	4: No Class
7: No Class	9	11
14	16	18
Fall Break
28	30	Nov. 1
4	6	8
11	13	15
18	20	22
25	Thanksgiving
Dec. 2	4	6
Final Exam