CSC 270: Computer Organization
Syllabus

Instructor: Prof. Chris Fernandes
Email: fernandc (at) union (dot) edu
Lecture: MWF 9:15-10:20 (Olin 206)
Lab: Thurs 9:00-10:45 or 10:55-12:40 (ISEC 051)
Office Hours: Mon 11-2, Wed 1-3, Fri 11-noon
or anytime my door's open!
Office: 219 Steinmetz Hall
Phone: 388-6401
Course Webpage: http://nexus.union.edu

Text (1 required):

David Harris and Sarah Harris, Digital Design and Computer Architecture, 2nd ed, Morgan Kaufmann, 2013. ISBN: 978-0-12-394424-5

Course Description

There are microprocessors in your cellphone, watch, kitchen appliances, and perhaps even your sneakers. This is the class where you learn how microprocessors work and how to build them. We'll learn the major components common to all computing architectures and how they interact.

By the end of the course, you should understand

all the components of a MIPS microprocessor
logic gates
computer architecture design
how to compare processors across a variety of performance metrics
MIPS assembly language programming
how to build a CPU capable of running a computer program

Prerequisites

C- or better in CSC 120 or its equivalent. Talk to your instructor immediately if you do not meet this prerequisite.

Evaluation

Microhomeworks. Small homework assignments will be given throughout the term and are normally due by the start of the next lecture. These will be on Gradescope, which you can sign up on using the entry code X8GN6B. You will type answers directly into Gradescope, but sometimes you'll be asked to upload a pdf file containing your answer. Pdf files must be typed. Nothing handwritten will be accepted. If you need to draw circuit diagrams, build them in Logisim. Each question requiring a pdf upload should be done in a separate pdf file. No late microhomeworks will be accepted.

Seminars. The CS department has a (usually) biweekly seminar that explores the diverse and rich field of computer science. Our seminars discuss a variety of topics, including, computer science research, applying for CS jobs or graduate school, and career and technical skill development. The seminars are frequently presented by visitors from academia and industry, and alumni. The seminar is typically Thursday during common lunch (12:50-1:50pm) and is held in Olin 107. Seminar dates and topics are announced on the CS department mailing list. As part of taking this course, you are expected to attend at least one CSC seminar this term and submit a brief written summary using the webform at https://tinyurl.com/unionCSseminar. Summaries are due on the last day of class and will count as a microhomework. Of course, you are strongly encouraged to attend as many CSC seminars as you are able.
(Note: attending at least one CS seminar is a requirement common to all CSC courses numbered 250 and above. So if you are taking more than one such CSC class this term, it is fine if you attend one seminar and double-count it towards this course and another CSC course.)

Lab projects. The purpose of a lab section in a computer science class is not busywork. They provide you with hands-on practice in an environment that allows the instructor to notice errors and bad design habits as they happen and "nip them in the bud" so that good habits can become ingrained in you instead. Labs meet weekly and are mandatory. Major assignments are given out in labs where you have the lab time to start on them. I normally do not expect you to finish labs during lab time. They will usually be due in a week. No lates will be accepted. If you miss a lab without an excused absence, you will lose 10% on that project. Coming to lab more than 30 minutes late counts as "missing the lab". There will be one multi-week final project towards the end of the term that will let you build an entire CPU from the ground up.

Exams. The midterm is on Mon, Feb 9^th during class and the final exam is on Mon, March 16^th from 8:30am to 10:30am. Both are cumulative, closed book, and limited notes. You may bring one single-sided page of notes to the midterm and two single-sided pages (or one double-sided page) of notes to the final.. If you cannot be at an exam for a good reason (illness, for example) then please let me know so we can make other arrangements. You will be responsible for all material covered in the readings and in lectures.

Grading

Microhomeworks: 10%
Lab projects: 35%
Final project: 15%
Midterm: 20%
Final exam: 20%

Academic Dishonesty

Struggling on your own to figure out what to do next is where a lot of the learning happens in CS. Give yourself the opportunity to do this -- ALONE. Here are some specific things to avoid (this is not a complete list):

Do not "work on the project together" with friends, especially if the group of you are each at your own computers and are always in lock step trying to figure out the same line of code or the same part of the logic circuit at the same time.
Do not give your circuit diagrams or code to another person or receive the same from another person -- EVER. You might think that it's just helping out a friend, but it's still academic dishonesty.
Do not even look at someone else's work unless it is to give that other person help. For example, if someone asks you to look at their code in order to understand an error message, that's fine. If you are looking because you yourself don't know how to write something and you need "inspiration", that's NOT fine.

Ok, so what should you do? Here are some tips:

Once you've struggled with something on your own and you're still getting nowhere, ask for help! Email and visit me, go to the helpdesk, and, yes, ask your fellow students! They can't show you their own work, but they can sure explain things and write out examples.
Microhomeworks should be worked on by yourself. If you have a question or you are stuck, get your $80 worth and ask me.
It's ok to write pseudocode together. Get the logic down in English. Then go off by yourself and translate it to code.
It's ok to work together on code/problems that are not part of the assignment, especially when it helps demonstrate the concept of what you're being asked to do. Go through a class example together or maybe a demo. There's no better way to understand something than trying to think up examples in order to teach it to someone else. Try it!
It is ok to reuse material that is in the textbook or in a class demo. It is not ok to use material you find on the Internet (including ChatGPT and similar sites), in other textbooks besides our own, or that is part of someone else's lab/hwk/project.

Here's the bottom line: except for the above, you have to write everything yourself, from scratch. Don't go looking on the Internet if you don't understand a class concept. You should be asking me.

We have an honorcode and I'm trusting y'all to follow it. Read up on it at http://honorcode.union.edu. All suspected violations will be reported to the Honor Council chair and Dean of Studies.

What you need to do

To prepare for class, you are required to do the following:

Show up

Read the text

Nexus

Check the webpage on Nexus

Check your email twice a day

Stay focused

and yours

Make backups

Don't let it be you.

Don't fall behind

Accommodations

Union College facilitates the implementation of reasonable accommodations, including resources and services, for students with disabilities, chronic medical conditions and temporary disabilities resulting in difficulties accessing learning opportunities. All students needing services must first register with Accommodative Services located in Reamer 303. It is strongly recommended that accommodations be requested within the first two weeks of the term. Last minute requests can be denied. Any student with a documented learning disorder is welcome to come talk to me privately about options for completion of exams and homework assignments.

The Bottom Line

Ask questions and seek help. This is the most important point of all. I live to answer questions. Don't be afraid to contact me every single day if you want. It's better for everybody (you AND me) if you understand things sooner rather than later. More often than not, there's a line of people waiting to see me on the day before a project is due. You'll get the help you need faster by starting on projects sooner rather than waiting until the last minute.

CSC 270: Computer Organization Syllabus