Roger L. Kraft

Syllabus
CS 22300
Computer Architecture & Assembly Language
Fall, 2015

Professor Roger Kraft
Office: Classroom Office Building, Room 368
Office phone: (219) 989-2696
Office hours: 11:00--12:00 MW, 2:00--3:00 TR, and by appointment.
E-mail: roger@purduecal.edu

Text:Computer Systems: A Programmer's Perspective, 3rd Edition, by Randal E. Bryant and David R. O'Hallaron, Pearson, 2015.

Supplemental Texts (all available online):

This course is an introduction to the fundamental concepts of computer architecture, progressing from the digital logic level to the microarchitecture level and then to the instruction set level. We cover data representations, machine level representations of C programs, processor architecture, program optimizations, and the memory hierarchy. Assembly language and the assembly process will also be included.

In addition to the study of computer architecture, two other subjects will be important in this course, the C programming language and the Linux operating system. All of the programming assignments will be done using the GCC compiler running in a Linux environment.

We will cover Chapters 1 - 4 and Chapter 7 of the textbook. Your grade for this course will be based on about eight programming assignments and two exams in the following manner:

           40%    programming assignments,
           30%    1st exam,
           30%    2nd exam.

Tentative dates for the two exams are

           Exam 1   Tuesday, November 10
           Exam 2   Final exam week.

Each of the programming assignments will have a due date. To receive full credit for an assignment, it must be turned in by the due date. All programs handed in late will be marked off 10% of the total points for each calendar day late up to a maximum of 50%. If an assignment is more than two weeks late, then I reserve the right not to accept it for credit. When you complete a programming assignment you will turn in the source code for your solution using the university's course management system. In this course web site there are detailed instructions on how assignments are to be turned in. You will be expected to follow the instructions. Also in this web site is information on the criteria used to grade your programming assignments.

You should turn in your own work for each programming assignment. Here is what that means: You may talk with your classmates about the course material and the ideas behind each homework assignment but you should solve each problem on your own and write your own code for the solution. Turning in someone else's solution (or even a modified version of someone else's solution) is a breach of academic integrity. Similarly, giving a copy of your solution to someone else in the class is also a breach of academic integrity. If you need help with a homework assignment, come and ask me. You can ask me as many questions as you want! Please do not hesitate to ask me questions after class, in my office, in an e-mail message, over the phone, etc.

The final grades for this course will use a plus and minus grading system. The possible grades for this course, and a tentative grading scale for the grades, is given in the table below. The final grading scale that I use may not quite be the same as the one given below (the grade cutoffs might possibly be lower, but they will not be any higher than what is given in this table).

A93 - 100
A-90 - 92
B+88 - 89
B83 - 87
B-80 - 82
C+78 - 79
C70 - 77
D+68 - 69
D63 - 67
D-60 - 62
F59 or less

In this web site you will find more information about this course. There are links to online help and documentation for C and Linux, information about course reading assignments, and, very importantly, all of your homework assignments and their due dates will be posted on one of the web pages.

The software that you need to do all of your programming assignments are on computers in the Mathematics Computer Labs in CLO 363 and CLO 365. If you wish to work at home, I will show you in class how to install and use a couple of different C development environments and Linux environments.

The learning objectives for this course are as follows.

  1. Explain the reasons for using different formats to represent numerical data and be able to convert numerical data from one format to another.
  2. Summarize how instructions are represented at both the machine level and in the context of a symbolic assembler.
  3. Explain how subroutine calls are handled at the assembly language level.
  4. Explain basic instruction level parallelism using pipelining and the major hazards that may occur.
  5. Explain the use of memory hierarchy to reduce the effective memory latency.
  6. Explain how interrupts are used to implement I/O control and data transfers.

Students who may need accommodations due to disability should contact the Office of Disability Resources (ODR) to discuss specific needs. The ODR is located on the third floor of the Student Union & Library Building, Room 341. If accommodations for a student are approved by that office, the student must provide his/her instructor with a copy of the official accommodations letter as soon as it is received in order to obtain accommodations. Students may contact the Office of Disability Resources by calling (219) 989-2455 or emailing odr@purduecal.edu.

Ethics are an integral part of being a student and a professional. Academic integrity is the hallmark of this University. Therefore, Purdue University does not tolerate academic dishonesty in any form. If a student breaches integrity, the student risks sanctions in both the academic and conduct arenas. Academic dishonesty includes, but is not limited to, the unauthorized use of other's intellectual property (plagiarism), and lying to an instructor or any University employee. Such actions WILL result in a failing grade on the assignment with the strong possibility of referral to the Office of the Dean of Students for a conduct sanction (see the Purdue University Calumet Student Handbook available from the Dean of Students office).

An information sheet, with instructions for various types of possible emergencies, is posted in each room on campus. These possibilities include criminal activity, fire, medical emergencies, and noises sounding like gunshots. Students are strongly encouraged to review this instruction sheet carefully and acquaint themselves with these important guidelines.