Computer Organization/Architecture II (CS 355)

Instructor:	S. Y. Cheung
Office:	North Decatur Bldg 140
Telephone:	404-727-3823
Office Hours:	MWF 3-4 PM
Text:	Structured Computer Organization
	by Andrew S. Tanenbaum.

Pre-requisite

Course Description and Objective

After examining the CPU and memory structures, we will discuss the micro programming level, where micro programs are used to implement more complex machine instructions using simpler instructions (much like a subroutine call). After this, we will examine the communication between the different parts of the computer: how do the CPU, memory and I/O devices communicate ? We will examine the use of address, data and control buses and study ``bus protocols''. We will learn about the two types of buses: synchronous and asynchronous, and we will see that the CPU uses different communication methods for communicating with the memory and an I/O device due to difference in speed. This will lead us into study programmed I/O and interrupt I/O. The above constitute the core material in CS355. The remainder of the course will discuss advance techniques in computer architecture -- these techniques are the ``bells and whistles'' added to the computer to make it run faster. Topics covered include pipelining, register windows, cache memory, virtual memory, and if time allows: multiprocessors.

Grading in CS355

• Your grade will be solely based on the scores you received in homework & project assignments, and midterm & final tests. The grade is not based on "how much effort you put in the course". It is like running the engine of a car on full speed but having the transmission on neutral will get you no where fast, working hard but not understanding the material will not get you a good grade in this course. The key is understanding the material taught.

• Homeworks and projects are to be treated as examinations and are expected to be your individual work. Under no circumstance should you show another student your answer and program, even after the due date - some students may have received special permission to turn in late. Read the policy statement concerning programming assignments at the end of this sylabus. This policy applies to homework assignments as well.

• The midterm and final examinations are open notes/book exams where the majority of the questions test students on their knowledge of the subject, i.e., whether you know material. The solution to some questions in the tests will require some synthesis thinking , i.e., apply what you know to solve a new problem.

• If you have any problems with the examination schedule (other than that you have to leave for home early), please let me know immediately so I can make up an examination for you to take on a mutually agreeable date. The date will be one before the scheduled exam date - that's my policy for individual tests and I will not deviate from it.

Class Policy

• Attendance is NOT required at Emory, but you are expected to attend. It is your responsibility to turn in the assignments and come to the tests on time. If you miss some classes, it is your responsibility to obtain the notes and material distributed in class.

• All homework assignments must be turned in according to the assigned date, regardless. (Unless you have a good reason to turn it in late. Having missed class and/or not knowing it was handed out previously are not an acceptable reason.)

• You may turn in three assignments late but you must ask for the extension in advance (the advance notice is only a formality so that I can instruct the turnin system to allow you to turn in the assignment late).

  Once you have used up your three extensions, you cannot turn in any assignment late. You should however turn in your incomplete assignment for partial credit.

• You cannot ask for an extension for the last assignment in the course - we need to grade that one ASAP to meet the grade turnin deadline of the college.

Students will be graded partially on the basis of their programming assignments. These programming assignments are to be treated as examinations, and are expected to be your individual work. While discussions with other students in the course may be permitted or encouraged by your instructor, you should write your program yourself. The mathlab representatives are available to explain error messages, discuss briefly technical details with which you may not be familiar, and give short suggestions as to how you might detect logic errors. The reps should not, however be asked to write part or all of your program. Your instructor (and any teaching assistants assigned to the course) will be glad to help you to the extent that he or she feels reasonable.

Submissions based on other students solutions in prior offerings of the course specifically violate these guidelines, as do submissions prepared with the help of an outside "tutor".

You should take precautions to protect the confidentiality of your work: preserve the secrecy of your password, do not make files or directories sharable, pick up your printouts promptly and dispose of printouts where they will not tempt other students. All work should be done either in the class directory of your ITD account (preferred) or in your "priv" directory (only if you do not have a class directory).

All submissions should include a comment statement near the top of the program of the form:

THIS CODE IS MY OWN WORK, IT WAS WRITTEN WITHOUT CONSULTING A TUTOR OR CODE WRITTEN BY OTHER STUDENTS - your name

Cases of apparent plagiarism or collusion will be referred to the Honor Council.