Summary Pearson BTEC Level 3 Information Technology - Unit 2 Creating systems to manage information – EXPLANATION OF EACH ACTIVITY + MARKSCHEME + EXAMPLES!!! – 2024

Unit 2 – Creating Systems to Manage Information
January 2019 – new format

Script A

Activity Band Mark Max
Mark
Part A
1 – Database relationship screenprint 4 8 8
2 – Table structures 4 8 8
3 – Queries and report 3 9 12
4 – Structure testing 3 5 6
5 – Structure evaluation 2 4 6
Part A Total 34 40
Part B
6 – Interface and functionality 3 10 14
7 – Interface and functionality testing 3 5 6
8 – Interface and functionality evaluation 3 5 6
Part B Total 20 26
Overall Total 54 66

,Contents
Activity 1 – Database Relationship Screenprint, Band 4, Marks 8...................................................................................................................................... 3
Activity 2 – Table Structures and Validation, Band 4, Marks 8........................................................................................................................................... 4
Activity 3 – Queries and Report, Band 3, Marks 9 .............................................................................................................................................................. 7
Activity 4 – Structure Testing, Band 3, Marks 5 ................................................................................................................................................................ 13
Activity 5 – Structure Evaluation, Band 2, Marks 4 .......................................................................................................................................................... 17
Activity 6 – Interface and Functionality, Band 3, Marks 10 .............................................................................................................................................. 19
Activity 7 – Interface and Functionality Testing, Band 3, Marks 5 ................................................................................................................................... 30
Activity 8 – Interface and Functionality Evaluation, Band 3, Marks 5 .............................................................................................................................. 38




Script A January 2019 – new format 2|P a g e

,Activity 1 – Database Relationship Screenprint, Band 4, Marks 8




Trait Band Comments
1 4 • All fields are in the correct tables
• Primary keys are correct
• Correctly normalised with no data redundancy
2 4 • Correct relationships and relationship types throughout
Band 4 The learner has fully normalised the data set and has provided an accurate solution. PrppertyPostCode is not penalised.
Mark 8 Spellings are not checked and it is clear to see what the field refers to.




Script A Part A - January 2019 – new format 3|P a g e

,Activity 2 – Table Structures and Validation, Band 4, Marks 8
Trait 1
• A recognised naming convention has been used throughout (tbl for
tables, also consistent naming of tables. Consistent naming of fields
– camel case
• There is a spelling error PrppertyPostCode – it is naming conventions
that are checked, not spellings. It is clear to see what the field refers
to

Trait 2
• Learner has identified all primary and foreign keys from their ERD in
Activity 1

Trait 3
• Bedrooms – Number
• PropertyHouseNumber – Short Text
• RentalStartDate – Date/Time
• RentalEndDate – Date/Time
• MonthlyRent – Currency
• TenantID (primary and foreign – Short Text)
• All data types correct




Script A Part A - January 2019 – new format 4|P a g e

, Presence Check Length Check Format Check




Range Check Table Lookup




Trait 4
The presence check is relevant to the scenario, activity 2 and testing. It includes a suitable error message. The length check is fine and evidence for
that can be taken from the presence check, length check or format check screenprint. More than one type of validation can be shown in a single
screenprint if it is relevant. For example the evidence for the presence check, length check and format check could all have come from the same
screenprint i.e. postcode – all three were checks on that field were relevant to the scenario/activity 2/testing. One screenprint would have been
enough to show all three. The range check is fine. The paper asked for a range check rather than Lookup check – though either would have been
acceptable. The table lookup is fine – it has been added to a foreign key and lookups to to the primary key. Limit to List has been set to Yes.
Script A Part A - January 2019 – new format 5|P a g e