It's important that you attend lecture regularly and that you set aside the time to complete the assigned readings prior to the start of class. Lecture complements the text and may cover different material, or present the readings from a different perspective.
Your grade will be based on 4 Programming lab assignments, pop quizzes, the midterm, and the final exam. The pop quizzes will be given during lecture and will not be announced.
Academic Integrity will be strictly enforced. Plagiarism and other forms of cheating will not be tolerated. Do meet with us to enrich your experience in the course. Do not submit work or ideas as your own that can be attributed to others.
The work done by your team must be done independently of other teams. You must not take written notes while discussing someone else's work nor anytime afterwords. You must not use code you didn’t write, nor code you wrote for another course, unless I authorize it. Anyone found plagiarizing another's work, or making their own work available to others, will receive a zero grade for the work in question and face other possible consequences.
You are assumed to be familiar with the Integrity of Scholarship Policies in effect for this course, as described in the following document, which also discusses code usage:
http://www.cse.ucsd.edu/~baden/Integrity.html
Be sure to familiarize yourself with this document. If you have any questions, see Professor Baden.
Plan your work schedule around any planned absences from school and inevitable machine downtime. Late assignments will be accepted for up two (2) days after the deadline, subject to a 10% penalty for each day the assignment is late. This policy will not be waived except in cases of emergency or hardship. In such cases contact us as soon as you can. If you are planning to be away from school, be sure and contact us in advance to avoid penalty.
Re-grade requests will be accepted for one week only, starting from the day the graded work is returned. After that, the grade is unchangeable. Re-grades should be requested only if there is clearly a mistake in grading, such as tallying your score or a missing score. Note that the whole assignment or exam will be re-graded; this could result in a lower score than before. Tampering with a graded assignment paper is considered a breach of Academic Integrity. The procedure for midterm re-grade requests is somewhat different: you must submit your re-grade request during class or office hours. No exam will be accepted for re-grading once it has been removed from the place where it was returned.
All programming assignments shall be done in teams of 2. If there are an odd number of students we will work it out.
Choose your partner carefully! Be sure to budget times in your busy schedules to enable you to meet for non-trivial amounts of time! It's best if you can meet in person for some of that time, if not by phone or video call. This is especially true if you have a job, or if you commute to school.
If your partner drops the class, contact one of us immediately so we can match you with a new partner.
If you want to switch partners, that's OK with us. However, note the following policies.
I may permit you to reuse code written outside the course, for example, from another course. Normally this would cover basic utility functions and the like, where the purpose of reusing the code would be to relieve you of mundane tasks but not working with the deeper intellectual content of the assignment. You must contact me for permission. For any jointly written code, you must provide the co-author(s)' permission to let you use the code. Other rules apply and be sure to read over the code reuse and sharing section of the Integrity of Scholarship Agreement.
Maintained by [Wed Jan 5 09:11:09 PST 2011]