See the class web page. Office hours are subject to change during the semester. We will update the class web page and will email the listserv when changes are needed.

You are welcome to stop by or call at times other than during posted office hours.  If we have time, we will answer questions.  If not, we will make an appointment with you for a later meeting (in-person or on the phone).

Email is a *very* useful tool in helping you understand the course material. This is true for other courses as well. Having a good subject line helps immensely in filtering the important email (that related to class work) from less important email.

Provide your name in the message. Do not rely on us knowing who you are based only on your email address. When asking about a program, include your cs login.

Use full sentences and write as clear a message as possible. Email that is poorly written simply results in us sending a reply that asks for more information. As an example, tell us specifically what your program is doing wrong, where (what line) it fails on, what output is wrong, which test case(s) do not work, etc.  Tell us what you already know about the problem as this saves us troubleshooting time and prevents us from telling you something you already know.

    include previous email only when useful in understanding your message

Note that all 4 parts have to be present. You will also have to (later) answer the email response from the listserv in order to complete the subscription.

The listserv is set up to always include 352 at the beginning of the subject line.

You can send email to the listserv using the address sysprog@listserv.arizona.edu. Email that asks a question of general interest to the class is appropriate for the listserv. Questions that are specific to your solution to an assignment should be sent to cs352fall08@cs and not to the sysprog listserv.

Quiz 7: Thursday, December 4th.

Assignments will be graded based primarily on whether the program/script/command does, or does not, work. In general, we will run your program/script against a set of test cases. For each test case, you will receive the points for the test case if your output is correct; you will receive zero points if your output is not correct.  Note this is a binary function, you will get all or none of the points for each test case.  For scripts/programs, there will also be points assigned for style (comments, indenting, readability), error-free compilation, and for satisfying specific requirements of the assignment (such as malloc’ing/free’ing memory, makefile use, etc.). In general, 60% to 80% of the grade will be based on the test cases. We will provide some test cases, along with the output of our solution prior to the due date of each assignment. We may use additional test cases during the grading process.

Unless stated differently in the assignment, scripts and programs will be graded on lectura. You can use other platforms for development and testing. You should allow time for testing (and fixing as needed) your solutions on lectura.

You will be able to submit a revised program/script for re-grade on an assignment. Points lost due to factors other than test cases cannot be reclaimed by a re-grade. Points lost due to failing test cases can be partially regained, depending on the amount of change in your code from the original turnin. In general, the formula for this is: 90% for less than 2% changed, 70% for less than 10% changed, 50% for less than 25% changed. The amount of change will be based on the lines of code: comments, and blank lines will be not be counted. Variations to this formula may be applied to specific assignments; see the class web site.

To request a re-grade on an assignment, you will first need to fix your code (we are available to help with this). Next, use the turnin command for the assignment to turnin your corrected code (turnin will be set to a different directory after the due date has passed, so a re-grade turnin will not overwrite your original turnin). Third, send us (cs352fall08@cs) an email requesting the re-grade. All three steps will need to be completed within the re-grade time limit specified for the assignment.

See the class web pages for re-grade information specific to each assignment.

Do not question or challenge the decisions of the TA on grades and on re-grades! The TA can only assign grades, and change grades, according to instructions that I have given. If you do not agree with the TA, talk to me.

• Late assignments are burdensome, and detract from time otherwise available to help students with the current assignment.

Do not feel that your program or assignment must be complete to be turned in. Partial credit will be given for those test cases your program does pass. You may be able to submit the program for a re-grade.

The one exception to this is for test cases. You are allowed to share test cases and expected results of these test cases for the programming assignments.

for further details on what constitutes cheating,  the penalties that may result, and the procedures involved.