CS 2213 (Advanced Programming) can substitute for CS 3443.
Note that prerequisites will be enforced.
You must be a good C programmer and be able to debug C programs by yourself to take this course.
You also need to know the basics of Java programming (with objects).

The emphasis of the course is on process management, but we will cover Parts 1 through 4 of Silberschatz along with the Linux and Windows case studies. Most of our specific examples will come from UNIX, and we will be covering most of chapters 1-8 and 18 of USP as well as some of the project chapters.

Attendance in the lecture is required.
Quizzes will be given at the start of most class periods.
There will also be some take-home quizzes.
These quizzes and class participation counts 15% of your grade.
During each class you will log into your linux account on the computer at your seat and execute ~classque/cs3733.

No make-up exams will be given except for university sanctioned excused absences. If you must miss an exam (for a good reason), it is your responsibility to contact me before the exam. Leave a message at the above number or send me email.

Unless otherwise stated, all assignments are due at the beginning of class on the due date. Assignments are usually due on a Wednesday. For these assignments, there will be a 10 percent penalty if they are turned in by the following Friday. Do not miss class to finish an assignment. Turn in what you have for partial credit. Assignments will not be accepted after the second due date unless prior arrangements have been made.

Programs must following the programming style guidelines given.
You must keep copies of the source code for all assignments for this course at least until you receive the your final grade for the course. At any time during the semester you may be asked to demonstrate any of your programs.

Unless explicitly stated in an assignment, you may receive help from any source. Discussions are encouraged. However, all discussions and other assistance you receive on an assignment must be documented in your assignment. What you turn in must be your own work. You may not just copy another person's assignment. You may not copy another person's code. However, you may discuss how to solve problems with others. You must keep track of the date and the name(s) of the person(s) you talked to, as well as produce short paragraph describing what was discussed and the contribution made by each person involved. Collaborations that are not documented will be considered cheating. This type of scholastic dishonesty usually results in immediate failure in the course and can lead to additional disciplinary action.

Important: If you use computers long enough you will delete a file by mistake. When working on assignments, make copies of your course code often and store the copies in a safe place. At a minimum, you should store them on your account in a different directory. It is a good idea to use a separate directory for each assignment and a separate subdirectory for each part of the assignment. Copy everything from one part of the assignment into a new directory before starting on the next part. After you have worked several hours on a program and have it almost working, make a backup copy before doing any major modifications.

All student are expected to understand the general rules and regulations of UTSA including the information at http://utsa.edu/syllabus.