Integrity of Scholarship

The basic goal for CSE 8B is:
Develop and confirm your individual abilities in computing.

In CSE8B PSAs (problem solving assignments) will be completed individually -- not in pairs. You are expected to perform all these components of each PSA on your own (reflecting the processes you will face in your career):

Read and understand a problem description/specification.

Design an algorithmic approach for the problem. This may involve deciding what classes (tester/application, object classes, etc.) should be designed and what data should be stored and methods should be supported.

Outline a set (that means many more than 1!) of sample inputs and outputs that you believe serve as "correct" inputs and outputs for the problem. (Sometimes a sample solution might be provided for you to use to define correct input/output executing pairs.)

Implement (write the code) a solution.

Debug.

Test the solution on your sample inputs and outputs.

Debug.

Submit (using bundle) the appropriate files.

While it is true that much real world programming happens in teams, there are still expectations of an individual programmer to complete (independently) subparts of a larger project. You will be developing that proficiency in this and many later classes.

When you run into problems, barriers, or bugs -- you should attempt to work through them on your own first. There are a variety of techniques we recommend including:

Identify the location of the error (either from the compiler error, or through use of a debugger or print statements for runtime errors).
Read and trace (manually your code).
Read in the textbook or look at Java API method descriptions on the web.
Review lecture notes.
Put in print statements printing appropriate variable values.
Take a break (get a drink, sleep).
Try a different input value.
Comment out complicating code.
Ask a tutor.

We repeat, it is important that you try to debug and fix your errors on your own.

However, we also know (and you know) that sometimes it is a lot easier for a fresh pair of eyes to "see" a bug. Can you ask another student in the class? Maybe.

We don't want you suffering needlessly when 2 seconds of someone else's time could help you move past your current bug. But, we want you to make an honest effort yourself. And we don't want someone else to read and copy your code without understanding for themselves why you developed the code that way.

So, in what scenarios is it OK to ask a fellow student for help? In what scenarios is it not OK? Beyond the intent described above, you will be helping us define the answer to this question. In the first half of the class, we'll ask you to submit a scenario that is either OK and one that is beyond the line in terms of acceptable "assistance" with a peer in the class. Then we'll have a discussion about the scenarios you have submitted and collectively decide what our rules for 8B will be for the rest of the class.

What happens if I cheat?

If you do cheat, we will enforce the UCSD Policy on Integrity of Scholarship (see the General Catalog or the corresponding web page (scroll 2/3 of the way down)). This means: You will get an F in the course, and the Dean of your college will put you on probation or suspend you from UCSD.

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