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, 3 quizzes, the midterm, and the final exam. The quizzes will be given at the start of a Friday lecture, spaced 2 weeks apart, not including the midterm week, and will be announced in advance.
All programming labs shall be carried out by teams of exactly two. We encourage you to discuss the labs with your classmates, but teams must work independently. If you aren't sure about this, see Professor Baden.
The quizzes will help prepare you for the midterm and final. They will be given during class, covering lecture, the readings and the programming assignments.
The midterm exam will be given during week 6. You will be responsible for all material covered in the readings, quizzes, lecture, as well as the programming assignments.
The final exam will be comprehensive, and cover all course material.
The policy for this class is that you must do your own work. In short, Don't cheat. The CSE 160 staff are available to you to learn what you need to do well in the course.
If you do cheat we will enforce the UCSD Policy on Integrity of Scholarship (see the UCSD Academic Integrity website). The consequences are this: You will get an F in the course, and the Dean of your college will put you on probation or suspend you from UCSD.
What counts as cheating? In CSE 160, you can read books, surf the web, talk to your friends and the CSE 160 staff to get ideas for solving your programming assignment. However, your 2-person team must write your own solutions to your programming assignments. Using code that someone else wrote (unless they are in your team for that assignment, or the code was explicitly provided as part of the assignment), or providing program code to someone else not on your team, or turning in code that you have written with someone else not in your team, is cheating. Yes, we do check every program that is turned in. WRITE YOUR OWN CODE.
To ensure you there are no misunderstanding: Don't even look at or discuss another student's code, and don't let another student look at your code. Don't start with someone else's code and make changes to it, or in any way share code with other students.
Note that we do provide for the possibility that you may use certain code that you've previously authored. The test we'll apply is whether or not the code functions in a support role, enabling further exploration, but doesn't replace the assignment or significantly reduce the learning experience. See me if you have code you'd like to re-use; for code written jointly with others, you must obtain their permission.
Also, in CSE 160, you must write your own answers on the closed-book exams and quizzes. Getting answers from someone else, or providing answers to someone else, is cheating.
More details about the Integrity of Scholarship Policies in effect for this course are described in the following document, which also discusses the code usage Policy for the course:
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 help match you with a new partner, and post to the "looking for a partner" Moodle web board.
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 the deeper intellectual content of the programming 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 [Sun Jan 6 21:25:35 PST 2013]