COMP112 Assignments
COMP112 2018 Tri 1: Assignments
Note that the demos will only run on the school workstations. They cannot be copied or downloaded to run at home. See also the weekly timetable with lecture, lab, and tutorial times. Assignments are generally due at 10am on Thursdays. Assignments will be made available on Thursdays at 4 pm. You can get online help from a tutor via the web interface orcomp112-help@ecs.vuw.ac.nz See more information about
Assignments, Submission and Marks
| Assig | Comment | Out | Due | Zip File |
Submit Answers |
Marks and Feedback |
|
|---|---|---|---|---|---|---|---|
| Lab 0 | 8 Mar | 15 Mar | zip | Submit | |||
| Assig 1 | 15 Mar | 22 Mar | zip | Submit | Marks | ||
| Assig 2 | 22 Mar | 5 Apr | zip | Submit | Marks | ||
| Assig 3 | 5 Apr | 12 Apr | zip | Submit | Marks | ||
| Assig 4 | 12 Apr | 19 Apr | zip | Submit | Marks | ||
| Break | |||||||
| Assig 5 | 19 Apr | 3 May | zip | Submit | Marks | ||
| Assig 6 | 3 May | 10 May | zip | Submit | Marks | ||
| Assig 7 | 10 May | 17 May | zip | Submit | Marks | ||
| Assig 6+7 | You can do this in place of Assig 6 and Assig 7 | 3 May | 17 May | zip | Submit | Marks | |
| Assig 8 | 17 May | 24 May | zip | Submit | Marks | ||
| Assig 9 | 24 May | 31 May | zip | Submit | Marks | ||
| Assig 8+9 | You can do this in place of Assig 8 and Assig 9 | 17 May | 31 May | zip | Submit | Marks | |
| Assig 10 | 31 May | 10 Jun | zip | Submit | Marks | ||
| Assig 10 Comp102 | You can do this simpler alternative to Assig 10 (max 80%) | 31 May | 10 Jun | zip | Submit | Marks | |
| Make up Assignments | |||||||
|---|---|---|---|---|---|---|---|
| Makeup Assig 1 | 27 Apr | 29 Jun | zip | Submit | |||
| Makeup Assig 2 | 28 May | 29 Jun | zip | Submit | |||
Structure of the Assignments
The assignment has "Exercises", "Core", "Completion", "Challenge", and "Reflection" parts.- Core parts: the parts that everyone should aim to do. They cover the basic principles that the assignment is intended to help you learn. You should complete all the core parts before going on the the other parts; if you are having difficulty with the assignments, it is important that you try to finish the core parts.
- Completion parts: should be attempted only when you have finished all the core parts of the assignment. They may cover additional programming features that are useful but not absolutely central to the course (or not central yet) and will give you more practice in programming. If you use up all your time for the course on the core parts, you should not spend more time on the completion parts.
- Challenge parts: will allow you to demonstrate your mastery of the course and are required to get an "A" for the program. Completing them is intended to be a challenge!
- Reflection part: getting you to reflect on and think about aspects of the assignment to help you get a deeper understanding of the material. Everyone should do this.
Marking
Each program in this assignment, as in all assignments, will be marked out of 100. The marks will be allocated according to the following criteria:- 0: did nothing or submitted too late (after the answers were posted),
- 1-49: attempted, but many errors, or incomplete (Grade: D or E)
- 50-64: got most of the Core working correctly, but little or none of Completion (Grade: C- to C+)
- 65-79: got most of the Core and Completion working (Grade: B- to B+)
- 80-100: got the Core and Completion working, and attempted some of the Challenge (Grade: A- to A+) The Reflection will also be marked out of 100, with 50 for an acceptable attempt, and up to 100 for displaying some insight. The marks will be returned electronically, along with feedback comments from the markers.