360 Rules
-
ASK QUESTIONS
If students don't ask questions, I tend to assume you're understanding the material and I continue covering new material.
If you're not getting something in class, ask questions about it.
If you're not sure what it is you're not getting, just ask me to go over the material again.
If nothing else, come to my office to and ask questions.
If you can't make it to my office hours, email me to arrange a time when you can come to my office.
-
SUBMIT ASSIGNMENTS ON THE DAY THEY ARE DUE
No late homeworks or labs are accepted.
Give yourself enough time to account for slow system response.
System response WILL NOT be accepted as an excuse for a late homework submission unless the Department's computer staff reports a significant system problem which prevented timely submissions.
-
MISSING MIDTERM OR FINAL WITHOUT PRIOR APPROVAL OR DOCUMENTABLE, VERIFIABLE, JUSTIFIABLE EXCUSE WILL RECEIVE A GRADE OF ZERO.
Oversleeping or mistaking the time or place are not valid excuses.
-
THE MATERIAL YOU SUBMIT IS WHAT YOU WILL BE GRADED ON
Submitting the wrong version or making a last minute editing mistake are not valid excuses.
You are responsible for what you submit.
-
USE EMAIL TO ASK ME QUESTIONS, IF POSSIBLE
I typcially check email several times a day so you can often get a quick response to a question.
Questions about how to do something in Unix or with the class software can also be posted to the class newsgroup.
-
BE FAMILIAR WITH CLASS INFORMATION ON WEB AND ON THE CLASS NEWSGROUP
Periodically, updates are made to assignments on the web.
Don't just print it out once and assume you've got it all.
I will post notices on the class newsgroup when I make updates to web information.
I will also post answers to questions about assignments, class lectures, material in the book, etc., if I think that the answer may be interesting to the class at large.
-
LEARN THESE 3 THINGS:
- How to assemble and disassemble instructions - convert between assembly language instructions and machine language instructions.
- How to program in assembler - how to write syntactically correct assembly language instructions
- How to specify the internal-CPU signals that could be generated to fetch and execute a given instruction
Of course there are other things you should learn also, but these are three big ones.
Last updated 12/11/03
360 syllabus