CS 420/520 Object-Oriented Programming
Academic Integrity Policy
Winter Quarter 2013
No familiarity with object-oriented programming is
assumed; students who have experience with Java or C++
should be prepared to unlearn some of what they think
they know. Prior experience with Smalltalk is not
required. The class assumes a working knowledge of
discrete mathematics and machine organization — the
fundamentals of instruction coding and data
representation in the computer's memory. (Students who
have completed PSU CS 310 and CS 340 will be well
Topics covered will include responsibility-driven design, test-driven development, refactoring, code reading, reuse, parametrization, inheritance and programming patterns.
Specific Learning Objectives
On completion of this course, students should be able to
Students are at university for two reasons: to learn stuff, and to gain a credential. Because the credential is important to many of our students, part of my role as a professor is to make sure that it has value. This means ensuring that the degree is awarded only to those students who have mastered the material in my course.
I have every sympathy for those who have difficulty with the material and seek the assistance of the instructor, the TA or their fellow students. I have no sympathy at all for those who decide that the fastest way to a degree is to cheat. I have been responsible for having cheating students dismissed from the university in the past, and I will not hesitate to seek to have cheaters dismissed in the future.
The most common form of academic dishonesty — cheating — is representing the work of others as your own. In all written material, it is expected that you will use others' work, but when you do so it must be in a way that makes it absolutely clear that someone else's work is being cited, and who is the original author. If you reproduce someone else's work in a way that makes it appear to be yours, you are guilty of plagiarism—in other words, of cheating.
Cheating on an assignment or exam will result in an automatic zero grade for that piece of work, and the initiation of disciplinary action at the University level.
Cheating and collaboration
I encourage collaboration on certain assignments; I will not tolerate cheating. Where is the line between these activities?
First, if an assignment is explicitly set up as a team assignment, you are of course allowed — indeed, required — to collaborate with the members of your team. In this case I will generally require only one completed piece of work to be turned in from the team as a whole.
For individual assignments, I encourage you to talk about the problem with your fellow students. During such discussion, you may even write something, perhaps the code of a critical method, as a group. If you do this, there is a danger that you might reproduce that group work as if it were your own. To guard against this danger, do the following: after the group session, destroy all the notes and code fragments that you may have brought away with you. Then go and do something else for an hour or two: go for a walk or a bike ride, play your favorite sport, go to the gym: do something to flush your short-term memory. Then sit down with a blank sheet of paper or a blank workspace and start work on your own solution. If you have a photographic memory or otherwise won't be able to forget what you have seen someone else write, then don't participate in collaborative problem-solving sessions.
If I see the same code or writing assignment from two
or more students I will take this as evidence that these
guidelines have been ignored, and will assign a grade of
zero to all of the students involved.
Grade Distribution: 55% on homework assignments, 35% on the class project, and 10% on attendance and class participation. Your participation will be used to judge whether you are keeping up with the reading assignments.
Most recently modified on Monday
Andrew P. Black