Syllabus: CSC 221, Computer Organization

	Location:	Julian 040, MWF 11:20-12:20
	Home Page:	http://www.csc.depauw.edu/~bhoward/courses/0405Fall/csc221/
	Professor:	Brian Howard (bhoward@depauw.edu)
	Office:	Julian 266, ph. 658-4120
	Office Hours:	M 3:30-5, TTh 10:30-12, or by appointment (or when my door is open)

Texts:

J. Stanley Warford, ``Computer Systems'', 2<sup>$\scriptsize nd$</sup> edition, Jones and Bartlett, 2002;
Tracy Kidder, ``The Soul of a New Machine'', Little, Brown and Co., 1981 (copies will be available for loan from the department)

Course Description:

(from the Catalog) This is an introduction to the study of computer hardware, concentrating on the central processing unit and main storage. Topics include representing information, machine language, combinational and sequential logic, input/output, registers, register transfer logic and bus structures. Assembly language and the high-level language, C++, are used to aid in the understanding of these topics.

Grading:

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

• 45%--Quizzes and Homework (including Programming Projects)
• 30%--In-class Exams: Friday, October 1 and Friday, November 19
• 25%--Final Exam: Tuesday, December 14, 8:30-11:30 a.m.

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:

 

Monday	Wednesday	Friday
	Aug. 25	27
30	Sept. 1	3
6	8	10
13	15	17
20	22	24
27	29	Oct. 1: Exam 1
4	6	8
11	13	15
Fall Break
25	27	29
Nov. 1	3	5
8	10	12
15	17	19: Exam 2
22	Thanksgiving
29	Dec. 1	3
6	8	10
Final Exam

Schedule of Topics:

This schedule is only approximate and subject to change.

• Week 1: Chapters 1 & 2 (App7 and HOL6)
• Weeks 2 & 3: Chapter 3 (ISA3: Information Representation)
• Week 4: Chapter 4 (ISA3: Computer Architecture)
• Week 5: Chapter 5 (Asmb5: Assembly Language)
• Week 6: Exam I (Friday, October 1)
• Weeks 7 & 8: Chapter 6 (Asmb5: Compiling)
• Weeks 9 & 10: Chapter 10 (LG1: Combinational Networks)
• Week 11: Chapter 11 (LG1: Sequential Networks)
• Week 12: Exam II (Friday, November 19)
• Weeks 13 & 14: Chapter 9 (OS4: Storage Management)