Academic Integrity

To reinforce all points addressed below, every student in CSE 11 must read, understand, and sign the Integrity of Scholarship Agreement before completing any work for this course. The Agreement will be part of your PA0.

You will also be completing the Source Code Plagiarism tutorial and take a screenshot of your certificate after finishing it:

http://libraries.ucsd.edu/assets/elearning/cse/cseplagiarismlink/story_html5.html

This will also be part of your PA0.

The basic rule for CSE 11 is: Work hard. Make use of the expertise of the CSE 11 staff to learn what you need to know to really do well in the course. Don't cheat.

If you do cheat, we will enforce the UCSD Policy on Integrity of Scholarship (see the General Catalog or the corresponding web page, posted on TODO under “Academic Integrity”). This means: You will get an F in the course, and the Dean of your college will put you on probation or suspend you or dismiss you from UCSD.

What counts as cheating?

In CSE 11, you can read books, surf the web, talk to your friends and the CSE 11 staff to get help understanding the concepts you need to know to solve your PA problems. However, you can only work with your partner on PAs and you can only work with a partner if it is allowed for that particular PA. Furthermore, when you are working with your partner, you must be working together, co-located, on the same part of the assignment, not dividing up the work, but working jointly and each understanding what solution you have produced and how and why it works.

The goal of CSE 11 is about skills as much as it about knowledge. Future instructors, employers, and colleagues will expect that you will attain a certain proficiency in problem solving. Using unauthorized aids in doing your work will prevent you from attaining the proficiencies that others will expect. Meeting or not meeting these expectations relate directly to getting internships, retaining employment, and success in your future studies.

In CSE 11, using program code that someone else has written (unless it was explicitly provided as part of the assignment), or providing program code to someone else, or turning in code that you have written with someone else other than your partner, is considered cheating. Yes, we do electronically check every program that is turned in.

Also, note that taking other students’ iclickers and help them answer iclicker questions is considered cheating.

How can I be sure that my actions are NOT considered cheating?

To ensure you don't have a problem with this, here are some suggestions (in this discussion we aren't talking about your assigned partner):

Don't even look at or discuss another student's code for a PA you are working on, 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.

If you are talking to another student about the assignment, don't take notes, and wait an hour afterward before you write any code.

Also, in CSE 11, you must write your own answers on the closed-book exams. Getting answers from someone else, or providing answers to someone else, is cheating.

Policy on integrity of scholarship

New guidelines

For more information on academic integrity, please visit the Academic Integrity Office at 301 University Center (Room 115), call 858-822-2163, email at mailto:aio@ucsd.edu, or visit the website at http://academicintegrity.ucsd.edu. The Academic Integrity Office offers academic integrity training and support to students, faculty and staff at UC San Diego and can be scheduled for presentations, workshops or 1:1 consultations.