CS 256 - Computer Organization and Architecture - Spring 2024

Description

If we have a reasonable understanding of what computers can do, a logical next step is to think about how they can do it. If I write var = var + 1; in C, what does the computer actually do, "behind the scenes," to make that happen? What are all of those parts inside the computer, and how do they work together? And how are they designed to be as efficient as possible?

We will approach these questions from two different directions. Computer science contains an abundance of abstraction, and this course investigates several layers of abstraction below what you have likely previously studied. In one direction, primarily in lab, we'll start from a very low level, the physical building blocks of digital electronics, and work upwards, building more and more complex structures as we reach towards a complete computer. In the other direction, we'll work from what we know of high-level programming languages down towards the physical implementation of a machine that can execute such code. In the middle, the two directions will often meet, joining to form a complete connection from code to electrons.

For an idea of the specific topics covered in the course, see the rough schedule for the semester.

Other Pages

Semester schedule — tentative - see Canvas for up-to-date details.

Online Resources — notes, readings, and other resources will be posted here. I will link to relevant entries from Canvas, but it doesn't hurt to browse and see what else is there.

Details

When/Where:
Lecture: TR 2:35-3:50PM / CNS E210
Lab: Tuesday 7-9PM / CNS WS203
Instructor: Mark Liffiton
Office: CNS C207B   (2nd floor CNS, in middle of building over atrium)
Office Hours:
  • Monday 11am-noon (by appointment — ask a day in advance)
  • Tuesday 10am-noon; 4-5pm
  • Wednesday 10-11am
  • Thursday 11am-noon
  • Friday 11am-noon (by appointment — ask a day in advance)
During my office hours, I will be in my office and possibly available on Discord (if I'm not with someone in person).
And generally, feel free to drop in any time if my door is open.
If your schedule prevents you from attending my set office hours or you would like to meet sooner than the next office hours you can attend, I will often be available on Discord, and I'm very happy to set up alternate meetings. Just ask.
Contact (you→me): We will use Piazza for most course- and content-related questions. For anything specific to you, feel free to talk to me before or after class, meet me in office hours, stop by my office, catch me on Discord, or email (for email, please start the subject with "CS 256:").
Contact (me→you): I will post course announcements through Canvas, and they will be sent to your IWU email accounts. Check your IWU email frequently or have it forwarded to an address you do check.
Textbook: Computer Organization and Design: The Hardware/Software Interface
Authors: David A. Patterson and John L. Hennessy
ISBN: 9780124077263 (5th ed.)
Note: The 4th and 6th editions have mostly the same content, as long as you are okay figuring out the mapping of sections and page numbers between editions.
Note: Be sure you get the MIPS version, not the ARM version. Students have ended up with the wrong version when ordering the international edition in the past, and it does matter.

Grading

The final grade will be based roughly on the following breakdown:

Assignments20%
Labs20%
Exam 125%
Exam 225%
Engagement10%

Assignments

Assignments will be posted on Canvas, usually about a week before they are due, and they will be collected there as well. Submissions should be in the form of PDF documents.

Labs

The labs will be hands-on explorations of hardware concepts, generally involving designing, building, and testing digital logic circuits. The labs will build your understanding of logic concepts as well as prepare us for a final class-wide project of designing, building, programming, and testing a complete, working CPU.

Lab assignments will be posted on Canvas. Reports should be submitted on Canvas as PDF files. The desired format of the reports will be specified on Canvas.

Late Policy

Assignments and Labs will be due at set times; they will be considered late at any point after that time. An assignment will lose 10% of the total possible points for every day or partial day it is late, and after five days it will not be accepted.

Assignments can't be accepted at all after solutions have been handed out or the graded work has been returned to the class.

Grace Tokens

Every student has two "grace tokens" that they may use for extensions in instances where they are unable to complete work by the assigned deadline. To use a grace token on an assignment, send me an email before the assignment deadline, explain why you need an extension, and we will determine an appropriate extension, which will be granted with no grade penalty. Some assignments may not be eligible for grace tokens due to immediate use of or feedback on the submitted work, but most will be.

Exams

There will be two exams during the semester, held in class.

Regrading

If you would like to request a regrade, submit a request in writing (via email) within one week of receiving the graded assignment, exam, etc. Indicate exactly which part you believe deserves a different score and why.

Engagement / Attendance

Class time will be complementary to the reading, and you will need both in order to learn all of the material in this class. Many class sessions will involve material and/or practice that you will not be able to find or make up elsewhere. Furthermore, each student benefits from the engagement of all others in the class. Part of your final grade will be based on that engagement. Attending every class period on time and prepared will earn a base of 70%; points can be gained by constructive participation, in class or out, such as asking questions, answering them, responding on Piazza or Discord, sharing insights or useful/interesting resources with the class (posting on Discord, for example), investigating concepts beyond the requirement in class, working on small independent learning projects, and in many other ways. Points can be lost for excessive (more than 3) unexcused absences, disrupting class (e.g., regularly showing up late), poor participation in group exercises, and the like.

Absences can be excused with documentation from health services or the Dean of Students' office, or if arrangements are made with me a week in advance. In general, if you know you will be missing a class, let me know as soon as you can.

Office Hours

If any concept, piece of code, compiler error, or anything else related to this course is ever unclear to you, please come see me during my office hours. One-on-one, I can help you bridge the gap from what you do understand to what you want to understand. It will generally be the easiest, fastest way to clarify something.

If you cannot attend any of my regularly scheduled office hours, I'm more than happy to setup another time to meet. Just let me know.

And to make sure that misunderstandings and difficulties do not go unaddressed, I will often ask that anyone who receives a C- or below on any assignment or exam come see me to see what we can do about improving that going forward.

Working with Others; Using External Resources

I strongly encourage you to form study groups with your classmates, compare notes, explain concepts to one another, and generally help each other learn the material in this course.

Any material turned in for a grade must be your own individual work, though. You may work on concepts with other students, but I ask that you not discuss assigned problems until after the work has been turned in. Giving or showing your solutions or code to another student — or looking at theirs — is not allowed.

This has two goals: 1) ensure that grades are a reflection of each student's own work, and 2) avoid situations where one person solves a problem and another records the answer as their own work without really learning.

Submitting solutions generated by a large language model (AI) as your own work is plagiarism. Copying code found online and submitting it as your own work is plagiarism as well. Copied code with a source cited will not be reported as an academic integrity violation, but if the code you've copied is a substantial portion of the problem you were supposed to solve, you may still lose points.

For details on the university's policies regarding academic integrity, please read the University Policies Concerning Student Conduct & Academic Integrity. Academic misconduct can result in failing the course and a report to the associate provost. If you are ever unsure of whether something might be crossing that line, please err on the side of caution. You can also just ask me, and I'll be happy to provide guidance.

Accommodations

Illinois Wesleyan University strives to make all learning experiences as accessible as possible. If you anticipate or experience academic barriers based on a disability (including mental health and chronic or temporary medical conditions), it is your responsibility to self-disclose and provide documentation to the Office of Student Accessibility Services. Please note that accommodations are not retroactive and accommodations cannot be provided until I receive an email from Student Accessibility Services. Once the email is sent, please make arrangements with me as soon as possible to discuss your accommodations confidentially so they may be implemented in a timely fashion. For more information contact Student Accessibility Services by e-mailing accessibility@iwu.edu or stopping by their office in Holmes Hall.

Diversity

Our university's mission statement includes, "The University through our policies, programs and practices is committed to diversity [...]" Our school and this course are made stronger by the mix of people that come into it bringing a diversity of ideas, experiences, and backgrounds. I expect everyone in this course — instructor, TA, and student — to contribute to an inclusive atmosphere that respects the diversity of all others in it. Dimensions of diversity can include sex, race, age, national origin, ethnicity, gender identity and expression, intellectual and physical ability, sexual orientation, income, faith and non-faith perspectives, socio-economic class, political ideology, education, primary language, family status, military experience, cognitive style, and communication style. The individual intersection of these experiences and characteristics must be valued in our community. If you have related concerns about the class environment or behavior of any in it (including me), you are welcome to raise them with me, and I will do my best to address them. If you are not comfortable speaking with me about them, you may also bring concerns to the Associate Provost or the Office of Diversity and Inclusion.

End-of-Syllabus Advice

Help each other. This is good advice for any course. By working out concepts with others or teaching someone about something you've already worked out yourself, you can greatly improve your understanding. Teaching or any other kind of back and forth will point out any gaps in your understanding, trust me; as a student, I learned a great deal and did well in many classes primarily because I helped others. In this course, helping each other is perhaps even more useful than normal, because the course is full of new kinds of ideas. Much of it will not be programming, will not be math, and will not be like anything you've done before. With everyone starting from a similar baseline, each person in the class might have a valuable insight or perspective on a particular concept that can be shared with the rest. The lab will also be very conducive to this sort of sharing; if you come up with a helpful way of working or thinking in the lab, let the rest of us know! There is no competition here.

page last updated Jan 29, 2024