1. Computer Organization II
CS 2733
Computer Organization II
Topics:
Staff, text, and policies
Lecture topics and assignments
Lab rationale

2. Teaching staff
See syllabus for detailed information

3. Textbook Randal E. Bryant and David R. O’Hallaron,
“Computer Systems: A Programmer’s Perspective”, Prentice Hall 2003.

4. Course Components Lectures Recitations Homeworks Higher level concepts
Applied concepts, important tools and skills for labs, clarification of lectures, exam coverage
Homeworks
The heart of the course
1 or 2 weeks
Provide in-depth understanding of an aspect of systems
Programming and measurement

5. Getting Help Web Personal help http://www.cs.utsa.edu/~dj/cs2733
Copies of lectures, assignments, exams, solutions
Personal help
Professors: Door open means come on in (no appt necessary). Door closed means go away unless something is on fire.
TAs: please first.

6. Cheating What is cheating? What is NOT cheating? Penalty for cheating:
Sharing code: either by copying, retyping, looking at, or supplying a copy of a file.
What is NOT cheating?
Helping others use systems or tools.
Helping others with high-level design issues.
Helping others debug their code.
When in doubt, ask the professor.
Penalty for cheating:
Referral to the Dean’s office where penalties range from a permanent mark on your record to separation from UTSA.

7. Facilities Assignments will use the “main” machines
Linux operating system.
In the 3rd floor SB lab (the Sun lab)
main201, main202, main203, ..., main209, ...
If one doesn’t work, try another one.
Available for remote login.
Getting help with the machines:
See course Web page for info
Please direct questions to your TA