Assignments

COMP102 2024 Tri 1: Assignments

IntroductoryLab will be made available on 4 Mar at 9am
Assignments are made available at midday on Thursdays.
Assignments are generally due at 10am on Thursdays.

See the weekly timetable with lecture, and lab times.

Labs are In-person: Go first to CO 219, and use CO 238 as an overflow lab.

See more information about

• Types of Assignments
• getting help online: You can ask tutors a question at any time via the web interface or email to comp102-help@ecs.vuw.ac.nz
• submitting assignments
• Extension Requests for COMP102.
• Your Marks for all assignments and tests.

Assig	Type of Assignment	Out	Due	Lab remarking	Submit Answers	Marks and Feedback
Introductory Lab (instructions + zip)		4 Mar	5 Mar	N.A.	Submit
Assig 1 (instructions + zip)	Pass/Fail (P/F)	7 Mar	14 Mar	25-26 Mar	Submit	Marks
Assig 2 (instructions + zip)	Pass/Fail (P/F)	14 Mar	21 Mar	15-16 Apr	Submit	Marks
Assig 3 (instructions + zip)	Pass/Fail (P/F)	21 Mar	28 Mar	22-23 Apr	Submit	Marks
Assig 4 (instructions + zip)	Pass/Fail (P/F)	18 Apr	24 Apr	6-7 May	Submit	Marks
Assig 5 (instructions + zip)	Pass/Fail (P/F)	25 Apr	2 May	13-14 May	Submit	Marks
Assig 6 (instructions + zip)	Pass/Fail (P/F)	2 May	9 May	20-21 May	Submit	Marks
Assig 7 (instructions + zip)	Graded	9 May	20 May	N.A.	Submit	Marks

Note that the demos will only run on the school workstations. They cannot be copied or downloaded to run at home.

Types of Assignments

Pass/Fail (P/F) Assignments

The first 6 assignments are P/F assignments. These are formative (i.e. designed for you to learn from them) and you have several attempts to pass them, following the rules below. Each of the P/F Assignments has two parts.

1. Online part: This is a number of small problems based closely on the content taught in the videos and class. When you attempt an assignment, you get immediate result/feedback. You can attempt them multiple times (unlimited), but you must successfully solve each problem before the assignment deadline.
2. Programming part: This is a bigger assigment, where you implement the solution in BlueJ and submit the code for evaluation. We provide a template, where you implement your own code. Each problem will have two levels
   1. Pass level: To pass you must successfully implement a solution to all parts of this level. All students must pass these.
   2. Challenge level: This will be additional challenging work that students can do as extra work. These will not be marked, but is available to provide challenges for top-level students. From week3, there is an optional challenge session where students can show and discuss their challenge-level work.

If you because of extenuating circumstances (e.g. illness) cannot meet the deadline, it is important to apply for an extension in the extension system as soon as possible. It is harder to get an extension after the deadline than before.

Marking

Your work will receive one of four grades in the assessment system:

• 3 : Pass (recognition of challenge level)
• 2 : Pass
• 1 : Redo
• 0 : No attempt, late attempt, or an attempt that was not substantial (i.e. too little work)

If you receive 2 or 3, you have passed (you will not receive specific feedback.)

If you receive a 1, you will be allowed to redo the assignment (with potential support from tutors in labs) and get it regraded in your following lab (the lab following the release of grades). If successful, this will change the grade to a 2 grade.

If you receive a 0, the assignment is a fail, and cannot be reattempted.

Impact of failing P/F Assignments

To get the full grade on the course (i.e. the overall result of the other assignment and tests) at least 5 of the 6 p/f assignments must be passed. Below is a list of the maximum grade you can achieve overall for different numbers of successfully passed p/f assignments:

• A+: Passed 5 or 6
• B+: Passed 4
• C+: Passed 2 or 3
• C-: Passed 0 or 1

Graded Assignment

The assignment has "Core", "Completion", and "Challenge" parts.

1. Core part: the part that everyone should aim to do to pass. 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 other parts; if you are having difficulty with the assignments, it is important that you try to finish the core parts.
2. Completion parts: should be attempted only when you have finished all the core parts of the assignment. They cover additional programming features that are useful but not absolutely central to the course (or not central yet) and 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.
3. Challenge parts: will allow you to demonstrate mastery of the material. Attempting the Challenge parts is required to get some kind of "A" on the program; completing them is intended to be a challenge!

Marking

The graded assignment program will be marked out of 100. The mark 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+)

This grade will be worth 20% of the final grade.