IJP aims to help students write real, useful applications. The course assessment is intended to reflect this; there are no exams and the assessment is based on two practical programming assignments (assignment1 and assignment2). The second of these involves the development of a realistic application from scratch:
|First assignment||30%||First practical programming assignment|
|Second Assignment||70%||Second practical programming assignment|
The marking scheme explains the criteria used for the assessment. These are based on:
- the code.
- written worksheets.
- a brief demonstration of the running code (see below).
Demonstrating your assignment
After you have submitted the first assignment, you will be asked to show your running code (and your test) to a demonstrator. You should make sure that you are able demonstrate the same version of the code as the one you submitted. The demonstrator will make some notes on your demonstration, and provide you with some feedback.
There will be a similar demonstration after the second assignment, but this will include a small group of other students. This will give you a chance to compare your approach with that of other students.
The demonstrations are compulsory, and you must attend your allocated demonstration sessions (on time).
You may be asked to provide a second demonstration to a marker; for example if there appears to be a discrepancy between the demonstration notes and the submitted code.
The School of Informatics has a Feedback Pledge.
Demonstrators are available throughout the course to provide feedback on your ongoing work during the lab sessions. Please do ask them for their views on your code - even if it apparently works, as it may not always be good in terms of correctness or readability (for example).
Written feedback will be provided on the assignments. This may be brief, but it should be clear from reading this in conjunction with the marking scheme how the final mark has been derived, and what might have been done in order to improve your solution.
Good scholarly practice
Please remember the University requirement as regards all assessed work for credit. Details and advice about this can be found on this page (and links from there). Note that, in particular, you are required to take reasonable measures to protect your assessed work from unauthorised access. For example, if you put any such work on a public repository then you must set access permissions appropriately (generally permitting access only to yourself).
Reading and discussing other people's code is extremely valuable when learning how to write real programs. However, when you submit code for assessment, your own contribution must be completely clear. For example, if you use code derived from elsewhere, or developed together with a colleague, you should comment the relevant section in the code, and explain this clearly on the worksheet.
We routinely run software on the IJP assignments which is extremely effective at detecting sections of code that have been derived from some other source (even when attempts are made to disguise this). If this software detects any unexplained similarities between assignment submissions, we will pass them directly to the Academic Misconduct Officer as a case of suspected plagiarism.