AY2017/8 Semester 1
|0||Volume of Box||21 Aug (Mon), 8am||Deadline: Before your first discussion session in week 3.
Please attempt this after your Intro Workshop.
|1||Three Simple Exercises||28 Aug (Mon), 8am||6 Sep (Wed), 5pm||Ex3 worksheet: pdf||Directory|
|2||Nanotable (0)||4 Sep (Mon), 8am||13 Sep (Wed), 5pm||Directory|
|3||Control Structures||7 Sep (Thu), 8am||18 Sep (Mon), 5pm||Ex2 worksheet: pdf||Directory|
|4||Arrays||22 Sep (Fri), 8am||11 Oct (Wed), 5pm||Ex2 worksheet: pdf||Directory|
|5||Two-dimensional Arrays||11 Oct (Wed), 5pm||25 Oct (Wed), 5pm||Ex3 worksheet: pdf||Directory|
Plagiarism, in general, is an act of academic dishonesty. In the context of a programming module, it refers, but is not limited, to cases of a student copying others' work and passing it off as his own, or a student who allows his own work to be copied by another.
We would thus advise you against collaborating on lab questions, or discussing the solution among yourselves or openly on the IVLE forum. However, you may raise your doubt about the task statements on the IVLE forum.
We encourage discussion among the students, but you need to draw a line between discussion and copying. Two students who get together to discuss a problem and derive the algorithm, and then leave to write the code on their own is fine. But most often than not, during the discussion the students tend to produce the code, a partial code, or a skeleton of the code together, and their end products will look quite identical. You need to be aware of this and to avoid getting into such situation.
For take-home lab assignments, we understand that sometimes you may discuss the problems with your friends as part of your learning experience. However, try to refrain from copying the programs from others without putting in your own real effort. If we encounter such cases, we will not award the attempt-mark to the students.
For more details on plagiarism, please refer to the page on NUS Plagiarism Notice.