CS 3853 and CS 3851 Architecture Syllabus
Fall 2012


Instructor: Dr. Steven Robbins
Office: 4.01.23 SB
Phone: 458-5544
Address: srobbins@cs.utsa.edu (subject must contain CS 3853)
Course Homepage: /classes/cs3853f2012/
Office Hours: Mondays, Wednesday, Fridays: 11:00 - 11:50 am
Class Times: MWF 10:00 - 11:50 am in room 3.02.02 SB
Recitation Times: Mondays and Wednesdays at 11 am in room 3.02.10A SB

Texts:

Prerequisites: CS 3423 (Systems Programming) and CS 3843 (Computer Organization)
Note that prerequisites will be enforced.

Course Objectives:

Course Content:
We will cover the following chapters of the text:
Chapter 1 (introduction, trends, benchmarks, Amdahl's law)
Appendix C (pipelining)
Appendix B, Chapter 2 (memory hierarchy)
Chapter 5, in part (parallel memory hierarchy)
Chapter 3 (instruction-level parallelism)
Chapter 4, in part as time permits

Grading:
   The same grade is assigned for CS 3853 and CS 3851.

Attendance:
Attendance in the lecture is required.
Questions will be asked at the start of most class periods.
These quizzes and class participation counts 20% of your grade.
During each class you will log into your linux account on the computer at your seat and execute ~classque/cs3853.

Notification of final grades:
If you wish to receive your final grades by email, send me an email message some time after the last class and before the final. The message should have the subject line
CS 3853 Grade Request
and the message should have a valid return address. After I have graded the final exam and determined the letter grades for the course I will reply to your email message.

Course Policy:
The last day for an undergraduate to drop this course is Wednesday, December 5. The last day for a graduate student to drop this course is Thursday, November 1. No make-up exams will be given except for university sanctioned excused absences. If you must miss an exam (for a good reason), it is your responsibility to contact me before the exam. Leave a message at the above number or send me email.

Unless otherwise stated, all assignments are due at the beginning of class on the due date. Assignments are usually due on a Monday. For these assignments, there will be a 10 percent penalty if they are turned in by the following Wednesday. Do not miss class to finish an assignment. Turn in what you have for partial credit. Assignments will not be accepted after the second due date unless prior arrangements have been made.

You must keep copies of the source code for all assignments for this course at least until you receive the your final grade for the course. At any time during the semester you may be asked to demonstrate any of your programs.

Unless explicitly stated in an assignment, you may receive help from any source. Discussions are encouraged. However, all discussions and other assistance you receive on an assignment must be documented in your assignment. What you turn in must be your own work. You may not just copy another person's assignment. However, you may discuss how to solve problems with others. You must keep track of the date and the name(s) of the person(s) you talked to, as well as produce short paragraph describing what was discussed and the contribution made by each person involved. Collaborations that are not documented will be considered cheating. This type of scholastic dishonesty usually results in immediate failure in the course and can lead to additional disciplinary action. All student are expected to follow the Roadrunner Creed.


Fine print
This Syllabus is provided for informational purposes regarding the anticipated course content and schedule of this course. It is based upon the most recent information available on the date of its issuance and is as accurate and complete as possible. I reserve the right to make any changes I deem necessary and/or appropriate. I will make my best efforts to communicate any changes in the syllabus in a timely manner. Students are responsible for being aware of these changes.