Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 2

COC281 Software Project Management 2014/15

Exam Summary Feedback

Overall a good set of results this year with an average of 61.4% (which is exactly
the same as last years average!). The highest mark was 85% (last year 87%)
and the lowest was 29% (last year was 19%). Questions 1 and 2 were the most
popular with most students attempting these. Only around 10% tackled question
5.

1a) Reasonable answers but wanted a little more detail than a bullet point.
1b) Some students drew the SDLC and consequently got low marks here.
1c) Generally answered well although some students did not focus on the
implementation stage as asked.
1d) Generally answered well.

2) Question two scored a lot of high marks overall.


2a) Reasonable answers but looking for the environment these days rather than
just advantages of an agile approach.
2b) Answered well although some found additional roles.
2c) Some students drew the standard cost/benefit/functionality graph rather
than showing costs escalating before implementation.
2d) Reasonable answers on the whole. A couple of students drew a
Functionality/Time graph by mistake.

3a) Reasonable answers to this on the whole.


3b) Not many students clearly showed the Build and Fix model developments
taking longer each cycle.
3c) Some top marks for this which is a difficult question.
3d) Lots of good points made.

4a) Average marks typically for this.

4b) On the whole the AoN diagram was correctly drawn giving full marks. A
couple of students restructured the diagram for some reason.
4c) Most students got good marks on this.
4d) A mixture of answers here. Some students could clearly draw an AoA
diagram, while others could not.

5a)Reasonable responses and points made.


5b) Only a few marks here but most did well on this question.
5c) Generally answered well.
5d) Lots of good marks for this relatively easy if it was understood. A couple of
students did not follow through the calculations correctly.

You might also like