[Homework 1] [Homework 2] [Homework 3] [Homework 4] [Homework 5] [Homework 6] [Homework 7] [Homework 8] [Homework 9] [Homework 10] [Homework 11] [Homework 12]

COMP2100
Homework

One component of the assessment for COMP2100 in 2003 is weekly homework. This will be due in your registered lab class each week.

Marks for homework

Your tutor will mark each homework exercise out of 2 as follows:

• 0 means either you did not attend your registered lab class, or you attended but had not done the homework.

• ½ means you attended the lab and had done something on your homework but it was unsatisfactory.

• 1 means you attended with the homework done and it was a bare pass, marginal.

• 1½ means you attended with the homework done and it was satisfactory.

• 2 means you attended and your homework was outstanding, nearly perfect.

These marks will count towards your final homework mark, up to a maximum of 20 marks. Since there are twelve weeks of lab classes, this means you get two weeks off for illness, pressure of other work or any other reason you might not be able to attend with the homework done.

Late homework will not be accepted, for any reason, including illness. If you are ill for more than two weeks, come to see me (the lecturer).

Due Dates

Homework N will be due in your registered lab class in Week N+1. This includes Week 9, when you will do the lab exam.

The phrase "in your registered lab class" means that tutors have been instructed not to mark homework for a student who is not on their class list.

For those of you in the Friday lab class, the homework due on the Good Friday holiday will be due and assessed the following week (that is, Week 9, after the break), along with the next homework. So you will have two lots of homework due on the Friday of Week 8.

Aims

The aim of the weekly homework is to provide you with an opportunity and an incentive to do regular programming. It also provides an opportunity for you to practice the PSP while carrying out a routine programming task -- one that isn't a major challenge involving new concepts and techniques. The programs should be relatively straightforward. The challenge is to write them well, in a reasonable time, with as few defects as possible and to learn to predict your own process.

In 2002 and 2003 many students found that the homework helped them to improve their programming skills quite dramatically. What I had expected to be easy tasks turned out to be rather difficult at first for many students, but by mid-way through the semester their skills had improved to the point where they were much more confident and capable programmers. If you are weak in Eiffel programming at the start of the semester, look at these weekly programming exercises as an opportunity to turn that weakness into a strength.

[Homework 1] [Homework 2] [Homework 3] [Homework 4] [Homework 5] [Homework 6] [Homework 7] [Homework 8] [Homework 9] [Homework 10] [Homework 11] [Homework 12]