CSC 221: Computer Organization, Spring 2006

Overview

Texts:

J. Stanley Warford, "Computer Systems" (third edition), Jones and Bartlett, 2005, ISBN: 0-7637-3239-7
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 (Wednesday, March 8 and Wednesday, April 26)
• 25%: Final exam (Wednesday, May 17, 8:30-11:30 am)

The grading scale used for this class will be the following: A (93-100), A- (90-92), B+ (87-89), B (83-86), B- (80-82), C+ (77-79), C (73-76), C- (70-72), D+ (67-69), D (63-66), D- (60-62), F(0-59). I reserve the right to alter this grading scale at any time. The last day to withdraw from class is Friday, March 17^th.

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 at the start of class and programming projects are due by 5 pm 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.
• 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.
• 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.
• During class time, the computer at your seat should be used for note-taking, classroom interaction, and in-class exercises. You are not permitted to read e-mail, browse the web, play games, etc. while class is in session.
• Regrade requests will be entertained for up to one week after the assignment or exam is returned to the student. To request a regrade, please write out on a separate sheet of paper your request and attach it to the assignment or exam, and give it to me. A simple request for more points without a justification is not sufficient! Keep in mind that the entire assignment or exam may be regraded, so carefully consider your requests!
• Please feel free to offer me feedback (positive and negative) about my performance or anything else related to the class. This feedback will have no effect on your grade in the class.
• Reading assignments will be given in class. They will mostly consist of readings from the class textbook, but other handouts and papers may be assigned as well.
• All information about the class, whether given in this handout or in class, is subject to change.

Calendar:

Week	Monday	Wednesday	Friday
1	Jan. 30	Feb. 1	3
2	Feb. 6	8	10
3	Feb. 13	15	17
4	Feb. 20	22	24
5	Feb. 27	Mar. 1	Mar. 3: No Class
6	Mar. 6	8: Exam 1	10
7	Mar. 13	15	17
8	Mar. 20	22	24
Spring Break
9	Apr. 3	5	7
10	Apr. 10	12	14
11	Apr. 17	19	21
12	Apr. 24	26: Exam 2	28
13	May 1	3	5
14	May 8	10
Final Exam

DePauw University, Computer Science Department, Spring 2006
Maintained by Brian Howard (bhoward@depauw.edu). Last updated