This is an individual assignment. You may not collude with any other individual, or plagiarise their work. Students are encouraged to discuss the assignment topic, but all submitted work must represent the individual's understanding of the topic. Students are expected to present the results of their own thinking, problem solving, and coding. Suspected collusion or plagiarism will be dealt with according to RMIT Academic Integrity policy. Being an advanced course, we will require students to be fully aware of academic integrity and behave professionally and ethically. If you do not, we will pursue the strongest consequences available to us under the RMIT regulations.
Some guidelines to take into account:
-
Never copy or use another student's work (even if the other student "explains it to you first") and never give or show your written work to others. Keep the collaboration verbal and high-level, without sharing or showing any code to each other.
-
Never copy your solution, or part of it, from the web. An assignment is not an open-source project and it is not acceptable to search for help in web forums or to look for solutions that others have made. The safest way is to directly not web search for any solution, but to build them from first-principle yourself. We will use powerful code similarity detection tools for plagiarism detection among submissions in the class and online code. We trust you will be professional and respectful of the teaching staff and the course, do not let us down!
-
Adapting someone else solution does not make it your own work: you are meant to generate the solution to the questions by yourself. You may however reuse code or techniques that are auxiliary to the problem being solved (e.g., code to sort a list of numbers), as long as you understand well the code being reused and document where it comes from.
-
Reading pseudo-code for a technique, from text-books, papers, the web, or slides, is completely fine and even expected (e.g., reading and studying the pseudo-code for minimax or A* algorithms).
-
Verbal discussion with your student peers of techniques and even solutions is totally OK and encouraged, as long as it is kept at verbal level and conceptual. It is not OK then if you show full or snippets of code, let alone if you share them.
Overall, the aim of the course and this project is your learning. Consider that everything we are teaching here is NOT new and has been in textbooks for decades: we are not inventing anything but helping you learn and acquire knowledge and skills that will be useful for you as a Computer Scientist. So, don't trick yourself and don't take risks; just see how far you can go by developing your solutions to the projects.
You can read more about the above points and strategies in the course FAQ: In a code assignment/project, how do I make sure I do not go against academic integrity?
Forum postings on assignment: Do not ever post any information on the forum that may disclose how to solve a question or what the solution may be. You can only post assignment related questions for clarification on what is being asked, questions about auxiliary programming tasks (e.g., how to sort a list of numbers in Python), or questions about generic issues and problems with the techniques study in the course (e.g., why does A* keep a closed list?). Posts discussing possible solutions or strategies may directly be considered plagiarism, see above. If in doubt, do not post and ask your question to the lecturer or tutor instead before going public.