Professional Documents
Culture Documents
SDT September 2015 Marking Scheme Final
SDT September 2015 Marking Scheme Final
SDT September 2015 Marking Scheme Final
Marking Scheme
Markers are advised that, unless a task specifies that an answer be provided in a
particular form, then an answer that is correct (factually or in practical terms) must be
given the available marks. If there is doubt as to the correctness of an answer, the relevant
NCC Education materials should be the first authority.
This marking scheme has been prepared as a guide only to markers and there will
frequently be many alternative responses which will provide a valid answer.
Each candidate’s script must be fully annotated with the marker’s comments (where
applicable) and the marks allocated for each part of the tasks.
Where markers award half marks in any part of a task, they should ensure that the
total mark recorded for the task is rounded up to a whole mark.
Marker's comments:
Moderator's comments:
The program algorithms should make effective use of all the tools
students have available - at a bare minimum, it should involve
functions, loops, selections and either array or string manipulation. It
is not necessary for this section of the assignment that the program
does what is required - all that is required is that the structured
outlined below are properly implemented in pseudocode. The 25
marks for this section are broken down as follows:
The marks for this deliverable are based on the program actually
meeting the requirements of the brief, regardless of how those
requirements are met. This will be based in large part on the desk-
checks that students provide - they should prove to you that their
programs work, you are not required to prove it for them. The 25
marks for this part of the assignment are broken down as follows:
Page 2 of 5
Software Development Techniques © NCC Education Limited 2015
Task Guide Maximum
Marks
Handles User Input and output
The program should allow for fact (1 mark) and cost (1 mark), mod (1 5
mark) and seed (1 mark) values to be provided using appropriate
data types (1 mark).
Program functionality
The program must meet the following functionality requirements:
25
3 Testing Data
Page 3 of 5
Software Development Techniques © NCC Education Limited 2015
Task Guide Maximum
Marks
Choosing test cases appropriate for black box testing
Award the full five marks for a set of testing data that permits for all 5
combinations of equivalence and boundary conditions to be tested
(as outlined above)
4 Desk Checking
The desk checks that students provide should support your marking
of deliverable two, but the format of the desk-checks themselves is
also under examination regardless of whether they support the case
for a working program. The 25 marks for this deliverable then are
broken down as follows:
Having a desk check for each black box test in deliverable three
10
Award two marks for each desk-check they produce that matches up
to their black-box testing cases in deliverable three, up to a
maximum of 10 marks.
Having a desk check for each white box test in deliverable three
Award two marks for each desk-check they produce that matches up
to their white-box testing cases in deliverable three, up to a 10
maximum of 10 marks.
25
Total: 100 Marks
Page 4 of 5
Software Development Techniques © NCC Education Limited 2015
Learning Outcomes matrix
Grade descriptors
Page 5 of 5
Software Development Techniques © NCC Education Limited 2015