Image goes here
Syllabus
CptS 260 - Intro to Computer Architecture
Washington State University

Course Location

MWF 15:10-16:00, Sloan 46

Course Web Pages

Information you need to successfully complete the course will be posted on the course web pages from time to time. This syllabus, a calendar of lectures and assignments, assignments themselves, lecture notes, handouts, etc. will all be found on the web pages: http://www.eecs.wsu.edu/~hauser/cs260.

Teacher Contact Info

Prof. Carl Hauser
Office: EME 53
Phone number: 5-6470
E-mail: hauser@eecs.wsu.edu
Office Hours: MWF 4PM-5PM or by appointment

TA Contact Info

Rasika Chakravarthy
Office: ETRL 309
Phone number: 335-TBD
E-mail: rmchakra@wsu.edu

Course Description

Computer systems architecture; logic, data representation, assembly language, memory organization and trends.

Course Objectives

The purpose of this course is to provide Computer Science students with the knowledge of computer hardware they need to design and implement effective and efficient software. Students who complete this course should be able to perform the following:
  • Write and debug simple programs using assembly language
  • Explain the principles underlying the design and development of computer systems for a variety of puposes
  • Trace the influences of important computing developments (such as compiler technology, networking. the web, multimedia. safety, security) on the architecture of computer systems
  • Outline the architectural features of a modern computer system.
In the context of the Computer Science degree programs this course contributes to: program outcome (a), students' abilities to apply knowledge of computing. It stresses acquisition of knowledge reinforced by its application; program outcome (c), ability to design, implement and evaluate computer systems and programs. Students learn about the role of evaluation of performance, costs, etc. in creating computing systems; and program outcome (i), ability to use current techniques, skills and tools necessary for computing practice. The MIPS architecture is a modern, widely-used microprocessor architecture.

Topics

  • Digital logic and digital systems
  • Machine level representations of data
  • Assembly level machine organization and programming
  • Memory system organization and architecture
  • Interfacing and communication
  • Functional organization
  • Multiprocessing and alternative architectures
  • Performance enhancements
  • Contemporary architectures

Texts

Douglas E. Comer, Essentials of Computer Architecture, Pearson Prentice Hall, Pearson Prentice Hall, 2005.

Robert L. Britton, MIPS Assembly Language Programming, Pearson Prentice Hall, 2004.

Additional Reading

Other materials will be either handed out or found on the Web.

Course Prerequisites

CptS 223 (Advanced Data Structures) - Concurrent enrollment ok.

Course Requirements

Attendance is expected at all lectures. Lecture notes will be posted on-line but reading the notes is not an adequate substitute for attendance. You are also expected to participate in class discussions to a reasonable extent. This aids learning and provides valuable feedback on the lecture. I reserve the right to lower the grade of any student who is markedly deficient in attendance and/or participation.

Homework, Assignments, and Tests

There will be two mid-term exams and one final exam. All programming assignments can be done with the computers in the instructional lab in Sloan 353, or alternatively, can be done at home. Turn-in will be via file upload and for some projects will involve an interview with the TA. The following allocation of grade percentages is tentative, and may change during the semester.

Students are reminded that a grade of C or better is required in this class is required in order for this class to be counted in a computer science degree program. To achieve a grade of C or better in the course, you must separately achieve a grade of C or better on the exams and C or better on the programming projects.

Cheating Policy

Exams, homework, and programming projects are subject to the EECS academic honor code. DO NOT CHEAT IN ANY WAY: DO YOUR OWN WORK! Doing your own work means that you may NOT work together with another student on any assignment. It means you do not turn in a solution you found on the web.

I do not know why this is such a difficult concept for students, but every semester I hear sob stories from students claiming that they didn't understand the policy. I don't want to hear them and you don't want to suffer the consequences. SO DON'T DO IT! If you are stuck on a problem I suggest discussing it with me or with the TA. You don't have to wait for office hours: I read e-mail all day, every day, so ASK!

Side effects of cheating can be severe, ranging from a failing grade on the assignment involved to a failing grade in the class to expulsion from the university.

Re-grading Policy

All homework and projects will be marked as soon as possible after the due date and returned during lecture. Additionally, some grades will be sent via e-mail. If you discover that a mistake was made in grading the work may be submitted for re-grading no later than one week after the assignment is returned. This is the only window of opportunity for re-grading. In order to request re-grading, write or type a detailed explanation of the reasons for the re-grading. Submit the explanation along with what was originally turned in to the teaching assistant or professor. Do not orally ask either the professor or TA to re-grade any piece work.

Students with Disabilities

Reasonable accommodations are available for students with a documented disability. If you have a disability and may need accommodations to fully participate in this class, please visit the Disability Resource Center (DRC). All accommodations MUST be approved through the DRC (Admin Annex Bldg, Room 205). Please stop by or call 509-335-3417 to make an appointment with a disability specialist.

Stress management

Students sometimes encounter stress and anxiety issues associated with homework, tests, or life situations that can be an obstacle to success in their courses. WSU Counseling Services (335-4511) offers information including a test anxiety workshop conducted several times each semester. Visit http://www.counsel.wsu.edu/self-help/test-anxiety.html for more information.

Other Policies and Expectations

  • I expect you to demonstrate critical thinking across the spectrum of course work.
  • I expect you to engage in active learning: speak up when you don't understand, question assumptions, relate course material to your experience outside class, seek out additional experience and reading related to the class.
  • I expect you to promptly review feedback you receive from me, the TA, or other students; to actively clarify the feedback if the material is still unclear; and to incorporate the feedback in your future work.
  • I expect you to spend adequate time on the course. Adequate time includes getting enough rest so that time you spend on course tasks is well-spent time. Adequate time includes proofreading and reviewing your assignments before you hand them in.
  • I expect you to have high expectations of yourself: set goals for yourself and try to do your very best. Consciously think about the balance between what you do to earn a grade and what you do to learn. (If I'm doing something that puts these in opposition to each other please let me know.)

Advice

  • Don't wait until the last minute to do homework or projects. The lab gets busy, computers break down, people get sick. These are not sufficient excuses for an extension.
  • Save early; save often!
  • Come see me or the TA if you are confused. Don't wait for office hours -- send a question by e-mail.
  • Come see me and the TA anyway. We'd like to know more about you.
  • If you have trouble with spelling and grammar, get and use a word processor that has spelling and grammar flagging.
(c) 2004-2006 Carl H. Hauser           E-mail questions or comments to Prof. Carl Hauser