Unit 2 Creating Systems to

Manage Information – 2019

Level 3 National in
Information Technology

Part A
Additional Sample Assessment
Marking Guidance
Contents
Introduction .............................................................................................. 3
Activity 1 – Database Relationship Screenprint (45 mins) ................................ 3
Trait 1 ................................................................................................... 3
Trait 2 ................................................................................................... 3
Activity 2 – Table Structures and Validation (45 mins) .................................... 4
Trait 1 ................................................................................................... 4
Trait 2 ................................................................................................... 4
Trait 3 ................................................................................................... 4
Trait 4 ................................................................................................... 4
Band 1 ................................................................................................... 5
Band 2 ................................................................................................... 5
Band 3 ................................................................................................... 5
Band 4 ................................................................................................... 5
Activity 3 – Queries and Report (40 minutes) ................................................ 6
Trait 1 ................................................................................................... 6
Trait 2 ................................................................................................... 6
Trait 3 ................................................................................................... 7
Activity 4 – Testing (20 minutes) ................................................................. 8
Activity 5 – Evaluation (20 minutes) ............................................................. 9

AddSAM 2019
Introduction
This solution provided is only one example. Candidates could have approached it several
different ways. It is important to read this guidance with each activity. If you are in any doubt
whether the method a candidate has used is valid, please refer to your team leader. Do not
assume a method that differs from solution is incorrect.

Activity 1 – Database Relationship Screenprint (45 mins)

How examiners must approach marking this activity

Trait 1 • Candidates should be using all and only attributes given in data file.
• More than two attributes (including keys) in wrong table class as significant
data redundancy.
• Two attributes in wrong table/missing – Band 2
• One attribute in wrong table/missing – Band 3
• If truncated see how many missing from what you expect to see
Trait 2 Relationship lines
• Do not need to check the fields they link to, referential integrity or anything
else, only the lines are important for this
Relationship types
• Check referential integrity
• Must be links on correct fields and referential integrity present

Band 1 1 relationship line correct (ignore relationship type)

Band 2 two relationship lines correct (ignore relationship type)

Band 3 1 out of 2 relationships and relationship types correct (exactly three

tables, two relationships and two relationship types present)

Band 4 all relationship lines and relationship types correct (exactly 3 tables, 2
relationships and 2 relationship types present)

Note foreign key evidence for activity 2 taken from this screenprint.

Activity 1 – Database Relationship Screenprint – AddSAM 3|Page

Activity 2 – Table Structures and Validation (45 mins)
How examiners must approach marking this activity

Trait 1 Look for naming conventions and whether fields are sensible
• tbl for table
• fields should be consistent either have spaces or do not, camel case etc,
so long as consistent. Fine for IDs to have no spaces even if other fields
have spaces
• If standard naming conventions are not used then cannot get higher than
band 2 for trait 1.
Trait 2 Check against their structure in activity 1.
• Primary and foreign keys should match
• No new foreign keys should be introduced
• No activity 1 then check against ERD given in solution.
• Band 3 can also be read as “all foreign and most primary”
Trait 3 Look at data types.
HouseNum: Text
TicketPrice: Currency
Event Date: Date/Time
NumTickets: Number
Rest short text
Primary any suitable
Foreign matches primary (Number foreign, AutoNumber primary etc.)
• Class same datatype incorrectly used as one error.
• Limited means more than two different datatypes are incorrect.
Trait 4 Validation must relate to the scenario and activity 2 for bands 3 and 4
Validation rules must contain relevant validation text for band 4.
Scenario requirements
• Evening Christmas events have been planned for 20 to 22 December
2019.
• Each event has a different ticket price.
• There are two types of seat: seats without tables and seats with tables.
• There must be at least one ticket purchased with each sale.
• A sale cannot exceed eight tickets.

Activity 2 requirements
• a record will not save without the surname, house number and postcode
of the customer being present
• a record will not save if the postcode is not in the correct format
• a record will not save if the event selected is invalid
• a record will not save if the seat type is invalid
• a record will not save if the number of tickets purchased is below the
accepted range
• a record will not save if the number of tickets purchased is above the
accepted range

Watch out for screenprints that do not show the actual field the
validation is applied to.

Just acceptable for keys

Would need to see name of table and field name (could be written)

Just acceptable for non-keys

Would need to see the name of the field (could be written)

Activity 2 – Table Structure – AddSAM 4|Page

 Presence Check (1 required)
Should be on any of these 3 fields
• Surname
• House number
• Postcode

Length Check (1 required)

• Any text field
• A length that is suitable
Value lookup or range check (1 required)
• NumTickets
o Range is between 1 and 8 with suitable validation text
o Lookup values are 1 to 8 must have limit to list set to Yes to be
classed as a range.
• SeatType
o values are table/no table
o does not need required set to yes but will help with testing activity
if they do that
Table Lookup (1 required)
• Should have been applied to EventID if the requirements of the activity
are taken into account.
• Could use another foreign key
• Limit to list must be set to Yes
Anything else is not suitable
Format Checks (1 required)
• Postcode
o input mask, >LL0\ 0LL
o or appropriate validation rule and text

Band 1 • At least 1 type of validation has been attempted – though may be

inaccurate
Band 2 • 2 types of validation are accurate
• Lookups shown in data sheet view validation text missing, limit to list not
set to yes, presence check on primary key – can still be classed as being
accurate in this band
• If lookups shown in datasheet view must be showing the drop down items
in the combo box
Band 3 • 3 types of validation are accurate
• Lookups shown in data sheet view validation text missing, limit to list not
set to yes, presence check on primary key – can still be classed as being
accurate in this band
• If lookups shown in datasheet view must be showing the drop down items
in the combo box
Band 4 • All validation correct including suitable validation text, limit to list set to
yes on table lookup

Activity 2 – Table Structure – AddSAM 5|Page

Activity 3 – Queries and Report (40 minutes)
(a) Create a query to display an alphabetically sorted list of the events running on the 20th and
21st of December. It must show event description and event ticket price only.

(b) Create a query that will calculate:

• the number of table tickets sold
• the income the tickets sold would generate.
Display:
• the event description
• the number of table seat tickets sold
• the income generated.

Trait 1 Band 1 1 query or the report present. At least two fields appropriate
Band 2 2 queries or query and report present. More than two fields
appropriate
Band 3 Both queries and report present. Fields mostly appropriate
Band 4 Query A
In the grid Displayed
• EventDate • EventDescription
• EventDescription • EventTicketPrice
• EventTicketPrice
Query B
In the grid Displayed
May include more (relevant) but at least • EventDescription
• EventDescription • Table Tickets Sold
• TableSeatsSold • Income
• SeatType
• Income
Report
EventDescription, Number of Customers All appear once only
Table seats sold, Non table seats sold per event
Total Tickets

Trait 2 9 sort/criteria/calculations in total

Query A (2) ascending sort (EventDescription), criteria for EventDate (20 and 21
December 2019)

Query B (3) criteria for table seats (table), number of table tickets sold
(Sum(NumTickets)), income (sold * EventTicketPrice)

Report (4) number of customers, number of table tickets*, number no table

tickets*, total tickets *may use grouping to achieve as opposed to calculations

Band 1 1 query or report has been attempted, little, if any are correct
Band 2 2 queries or 1 query and report has been attempted, 3 are correct
Band 3 All 3 have been attempted, 5 are correct
Band 4 All 3 have been attempted all are correct

Activity 3 – Queries and Report - AddSAM 6|Page

 Trait 3
Band 1 Will have attempted at least one task
Data may be truncated
May be too many records showing due to lack of grouping or lack
of relationships in query window
Band 2 Will have attempted at least two tasks
Limited truncation
Report pdf may be missing
Query B uses grouping and has correct relationships shown in the
top of the query window
Band 3 Will have attempted 1 query and the report
Queries
• Ordering of columns in the query results is appropriate
• No truncation
• Generated fields may not have appropriate names
• Grouping and relationships correct (Query b)
Report
• Includes suitable title
• Includes suitable field labels
• No truncation of data
Band 4 Will have attempted all tasks
Queries
• Ordering of columns in the query results is appropriate
• Income is shown as currency with 2 decimal places
• No truncation
• Generated fields have names that aid readability
• Grouping and relationships correct
Report
• Includes suitable title
• Includes suitable field labels
• No truncation of data
• Good use of white space

Activity 3 – Queries and Report - AddSAM 7|Page

Activity 4 – Testing (20 minutes)
How examiners approach marking this activity

Tests to be carried out

• a record will not save without the surname being present

• a record will not save if the postcode is not in the correct format
• a record will not save if the event selected is invalid
• a record will not save if the seat type is invalid
• a record will not save if the number of tickets purchased is below the accepted range
• a record will not save if the number of tickets purchased is above the accepted range

Band 1 • Not all of the tests requested will be present or they may be inappropriate
• Type of test may not be present or may be incorrect
• There will be no test data, or it will not relate to the test being carried out
• Expected results may be inappropriate
• At least 1 test result will be appropriate
• Errors may be present that have not been identified
Band 2 • All of the tests will be present, but they may not be entirely appropriate
• Type of test may not be present or may be incorrect
• There will be test data, but it may be incomplete or general e.g. leave
surname blank rather than stating exactly what data will be used in each field
• Expected results will be sensible but may not be detailed e.g. ‘error message’
rather than ‘error message saying surname has to be present’
• Actual results will be present, but some may not be entirely appropriate
• Errors may/may not have been found
Band 3 • All tests will be present, and they will be appropriate
• Test data will be specific for all fields
• Type of test will be mostly accurate
• Expected results will be specific
• Actual results will show all of the test data used and any relevant messages
• Do not penalise if there are no errors and the testing is accurate

Activity 4 – Testing – AddSAM 8|Page

Activity 5 – Evaluation (20 minutes)
How examiners approach marking this activity

• Read evaluation and determine best fit for band based on understanding of technical
concepts and technical vocabulary
• Assign position in that mark band based on evaluative content

What should be evaluated:

• how well your database structure has minimised data duplication

• how well your database structure meets these requirements:
o there are two types of seat: seats without tables and seats with tables.
o there must be at least one ticket purchased with each sale.
o a sale cannot exceed eight tickets.

Band 1 Will be very superficial with major omissions

Band 2 Will discuss some aspects sensibly though may not fully explain them or relate
them very well to their own solution.
Band 3 Will discuss data duplication in terms of
• repeated customer data
• repeated event data
• removing repeated data into table whilst maintaining the link
• may pick up that seat type cannot meet 3NF as they cannot introduce
any new fields i.e. it does not depend on the primary key.
Needs to be clear they are talking about their solution and not just trying to
slip technical vocabulary in. Need to see clear understanding

Meeting requirements
Seat type may already have been discussed in terms of not meeting 3NF.
Should also talk about their choice of validation and why it was the best.
Should talk about their choice of validation for number of tickets sold and why
it was the best.

Activity 5 – Evaluation – AddSAM 9|Page