UCR CS 61: Computer Organization & Assembly Language
Summer Session 2, 2003
Lecture Schedule
Lab Schedule
Turnin
Previous CS61's
In this course we start with transistors, logic gates, latches, logic structures,
and memory circuits. We cover the von Neumann model of computing, and then use all
these tools to understand thoroughly the Instruction Set Architecture of a simple
computer, the LC-2. This leads on to assembly language programming of the LC-2.
Catalog description :
Lecture, six hours / week; laboratory, six hours / week.
Prerequisite: CS10
Class web site:
www.ilearn.ucr.edu
Enrolling in this course gives you automatic access to the
UCR "ilearn" site: your login id is the name part of your ucr
student email address, and your initial password is your Student
ID (no dashes or spaces).
ALL communication with the class (announcements, assignments,
handouts, etc.) will be via the ilearn site.
Some communications may be made only via the
ilearn site, so you are expected to check it regularly.
Instructor :
Dr. Brian Linard (blinard@cs.ucr.edu)
Office hours: Monday to Thursday 10:00 am to noon (by appontment)
Office:
Surge Bldg. 340.
Teaching Assistants and office hours:
Honomount Rawat hrawat@cs.ucr.edu)
Office hours held in
Surge Bldg. 282.
Lectures:
MTWR 1:00 to 2:30 pm in
Boyce Hall. 1471
Labs:
Lab attendance is mandatory. Plan to stay in the lab for the entire
lab session, working on material related to this course.
MW 3:00 to 6:00 pm in
Surge Bldg. 282
Text Book:
Introduction to Computing Systems , by Patt & Patel (McGraw-Hill)
Course grading:
Letter grades are assigned (approximately) according to the usual
90/80/70/60 scale out of 100 total course points, with 90 and
above corresponding to an A, 80 and above to a B, 70 and above to a
C, 60 and above to a D, and less than 60 to an F. +/- grades will
likely be given. A+'s will be given to students in the high 90's who
also have turned in all required material and many of the challenge
in-lab excercises. The course is divided into two grading components,
combined as a weighted sum to total 100 points:
65: Theory component:
20: Quizzes/homeworks (expect a 10 - 15 min. quiz, and a
homework set, each Tuesday & Thursday)
20: Midterm
25: Final
35: Practical component:
10: In-lab programming exercises and attendance
5: In-lab practical exams
20: Take-home programming assignments (5 assignments x 4 points each)
To ensure minimum competency in successive courses requiring a
C- or better in this course, the following grading scheme will be used:
a C- minimum in both components is necessary to achieve a C-
minimum for the final course grade, regardless of the components'
weighted sum; otherwise, the final course grade will be no greater
than a D+. For example, a B in the practical component and a D in the
theory component might yield a weighted sum of a C, but would instead
result in a final course grade of D.
Approximate Time Requirements:
This is a four-unit CS course. As such, you should expect to spend
the following approximate amount of time:
6 hours/week in lecture
6 hours/week in lab
10 to 20 hours/week doing individual study (readings,
homework, programming, lab preparation, etc).
Please don't underestimate the time you will need to spend on this
course. These are real time amounts spent by average successful past
students. Computer Science and Engineering are challenging disciplines
requiring extensive time to master.
Subject to change as the quarter progresses.
Read the book before lecture! Reading ahead is one of the most effective
ways of doing better in class -- you'll be amazed how much more
comprehensible and useful the lectures will be.
Note: a unit refers to a period of 2 lectures / 1 lab - i.e. there
are 2 units per week in the Summer session
- Unit 1: Introduction to concepts of Computer Organization
and LC-2 Assembly language (Chap 1)
Quiz 1
- Unit 2: Binary arithmetic & data types (Chap 2)
Quiz 2
- Unit 3: Logic operations, Boolean algebra (Chap 2)
Hardware basics: transistors, logic gates (Chap 3)
Quiz 3
- Unit 4: Logic circuits & Memory (Chap 3)
Quiz 4
- Unit 5: von Neumann model & the Instruction cycle (Chap 4)
Midterm
- Unit 6: LC-2 Instruction Set in detail; LC-2 data path (Chap 5)
Quiz 5
- Unit 7: Assembly Language programming: the process (Chap 7)
Quiz 6
- Unit 8: Assembly Language programming: i/o, traps to os, subroutines (Chaps 8/9)
Quiz 7
- Unit 9: Creating a Stack data structure (Chap 10)
Using Assembly language to inplement some HLL functionality (Chap 14)
Quiz 8
- Unit 10: Miscellaneous & Review
to be announced
- Material covered: Lectures do not necessarily cover all required material:
some appears in the course books and may be covered only in the
lab sessions.
- Academic dishonesty: cheating will be strongly punished
(typically with an F in the course). You can report cheating anonymously
at:
https://www.cs.ucr.edu/cheating/. Assignment submissions must
represent your original work. Copying from any sources (web, other
books, past or current students, etc.) is strictly prohibited --
learning to program requires you to learn to solve programming problems
by yourself; using existing code and other resources becomes important
later on in your studies. While discussing assignments together is
encouraged, team coding (even of pseudo-code) or letting others
see your code are specifically not allowed. Be aware that
programs are automatically compared to the current and prior quarter's
programs for plagiarism, using a sophisticated code-comparison tool
that ignores insignificant differences (like whitespace and variable
names). If you're smart enough to fool the instructors, TAs, and
code-comparison tools, you're more than smart enough to do the programs
on your own!
A couple more notes. Be aware that a subset of exams may be photocopied,
for comparison with exams submitted for regrades. Also, be aware that
lying to an instructor in order to be able to makeup a missed exam
or in other ways to obtain a better grade can be treated as academic
dishonesty. During exams, cell phones must be stored away in a
place not visible (e.g., inside a backpack).
- Final Exams are scheduled by the University, not by the
instructor, and are correlated to the course sections. What that means is
that you must take the final exam scheduled for the section you are
enrolled in.
- Regrade policy: regrade requests must be submitted in
writing and within one week of the distribution of the graded
material. The entire exam/assignment may be regraded, not just the
problem in question, so the grade may go up or down. Thus, think your
regrade requests through carefully. Grade-database errors should also
be pointed out within one week of posting.
- Final grades: Per university policy, changes to your final
grade will be made only in the event of a clerical error.
Asking your instructor how far you were from a cutoff and what
extra work you can do to improve the grade is not appropriate.
- Switching/adding/dropping lab and lecture sections: all
add, drop, and section changes of all lower division Computer Science
courses, after the period when students can do so electronically is over,
are done through the College of Engineering's Student Affairs
office. Neither the instructors nor the CS department itself can sign any
add/drop forms, nor can they arrange for section changes. Please go to
Student Affairs, Bourns Hall A159, for any such changes.
- Communicating with the instructors and TAs: when sending
electronic mail to the instructors or TAs, please include your
full name, student ID number, and UCR email
address, so that we may properly identify you (remember, many
students have similar names). Also, please try to be polite and
use reasonable grammar and formatting.
- Cell phones: During lectures and lab sessions, please
turn off your cell phone.
- Homework and lab reports: All turned-in assignments
will be turned in electronically.
Each file should begin with our
report
template header. Source code must comply with professionally accepted
coding
standards. In particular, all your code must be compiled with
the -Wall -W -Werror command line options, or else it will not be
graded. Also, you must include a section explaining the
design, structure, etc of your program and how it works. Comments in
source code are important, but they are
not a replacement for an explanatory section. Please
remember that successfully writing a computer program that compiles and
runs correctly is not something anyone can do in just a few minutes,
even when it looks easy. Debugging typically takes three times
longer than figuring out how to write your program. So don't leave
your programming assignments to the last minute!
- Reading: Read the current book sections before coming
to lecture, and attend all lectures in their entirety. To encourage these
important college study habits, we may give a few simple pop quizzes
during the quarter, at any time during lecture.
- Students are required to stay the full three hours of lab session
every week. You'll have in-lab exercises, discussions, and possibly
practical exams. Work ahead or on extra course-related material if you
finish early.
- During lab discussion time, students should not use the computers.
Ideally, students would move their chairs to the whiteboard area.
- Prepare for lab before arriving.
- To reduce disruptions and provide for the best educational
environment, all persons in lab during scheduled lab time
should be formally registered in that section. In general, no
swapping sections and no unregistered people in the lab are allowed,
even if there are extra computers.