Project Honesty Policy for CMSC 433

Guidelines for ALL Projects

There are a few simple rules that you should keep in mind for all of our coding assignments:
  • Under no circumstances may you copy code from another student.
  • Under no circumstances may you post code from your project in any online forum, code depot, etc. other than your private class CVS repository.
  • If you customize generic code that you have found in an online resource such as a tutorial on a topic, you must cite this source in your code comments.
  • Under no circumstances should you be viewing source-code written by other for these projects.
  • It is always OK to openly discuss course-wide policies on things like programming style, grading, submissions, etc.
  • It is always OK to openly discuss the project specification. Be careful though -- here we are talking about WHAT the project description requires you to implement, not HOW the code will be written! The "how" portion is generally off-limits for discussion except for discussion about what topics or examples from class might apply to a part of the project, or discussions with the instructor or TAs (that means you can't ask students outside the class or family or friends with coding experience either).
  • Remember, looking at another student's source-code is forbidden.



Example Scenarios

Below are some "example scenarios" to help you understand what is okay and what is not. Imagine you are considering the following conversations with a classmate. The green checkmarks mean the conversation is OK, the red X's mean you would be violating the course policy -- these would be considered examples of academic dishonesty.

Something you might say... or
"What does the project description mean by 'test repeatedly for non-deterministic livelock and deadlock'?
"Which code example do you think would help me figure out how to keep the link list from getting corrupted?"
"What did they mean that we should use a runnable object for the thread?"
"I keep failing the second public test! Can you give me a hint on how you got that to work?"
"I've been working on this going from one thread to two for hours and I can't figure out what's wrong! Could you look at my code and help me out?"
"I can't figure this part out -- can I look at your code to see how you did it?"
"Cool, I found a copy of a similar class from a project online and can just drop it in since I can't figure out how to write it!"



Menu Options

Announcements 
Syllabus 
Schedule 
Projects 
Section 0101 Materials 
Section 0201 Materials 
Eclipse/CVS Info 
Grades Server 
Submit Server 
Office Hours 





























Web Accessibility