22.07.2013 Views

The MBC information booklet - RMIT University

The MBC information booklet - RMIT University

The MBC information booklet - RMIT University

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

14.41 Photocopiers<br />

14.41.1 I need to use a<br />

photocopier.<br />

Can I get<br />

access to<br />

one?<br />

14.42 Plagiarism<br />

14.42.1 Academic<br />

Integrity<br />

Workshop<br />

available<br />

14.42.2 What is<br />

Plagiarism?<br />

Chapter 14: Frequently asked questions<br />

You can find photocopiers in the Swanston library (Building 8, Level 5) and in Building 10,<br />

Level 4. Note, though, that photocopying is not free.<br />

At the start of each semester you can attend a workshop on academic integrity. To register<br />

to attend one of these sessions click the ‘Week 1 Activities’ link at<br />

www.rmit.edu.au/csit.<br />

Plagiarism is cheating. Specifically, it is wrong to submit an assignment that contains<br />

other people's work without acknowledgement, or to help someone else to plagiarise.<br />

Students are encouraged to discuss their work and seek advice when they are struggling<br />

with problems or assignments. However, students need to be aware that:<br />

• <strong>The</strong>y must not submit material that is not their own work.<br />

• <strong>The</strong>y must not submit work they don't fully understand.<br />

• <strong>The</strong>y must not submit work that has been copied from elsewhere, unless they have<br />

permission from the lecturer to include copied material and there is full<br />

acknowledgement of which material is copied.<br />

• <strong>The</strong>y must not enable other students to plagiarise their work.<br />

While it is fair practice for a student to seek advice while developing a solution to an<br />

assignment, the solution must primarily be the student's alone.<br />

As a rule of thumb, an assignment is plagiarised if writing it (or writing any non-trivial part<br />

of it) involved having another solution to work from; or having a sketch of a solution written<br />

by someone else; or even having a sketch of a solution developed together with a friend.<br />

If the outline of a solution or part of a solution is from a textbook, or was provided by the<br />

lecturer, this material can only be used with the permission of the lecturer, and must be<br />

acknowledged in the assignment's documentation.<br />

In group assignment work, there is a shared responsibility by all group members to ensure<br />

that the work has been completed within the group. It is essential to contribute honest work<br />

to the joint submission and to clearly indicate who is responsible for each individual<br />

section.<br />

Other situations are also treated as plagiarism. In particular, giving a solution to another<br />

student is plagiarism; if a student gives their work to a friend or friends, all are cheating<br />

and are equally disciplined.<br />

<strong>The</strong> only case in which it is acceptable for a student to include other people's work in an<br />

assignment is when there is explicit permission from the lecturer. In this case, the part of<br />

the assignment that is copied must be clearly acknowledged. For example, if the copied<br />

work is included in a program, the program should include all of the following forms of<br />

acknowledgement:<br />

• A detailed comment at the start of the program stating that part of it is copied, and<br />

stating who wrote the copied part.<br />

• Clear comments in the body of the program marking the start and end of the copied<br />

material. <strong>The</strong>se comments must also give the name of the author.<br />

• If code has been obtained from elsewhere, then modified by the student, the<br />

modifications need to be explained. For example, a comment might have the wording<br />

"<strong>The</strong> original code obtained from Jos Leubnitz was modified to print more detailed<br />

error messages". Each adaptation of the original code should be documented.<br />

93

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!