The George Washington University
School of Engineering and Applied Science
Department of Computer Science
CSci 51 -- Introduction to Software Development
PLAGIARISM AND COLLABORATION ON PROGRAMMING PROJECTS
The project work you turn in must represent your own work and not the work
of someone else. On the other hand, it is unreasonable to expect that you
will work in a complete vacuum, without ever speaking to a classmate. The
purpose of this note is to give you some guidance about the areas in which
it is appropriate to discuss project phases with your classmates. Violating
these guidelines may result in a charge of academic dishonesty.
Plagiarism
The term plagiarism describes an attempt to claim work as your own,
which you have copied from another person, whether that other person knows
about it or not. In a class like this, plagiarism includes copying program
code, data, documentation, etc. Plagiarism is simply not allowed. If you
submit another student's work as your own, you will be charged with a violation
of the GW Academic Integrity Code.
Collaboration
Collaboration is defined as two or more students working together
on a phase of a project. Working together does not mean that one student
does the work and the other student just copies it! Collaboration is allowed
under certain conditions, as long as you are honest about it.
You are taking this class to learn important fundamental things about
computing, and I must give you a grade that fairly represents what I think
you've learned. Therefore, I need to know that your work is your
work, so I need to limit the collaboration somewhat. For purposes of projects
in this class, here are some guidelines as to which phases of a project
are appropriate for discussion with friends, and which are inappropriate.
| OK |
Preliminary analysis of problem |
| OK |
Developing basic algorithm |
| OK |
Developing a test plan |
| NO |
Coding in the programming language |
| NO |
Proof-reading the program before compiling |
| OK |
Interpreting error messages from the compiler |
| OK |
Interpreting exception tracebacks and logic errors at execution
time |
| NO |
Modifying your code to correct compilation or execution errors |
| NO |
Writing up the Case Study |
Project Signature Page
The first page of each project must be a photocopy or printout of the project
signature page, with your original signature and date, and any other
required information filled, in.
"Truth in Advertising"
If you receive help from another student you must list your collaborator's
name on the signature sheet, giving the phase(s) in which your collaborator
assisted you.
Save Your Projects!
You are required to save all your projects until the end of the semester,
after grades have been reported. Be prepared to re-submit these to the
instructor if he or she asks you to do so.
Protect Yourself
If you suspect that another student is misusing your work (for example,
one of your printouts disappeared), report this immediately to the instructor,
to protect yourself against a charge of plagiarism if your work is copied
by another student.
Read Academic
Integrity in Computer Science and theGW
Code of Academic Integrity carefully.