Timeline for How do you assess programming related topics and avoid student cheating?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2018 at 9:45 | history | edited | famargar | CC BY-SA 3.0 |
Added clarifications
|
| Jan 22, 2018 at 9:37 | comment | added | famargar | Glad it helped. I added a small description above to make the point that some of the suggestions above are already implemented in e-learing platforms. The problem you are facing is very general, and the solution above applies to most subjects (other than input randomisation, that applies only to quantitative subjects) | |
| Jan 22, 2018 at 9:36 | history | edited | famargar | CC BY-SA 3.0 |
Added clarifications
|
| Jan 21, 2018 at 10:09 | vote | accept | Ziqi | ||
| Jan 21, 2018 at 10:09 | comment | added | Ziqi | thank you. indeed the question is how to make the assignment harder to plagiarise, and it does take a lot more effort to address. I am thinking whether this has been the problem for most practical-based subjects... and certainly taking some elements into exam instead of using coursework/assignment can help | |
| Jan 18, 2018 at 16:00 | history | answered | famargar | CC BY-SA 3.0 |