IAL IT Unit 4 Exemplar Responses adSAM

INTERNATIONAL ADVANCED LEVEL
INFORMATION
TECHNOLOGY
Exemplars with examiner
commentaries
Unit 4 (WIT14)
Pre-first assessment materials based on additional SAMs
Pearson Edexcel International Advanced Subsidiary in Information Technology (XIT11)

Pearson Edexcel International Advanced Level in Information Technology (YIT11)
Pearson Edexcel International A Level in Information Technology Unit 3 – Exemplar materials

Issue 1 – December 2019 © Pearson Education Limited 2019
1
Introduction
1.1 About this booklet
This booklet has been produced to support teachers delivering the Pearson Edexcel International
Advanced Level in Information Technology specification. These exemplar materials will enable
teachers to guide their students in the application of knowledge and skills required to successfully
complete this course. The booklet looks at questions from the additional Sample Assessment
Materials (additional SAMs) for Unit 4, showing example responses to questions and how examiners
will apply mark schemes to demonstrate how candidate responses should be marked.
1.2 How to use this booklet

Additional Sample Assessment Materials have been used with exemplar responses, and each
question contains:
• Question number and question in full

• Mark scheme for each question
• Exemplar responses for the selected questions
• Exemplification of the marker decision based on the additional SAMs mark scheme,
accompanied by examiner commentary and guidance on how the answer could be improved
where needed.
The exemplification highlights the achievement of the Assessment Objectives alongside

exemplifications of the new format for long answer assessment through levels-based assessment
bands, which centres are required to review carefully.
Centres should utilise the commentaries to support their internal assessment of students and
embed exam skills into the delivery of the specification.
1.3 Further support

A range of materials is available to download from the Information Technology page of the Pearson
website to support you in planning and delivering the new specifications.
Centres may find it beneficial to review this document in conjunction with:

Additional Sample Assessment Materials, Getting Started Guide and the Specification.
Pearson Edexcel IAL Information Technology Unit 4 – pre-first assessment exemplars (additional SAMs). March 2020 1
Command words shown in red are further explained in Appendix 6: Taxonomy, in
the specification.
The additional sample assessment materials use this context:
Mobin owns a company that provides dog walkers. The dog walkers visit the
homes of people who want their dogs taken out for a walk.
Owners can request visits between:
• one and five days a week

• one and three times a day.
The walk durations depend on the number of visits each day.
If the owner requests:
• one visit each day, then the walk duration is 60 minutes

• two visits each day, then each walk duration is 30 minutes
• three visits each day, then each walk duration is 20 minutes.
The total walk duration is always 60 minutes each day.
Staff are employed on either a full-time or a part-time basis and work five
days a week.
Full-time staff work 40 hours a week.
Part-time staff work from 22 to 32 hours a week.
All staff take 20 days holiday a year.
Mobin keeps a list of owners in a single table within the database Dog
Walking.
Mobin uses the Staff spreadsheet to keep a record of the staff and the
owners of the dogs they walk.
Mobin is finding it increasingly difficult to keep track of:
• the dogs and their owners

• the staff who are walking the dogs
• staff holidays.
He wants a solution that will allow him to manage the system more
effectively and reduce the number of errors in record keeping.
Question 1(a) uses this context:
The owner table in the dog-walking database needs to be improved.
1(a)(i) The postcode field in this database will use this format:
2 uppercase letters
1 digit
1 space
1 digit
2 uppercase letters
Set up a format check so that only postcodes in this format are

accepted.
Screenprint the table in Design view, making sure that the format
check can be clearly seen.
Paste the screen print into the appropriate place in the template.
Re-save your template.

(1)
1(a)(ii) Set up a range check on the field NumberWalksPerDay so that only
1, 2 or 3 dog walks per day are accepted.
Screenprint the table in Design view, making sure that the range
check can be clearly seen.

(3)
Mark scheme
Sample response 1 with examiner commentary
(i) One mark was awarded

for a suitable input mask. (1)
(ii) Two marks awarded.

Validation rule would limit entry to the correct range. (1)
Validation text has been added that would provide an appropriate error message. (1)
Total for 1(a): 3 marks
(i) One mark was awarded for a

suitable input mask (1)
(ii) Two marks.
In this example, a value list combo box has been used to evidence a range check.
The Row Source shows that only the values 1, 2 and 3 will appear in the combo box. By itself
this would not be enough to ensure only those values could be selected. However, Limit to
List has been set to Yes. (1)
Whilst there is no validation text, by default, an error message would appear with an
appropriate error message telling the user the value they have tried to input is not in the list
and the list would be shown for them to choose from it. This is the only type of control that
gives an appropriate error message by default. (1)
(i) No mark awarded as this

(ii) Two marks awarded.
input mask would not format
Validation rule would limit entry to the correct range. (1)
the letters to uppercase. > is
Validation text has been added that would provide an
missing. (0)
appropriate error message. (1)
1(b) Mobin needs a form to enter data about an owner who has asked to use
the dogwalking service.
The form must:
• open ready for data entry

• allow data entry of:
 owner details
 dog details
 walk details
• ensure the automatic generation of the walk duration using these
rules:
 1 walk per day is a 60-minute walk
 2 walks per day is 30 minutes each walk
 3 walks per day is 20 minutes each walk
• provide a button to save the entered and generated data in the
table.
(9)
Mark scheme
Form view – this form is bound to the owner table
The form has a
meaningful title that
clearly indicates what The OwnerID
the form will be used field has been
for. The labels are
disabled. (1)
suitable. The first
letter is capitalised for
each word, there is a
space between each
word, and they are
aligned sensibly.
Data entry boxes are
suitably sized for the
data they contain. (1)
A button is present. (1)
The form is clear ready for data entry. (1)
The DaysToWalk field is missing so not all fields from the owner table have been included. (0)
In this paper, there are no marks for the instructions telling the user how to use the form, the
asterisks (*) to show where data entry is required or that the walk duration has been disabled
as the contents of that field are generated. However, these form part of good interface design
and may be awarded marks in future papers.
Design view macros, code etc.
Design view of the form shows that

the fields are bound to the fields in
the owner table.
This also shows that the form is bound and is ready for data
entry as Allow Additions has been set to Yes. The mark for this
was awarded on the previous page.
The WalkDurationMins is correct for each of the

NumberWalksPerDay rules. One mark awarded
for one of them being correct. (1) One mark
awarded for all three being correct. (1)
At least three presence checks have been applied (OwnerFirstname, OwnerSurname,

OwnerAddress, OwnerPostcode, NumberWalksPerDay, DogDetails) and there is a suitable error
message. (1)
The record would save in the correct table i.e. the form is bound to the owner table and the
‘Save’ command has been used. (1) The form would clear ready for data entry and a suitable
message would appear, which is good practice. Whilst in this paper there are no individual
marks for associated to these actions, there could be in future papers as all of the actions work
together to form an efficient, automated save process.
Total for 1(b): 8 marks
Form view – this form is bound to the table
The form has a

meaningful title that
clearly indicates what the
form will be used for. The
labels are suitable. The
The OwnerID
first letter of each word is
capitalised, there is a field has been
space between each disabled (1)
word, and they are
aligned sensibly.
Data entry boxes are
suitably sized for the data
they contain (though
slight weakness for the
owner ID and walk
duration field – too wide).
(1)
A button has been added. (1)

The form is not clear ready for data entry. (0)
All fields from the owner table have been included. (1)
There are no marks for the instructions telling the user how to use the form, the asterisks (*) to
show where data entry is required or that all generated fields have been disabled. However,
these form part of good interface design and may be awarded marks in future papers.
This form goes beyond requirements, i.e. recognising the weakness in the owner table in terms
of non-atomic values (dog breed and name). It made the creation of the automated process far
more complex than required. There is no requirement for candidates to correct shortcomings
such as this in the pre-built table, though they may be asked questions about it.
Design view, macros, code, queries and/or properties screenprints
Design view of the form show that it is a bound form.
WalkDurationMins is correct for each of

the NumberWalksPerDay rules. Mark
awarded for one of them being correct
(1). Mark awarded for all three being
correct. (1)
At least three presence checks have been applied. (1) In this example, they have been applied to
the properties of the field on the form. It is worth noting that this method of applying a
presence check is only suitable for a form that is bound to the table and would not attract
marks on an unbound form. The control source for the fields show that this is a bound form.
This section of the code is above requirements. There was no need to have separate breed
fields etc. and then concatenate. A presence check on the DogBreed AndName field would have
been enough. However,
without it, this particular
form would not save
correctly.
This is part of the save
process, without it the
WalkDuration would not
have a value.
This is also part of the save
process. It closes and opens
the form in order to add the
record to the table.
There is enough to award
the ‘save in the correct table’
mark. (1) The save message does not have a specific mark attached to it nor does setting the
DataMode to ‘Add’; however, they could in future papers as they are both part of an efficient
save process.
Form view screenprint – this form is unbound
The form does not

have a meaningful title. The
labels are not suitable.
There are no spaces
between words and there is
inconsistent use of
uppercase letters for the
beginning of words.
Data entry boxes are not
suitably sized for the data
they contain. The first name
field is too wide in
comparison to the surname
field (they would tend to
hold around the same
amount of characters). The
postcode field is too wide considering it is 7 characters long. The number of walks per day and
walk duration fields are too wide considering they will only hold numbers. (0)
There is no OwnerID field present and the DaysToWalk field is also missing, therefore the mark for
disabling it cannot be awarded (0), nor can the mark for including all of the fields from the owner
table. (0) Whilst the OwnerID is an AutoNumber field, it should still be shown/generated on the
form.
There is a button present but the caption is not appropriate, therefore the mark cannot be
awarded. (0)
The form is not clear ready for data entry. (1)
Macros, code, queries and/or properties screenprints
The form is unbound, i.e. the

fields are not bound to the
fields in the owner table.
There is an attempt to
generate the walk duration.
However, the formula has been
truncated so it cannot be
determined whether it is
correct. (0)
A macro and append query have
been used for the save process in
this example.
A presence check has been applied

to three appropriate fields including
a suitable error message. (1)
An append query is called in order to

append the data from the form to
the table. Design view of the query
clearly shows the fields that will be
appended. None are inappropriate
and there is no truncation. There is
no attempt to append the OwnerID.
However, this is an AutoNumber field
meaning it would be generated
The save message did
automatically. There is enough to
not attract a mark in
this paper. However, it determine the record would save in
could in future papers. the correct table. (1)
1(c) A data entry form should include user interface components that support
users.
Assess the extent to which the data entry form you created in question
1(b) does this.
Type your response in the appropriate place in the template.
Do not include any screen prints.
(9)
Mark scheme
Sample response 1
These are the factors I am going to take into account:
1. The form should only include fields that are relevant, and they should have sensible and
meaningful field names.
2. The form should have a sensible layout so that it is easy to use.
3. The user should know how to use the form and get useful error messages if they do
something wrong.
4. Data entry should be simplified as much as possible.
This is my assessment:
1. The form does not have any fields that are not relevant. All of the fields from the owner
table were included as all of them were necessary in order to get a full record. I made
sure I put spaces between the words in each label to make sure they were easy to read
and that the names reflected the data the user would have to put in so that they knew
what data would need to be put in each field.
2. I think this is one of the most important considerations. The form I have created has a
title, that I think, clearly tells the user what the form is for. They can instantly tell it is to
add owners because this is what the title says. I think this is a very important component
to include. The user could use the form without it but, especially the first time they use
the form, it could take them a while to work out what the form is for.
The form would be very difficult to use if the layout was not logical. I think that my form
does have a logical layout. I have grouped the owner information together and the dog
information together. The boxes around them show a clear divide between the two. I
think it is sensible that the owner information comes before the dog information because
that is what the user would tend to want to enter first. I also think having the save button
at the bottom of the form is logical as that is what they will do last.
3. I think this is also a very important consideration. If the user was not guided on how to
use the form, then they could end up not using the form at all. I think my instructions
telling them what is generated is a very good point because they could be confused as to
why they are greyed out and why they cannot click in them. I think using the asterisks to
show where to enter data is also a very good thing that I have done. They are standard
on forms and known internationally so any user should instantly recognise what they
mean. I think my instructions and asterisks help minimise the data input errors they
could make.
4. I think this is probably the most important consideration if data entry is over
complicated or the user has to do too much then they could become frustrated and stop
using it. I think my form simplifies data entry quite well. I have an input mask on the
postcode so the user cannot possibly enter a postcode in the wrong format. However it
could be a bit better as it does not have an error message or guidance to tell them the
pattern. The form has a combo box for the numebr of walks per day that is very useful.
If the user has forgotten that there can only be between 1 and 3 walks per day then it
doesn’t matter as they can only possibly pick between 1 and 3 from the box. I also think
the form really simplifies how long the walk will be as it does it automatically when the
user picks the number of walks from the combo box. This saves them time and prevents
them making a mistake.
Total for 1(c): 9 marks
Examiner commentary
This is a levels-based question. This means that marks are allocated using the levels descriptors
shown in the mark scheme. The command word is assess; this means that there should be
careful consideration of all the factors or events that apply and identification which are the
most important or relevant. There should also be judgements about significance/importance.
In this response, the factors that will be considered are clearly given as a numbered list. There
is no requirement to do this though it does make clear the factors the candidate thinks are the
most important and it can help with structuring their response. The response also has a clear
section in terms of judgements/assessment.
The response fully meets level 3. A thorough understanding has been shown of the issue. This
can be gathered from the factors they have given and their assessment of each factor. The
assessment is balanced and fully developed including an assessment on the effect to the
user. Evidence from their own solution is given to support judgements throughout.
Sample response 2
These are the important factors I am going to consider:
• which fields to include
• the size of the fields for data entry
• instructions to the user
• disabled fields for system-supplied data
• message confirming successful save
• validation on input data with error messages
• use of selection rather than typing to reduce errors
• order of fields on form
• clear title and field name labels
• use of separate text boxes for up to 3 dogs’ details automatically formatted
• presence checks on most fields
This is my assessment:
The fields I have included are all important for the user to see. The user is not required to enter
duration of walk, but it is shown on the form as a visual confirmation of the number of walks
per day.
The size of the boxes for data entry is appropriate for the expected data.
There are clear instructions to the user to ensure all the required data is entered.
The fields for OwnerID and Duration of Walk are disabled as the information in them is
automatically supplied by the system. The OwnerID field is AutoNumber and the form is
opened in Add mode. The has reduced the chance of user error in calculating the next
OwnerID.
A message is displayed to inform to the user that the data has been added and an empty form
is displayed.
Combo boxes have been used instead of text boxes for the fields NumberOfWalksPerDay and
DaysPerWeek as there are validation rules in place on both, limiting the values that can be
selected. No data can be typed in so values that are not on the list cannot be entered.
The fields are in a logical order on the form so that the user can easily complete the owner
details, the required service and then the dog details.
The form has a clear title which explains its purpose and the labels for each field have been
edited to be clear and easily understood.
As up to three dogs can be entered for each owner (from the supplied data), rather than ask the
user to format the data to match the current records, I have used six text boxes to collect the
data for up to three dogs. On pressing the clearly labelled Save button this data is automatically
formatted and saved into the single field in the table.
Presence checks on most fields will cause a message to be displayed of the field is left blank.
The message states which data needs to be input. There are no presence checks on the fields
for data about second and third dogs as these will not be required in every case.
I think the form is clear and user friendly. It has made it straightforward for the user to enter
data without data input errors and uses label and messages to communicate with the user.
Examiner commentary
In this response, the factors that will be considered are clearly given as a bulleted list. There is
no requirement to do this though it does make clear the factors the candidate thinks are the
most important and it can help with structuring their response. The response also has a clear
section in terms of judgements/assessment.
The response partially meets level 3. There is a thorough understanding of the issue. This can
be gathered from the factors they have given and their assessment of each factor. However,
assessment of the solution is not fully balanced as the effect on the user is not taken into
account in some places or is quite vague. Evidence from their own solution is given to support
judgements throughout.
Sample response 3
The owner form has a clear title ensuring the user knows where they are in the system.
There are clear instructions on how to use the form and how to save the details entered.
All the labels are clear and understandable.
Text box sizes have been adjusted to ensure all the data can be seen, there is no truncation and
they are not too large for the shorter information.
Asterisks have been placed at the end of text boxes where information must be entered.
The OwnerID is generated automatically using Auto number as the data type in the owner
table. This ensures the integrity of the database is not compromised as the OwnerID number
will not be duplicated. This field is locked so it cannot be accidentally edited.
A combo box for the number of walks has been added to the form. This will only allow either
one, two or three to be entered. This will reduce any data entry errors.
The duration of the walks is automatically generated. This field is locked and cannot be
amended by the user.
The save button has a macro attached which ensures all the text boxes are completed. If they
the text boxes are null the macro is set to show a clear error message explaining which field
need to be completed. When all the text boxes are completed the macro runs an append query
to save the record to the table. Finally the macro closes and reopens the Owner form on a new
record so the next owner details can be entered.
Examiner commentary
This response includes factors that are considered to be important and there is an attempt at
an assessment of each. However, there is little to no specific assessment on the effect to the
user who is the most important factor really. Some coherent connections are present, and
assessment is partially developed. It is unbalanced as does not clearly take into account the
user.
1(d) Mobin currently uses the staff spreadsheet to keep a record of the staff
and the dog walks for which they are responsible.
Develop the dog-walking database to add this functionality. You must

create an efficient data structure that minimises data duplication, uses
correct data types and primary keys, and enforces referential integrity.
Produce a screen print that clearly shows the relationships including
table names, field names, and primary keys.
Produce screen prints showing the field names and data types in the
tables you have created.
Paste the screen prints into the appropriate places in the template.
(9)
Mark scheme
• Appropriate naming conventions have been used. tbl prefix and all fields consistently
use an uppercase letter at the beginning of each word. The keys all use uppercase ID.
(1)
• The staff table is present. (1)
• The walk table is present. (1)
• There is a one to many relationship between the owner table and the walk table. (1)
• There is a one to many relationship between the staff table and the walk table. (1)
• The staff table has a suitable primary key StaffID. (1)
• The walk table uses a composite key OwnerID, StaffID. (1)
• The data type Date/Time has been used for the field WalkingStartDate. (1)
• The data type Number has been used for the field ContractedHours. (1)
Total for 1(d): 9 marks
• Appropriate naming conventions have been used. tbl prefix and all fields consistently
use an uppercase letter at the beginning of each word. The keys all use uppercase ID.
(1)
• The staff table is present. (1)
• The walk table is present. (1)
• There is no one to many relationship between the owner table and the walk table.
Referential integrity needs to be enforced in order to see the relationship clearly. (0)
• There is no one to many relationship between the staff table and the walk table.
Referential integrity is missing. (0)
• The staff table has a suitable primary key StaffID. (1)
• The walk table does not have a suitable primary key. (0)
• The data type Date/Time has been used for the field WalkingStartDate. (1)
• The data type Short Text for the field ContractedHours is not appropriate for an integer
number. (0)
Total for 1(d): 5 marks
1(e) Mobin wants to ensure that the data in the database is valid.
You can assume that, for each field, the sample data provided in the
staff spreadsheet contains all the options that should be considered.
Apply validation to the data in the tables you have created.
Produce a screen print in Design view of:
• one length check

• one value lookup
• one table lookup.
Make sure the validation can be clearly seen.

(4)
Mark scheme
A suitable value lookup has been applied.

A combo box has been used. The correct values
“Full Time” and “Part Time” have been used. (1)
A suitable length check has been specified. (1)
A suitable table lookup has been

applied to a foreign key. The
combo box is looking up to the
owner table (1) and limit to list has
been set to ‘Yes’. (1)
Total for 1(e): 4 marks
A suitable value lookup has been applied.

A combo box has been used. The correct values “Full
Time” and “Part Time” have been used. (1)
A suitable length check has been specified. (1)
A table lookup has been applied; however, it is

not suitable. It is looking up into the walk table
(where it is a foreign key) when it should be
looking up into the owner table (where it is a
primary key). (0) Limit to list has been set to
‘Yes’. (1)
Total for 1(e): 3 marks
1(f) Import the data from the staff spreadsheet into the dog-walking
database.
Produce screen prints of the tables you have created showing at least
five records and the full record count. (If the fields are too wide to fit on
one page, truncated data is allowed.)
(2)
Mark scheme
The walk table has 36 records, which is correct. (1)

The staff table has 6 records, which is correct. (1)
Total for (f): 2 marks
The walk table has 36 records, which is correct. (1)
The number of records is not

showing for the staff table.
Therefore it is impossible to
determine whether it has 36
records. (0)
Total for 1(f): 1 mark
Question 2(a) uses this context:
Mobin wants information about part-time staff.
2(a)(i) Create a query that will display the names and contracted hours of
part-time staff.
The information should be displayed in alphabetical order of first name

within highest to lowest contracted hours.
Screenprint your query in Design view, making sure that all required
tables, fields and criteria can be clearly seen.

(7)
Mark scheme
Only the staff table Only suitable fields have been

has been included in included, contracted hours for
the query (1) the descending sort, both
names and the StaffStatus in
order to find part time staff. (1)
StaffStatus uses
correct critieria in
order to find part
time staff. (1)
Only ContractedHours, StaffSurname and StaffFirstname will be displayed. This is appropriate

but could also have chosen to display StaffStatus. (1)
Contracted hours show a descending sort (1) and StaffFirstName has an ascending sort. (1)
The descending sort takes place before the ascending sort giving the correct nesting. (1)
Total for 2(a)(i): 7 marks
The walks table should

not be included as it is
irrelevant to the WalkingStartDate
query. (0) should not have
been included in the
query grid. It is
irrelevant. (0)
Criteria would find

those who work
part time. (1)
The WalkingStartDate should not be displayed. It is irrelevant. (0)
Contracted hours cell does not have a descending sort. (0)

StaffFirstName has an ascending sort. (1)
One of the sorts is missing therefore the correct nesting cannot be achieved. (0)
Total for 2(a)(i): 2 marks
2(a)(ii) Export your query as an html document.
Screenprint the browser window showing the contents of your html

document.
(1)
Mark scheme

The results of the query have been exported. The
browser can be seen. (1)
Total for 2(a)(ii): 1 mark

The browser cannot be seen. Therefore, it is impossible to
know whether the export has taken place correctly. (0)
Total for 2(a)(ii): 0 marks
The results of a query has been exported. The browser can be seen. The query is not the query
required. However, it is the skill of being able to export a query as HTML that is being tested so
the mark has been awarded. (1)
Total for 2(a)(ii): 1 mark
Question 2(b) uses this context:
Mobin wants information about part-time staff.
Mobin charges owners £15.00 a day for the dog-walking service.
Staff members give weekly invoices to the owners.
Mobin wants to use the standard invoice in Figure 1. This will use information
from the database.
Figure 1
2(b)(i) Create a query that will extract appropriate data from the database for a
staff member of Mobin’s choice.
tables, fields, criteria and parameters can be clearly seen.
(5)
Mark scheme
Correct
related tables
added. (1)
A parameter has been added that would allow the staff member to be found (1) and the input
message is sensible. (1)
There is no attempt to calculate the weekly cost. If the calcuation could have been seen in 2(b)(ii)
then the mark would have been awarded. However, it cannot be see there. (0)
The weekly cost field has not been generated so there is no name to check in the query. However,
the label on the report evidence in 2(b)(ii) was suitable ‘Weekly Cost’ so the mark can be awarded.
(1)
Total for 2(b)(i): 3 marks
The evidence does not show which tables were included in the query so a judgement cannot be
made as to whether they are the correct related tables. (0)
A parameter has been added that would allow the staff member to be found (1) and the input
message is sensible. (1)
The WeeklyCost has been calculated using a suitable expression (1) and it has a suitable field
name. (1)
Correct
related tables
added. (1)
WeeklyCost
generated
correctly. (1)
Generated field
has suitable field
name. (1)
Parameter added to
suitable field (1)
with an appropriate
input message. (1)
Correct related
tables added (1)
WeeklyCost truncated so cannot determine Just enough evidence to suggest a

whether it has been generated correctly. (0) parameter has been added to the
However, it does have a suitable field name. (1) correct field. (1) However, not
enough evidence to award the mark
for an appropriate input message
as it has been truncated. (0)
Question 2(b)(ii) uses this context:
Mobin plans to print one invoice per page.
He will use the report format shown in Figure 1.
Use your query from question 2(b)(i) to extract the data for the report.
The invoice date must be set to the current date automatically.
There must be a page break after each invoice.
2(b)(ii) Create the report.
Screenprint:
• your report in Design view

• your method of ensuring there is a page break after each invoice
• the first page of your report in Print Preview view.

(6)
Mark scheme
Title is in the
page header.
(1)
The date is
automatically
generated. (1)
Monetary amounts
are displayed as
currency with two
decimal places. (1)
Layout is as given with no truncation. (1)

Standard text and labels are as given. (1)
The page break has been forced after the detail section, which is a suitable location. (1)
Total for part 2(b)(ii): 6 marks
Title is in the page

header. (1)
The date is
automatically
generated. (1)
Page break has

been added in a
suitable place. (1)
Layout is as given with no truncation. (1)

Standard text and labels are as given. The last three lines of text have been emboldened.
However, this is a minor difference so the mark has been awarded. (1)
Monetary amounts
are displayed as
currency with two
decimal places. (1)
Title is in the page

header. (1)
It does not make sense to

have the WalkingStartDate
as the date for the invoice.
It is a weekly invoice so
needs to be the current
date. (0)
There is no evidence of ensuring each invoice prints on a separate page. (0)
There is a line missing from

beneath the word Mobin and the
line underneath the title is not
straight. There is not enough
evidence to award layout mark. (0)
Standard text and labels are as

given. (1)
Monetary amounts are

displayed as currency
with two decimal places.
(1)
Question 3 uses this context:
Mobin needs to know the number of owners per staff member.
3(a) Create a query that will extract the staff name and the total number of
owners for each staff member.
tables, fields and criteria can be clearly seen.
(3)
Mark scheme

StaffSurname (or
StaffFirstname) is present. (1)
There is a count on OwnerID,

which would give the number
of owners. (1)
The generated field has a

sensible name. (1)
Total for 3 (a): 3 marks
StaffSurname (or StaffFirstname) is
present. (1)
There is a count on OwnerID, which

would give the number of owners. (1)
The generated field has been left at

default; this means it will be
unsuitable when the query is
executed. (0)
3(b) Mobin would like the information in chart format to make it easier to read.
The chart needs to clearly show the information from the query you
created inquestion 3(a).
Create a report that displays this information as a chart.

Screenprint your report in Report view.
(6)
Mark scheme

Suitable chart has been
created. (1)
Meaningful chart title has

been used. (1)
Staff names are shown

on X axis. (1)
Full names of staff are

shown. (1)
Data values are shown.

(1)
The chart is fit for purpose. There is no legend and the elements have been sized
appropriately. (1)
Suitable chart has been
created. (1)
Meaningful chart title has

been used. (1)
Staff names are shown in the

legend. (1)
Legend shows full names of

staff are shown. (1)
Data values are shown. (1)
The chart is fit for purpose. There is a legend and the elements have been sized appropriately.
(1)
Total for part 3(b): 6 marks
4 The database must be tested to check that the solution meets the
specified requirements.
One of the specified requirements in the scenario is that owners can

request visits between one to five days a week.
You should plan tests that will prove only values within the range will be
accepted.
Do not test for non-numerical values.
Do not test for null values.
Complete the table given in the template to plan the tests for this
requirement.
(6)
Mark scheme

Comments
Test Number 1
Test Data 1 Suitable test data for boundary testing though should really
include the field name (DaysToWalk). (1)
Test Type Boundary Type of test named correctly.
Expected Data accepted Expected results correct.
Results
Comments
Test Number 2
Test Data 5 Suitable test data for boundary testing though should really
include the field name (DaysToWalk) (mark already awarded).
Expected Data accepted Expected results correct for the test data.
Results
Comments
Test Number 3
Test Data 0 Suitable test data for extreme testing though should really
Test Type Extreme Type of test named correctly.
Expected Error message Expected results are correct for test data and type of test.
Results displayed; field
cleared
Comments
Test Number 4
Test Data 6 Suitable test data for extreme testing though should really
include the field name (DaysToWalk) (mark already awarded).
Expected Error message Expected results are correctly for test data and type of test.
Results displayed; field
cleared
Comments
Test Number 5
Test Data 3 Suitable test data for normal testing though should really
Test Type Normal Type of test named correctly.
Expected Data accepted Expected results are correct.
Results
The type of test is correct in all tests. (1)
The expected results are correct in all tests. (1)
Values 1 and 5 were tested as boundary and 0 and 6 as extreme. (1)
Total for 4: 6 marks
Comments
Test Number 1
Test Data Number of Walks The question did not ask for testing on the NumberWalksPerDay field,
per Day = 0 it wanted the DaysToWalk field testing. However, this is also a field
that includes a range, so it has been accepted as being suitable test
data for an extreme test on the field given. Good that the field name
has also been given otherwise some of the test data would not have
been suitable when compared to the mark scheme. (1)
Expected Error message Expected results are correct.
Results
Comments
Test Number 2
Test Data Number of Walks Suitable test data for extreme testing (mark already awarded).
per Day = 6
Expected Error message Expected results are correct.
Results
Comments
Test Number 3
Test Data Number of Walks Suitable test data for boundary testing. (1)
per Day = 1
Expected Accepted and the Expected results are correct. The field tested means the expected
Results Walk Duration (Mins) results are more complicated than what was required for testing the
calculates and DaysToWalk field. If a value is accepted, then the WalkDuration should
updates to 60 automatically calculate and it would be expected that this would be
identified, and the value would be given.
Comments
Test Number 4
Test Data Number of Walks Suitable test data for boundary testing (mark already awarded).
per Day = 3
Comments
Test Number 5
Test Data Number of Walks Test data is fine for normal testing (it is the type of test that is
per Day = 2 incorrect). (1)
Test Type Boundary Type of test is incorrect. This is normal testing.
Type of test does not match value in all cases (test number 5, value is normal testing, type of
test identified as boundary). (0)
The expected results match the all cases. (1)
Values 1 and 5 were tested as boundary and 0 and 6 as extreme. (1)
5 Mobin wants to track staff holidays in the dog-walking database.
Figure 2 shows an extract from the spreadsheet he uses at present.
Figure 2
Mobin wants the dog-walking database to:
• ensure that only one member of staff can take a holiday at any one
time
• show whether a temporary member of staff has been arranged to
cover the holiday
• track the number of days holiday each member of staff has used
• track the number of days holiday each member of staff has left to
take.
Analyse why the present database structure does not allow the four
identified tasks to be carried out.
Recommend how the database structure could be modified to carry out

the four identified tasks.
Type your response in the appropriate place in the template.

(9)
Mark scheme
Sample response 1
Analysis of structure:
The staff table has primary key of StaffID. This means the StaffID is unique and can only
appear in the table once. The extract shows that staff take more than one holiday in a year so
there would be a need to repeat the StaffID which means it would no longer be suitable as a
primary key. Even if another ID were introduced there would still be repeating groups of
attributes i.e. StaffSurname, StaffFirstname, StaffTelephone, StaffStatus, ContractedHours.
Recommendations for improvements:

A new holiday table could be created. This could have HolidayID as a primary key. StaffID
would be a foreign key so that a holiday could be associated with a member of staff.
AnnualDays could stay in the staff table as the information is only needed to be recorded
once. NumHoursToCover would not need to be stored at all as the information is already in
the staff table but named ContractedHours. HolidayStartDate, HolidayEndDate, Comments
and CoverArranged would move to the holiday table as they are different for each holiday the
member of staff takes. NumDays, NumDays and NumHolsLeft would not need to be stored as
they can be calculated from the AnnualDays and the holiday dates. A new field could be added
called HolidayAgreed which would be a Boolean field. This would show whether the member
of staff has been given the holidays.
This would mean that once holiday start and end dates have been input on a form a query
could be used to check whether any member of staff is off during those times. It would use the
dates as criteria and only for holidays that have been agreed.
A query could be used to see whether cover has been arranged. Parameters could be used to
find the staff member and holiday dates only for the holidays that have been agreed.
Calculations could be used to show Mobin how many days holiday have been taken and
remain. These could be on a form, in a query or on a report. The holiday start and end dates
would be used to determine how many holidays have been taken and these would be
subtracted from the annual days to determine how many are left.
Examiner commentary
This is a levels-based question. This means that marks are allocated using the levels
descriptors shown in the mark scheme. The command words are analyse and recommend;
this means that the response should examine elements in detail and provide support for a
course of action.
The first section of the response includes a clear analysis of the perceived problems. There is
no requirement to do this, but it can help candidates focus on the problem and then ensure
they focus on recommendations specifically relate to the problem.
The analysis section clearly shows understanding of shortcomings of the current structure in
terms of what Mobin wants the database to do. The recommendations given do relate to
solving the identified shortcomings and they are fully developed. The response is fluent and
logical throughout.
The recommendations would lead to an appropriate, workable solution.
Sample response 2
My analysis:
Another table would need to be added to the structure. These fields cannot be added to the
staff table as the StaffID, primary key, will not allow duplicates and the 20 days holiday
allowance will not be all taken at the same time.
Recommendations for improvements:

The new table would need to be linked to the staff table in a one to many relationship. The
table would need to have a clearly identifiable name, e.g. tblHoliday. It would need a primary
key to ensure no data duplication and a foreign key of StaffID to allow the one to many link.
A form needs be created to make entering and saving the holidays more efficient.
Fields required:
• HolidayID which will be generated automatically either with an expression or simply

using AutoNumber in the table. This field would be locked to prevent accidental
amendment.
• StaffID will be a drop-down list which is limited to list with a clear error message in-case
of data entry error.
• Holiday start date and holiday end date fields would be formatted to a date field to
avoid incorrect data entry. A query would need to be run when these fields have been
completed to check the dates have not already been booked. If the dates have been
booked a clearly worded error message will appear,
• Num Days will be generated using a date function to calculate the number of days
between the holiday start date and the holiday end date. This field will be locked as no
data entry will be required.
• Num Hols Left will also be generated using an expression. A calculation would be
needed to work out the total number of days taken and subtract this from 20, therefore
an Annual Days text box/field would not be required. This field would be locked.
• Number of hours to cover would not be needed as this information is already stored in
the staff table.
• Cover Arranged will be a Yes/No, Boolean field.
• A macro will be created which will be attached to a save button. The macro will ensure
all fields are completed and if not will send a clearly worded error message to the user.
It will run an append query to save all the fields barring fields to the Holiday table.
A holiday report could also be generated using similar fields/expressions as Mobin will need to
know whether all the dog walks are covered, and which members of staff will be walking the
dogs. It may be that if cover cannot be arranged for the dates required, he may want to ask
the member of staff to take their holidays at another time. Leading to the need for a field to
say whether the holiday has been approved or declined.
Examiner commentary
This is a levels-based question. This means that marks are allocated using the levels
descriptors shown in the mark scheme. The command words are analyse and recommend;
this means that the response should examine elements in detail and provide support for a
course of action.
The first section of the response includes an analysis of the perceived problems. However,
reference to ‘these’ fields is quite vague. The fields could have been given to make it clearer
and to judge whether there is, indeed, a problem with them.
The recommendation of a new table is valid and the identification of the relationship, etc.
Again, it could be perceived to be lacking in terms of the fact it does not really say what fields
would be in the table, etc. However, the recommendations for the form are very detailed and
the fields that would be in the table can be taken from here. There are some really good ideas
for the form including calculated fields, user input aids and how the save would take place.
The save does indicate which fields are in the table.
Analysis could be slightly better in that it is not fully clear which fields are causing the
problems etc. The recommendations are sound and developed. The recommendations would
lead to an appropriate, workable solution.
This response would be awarded full marks but for different reasons compared to response 1.
Response 1 analysis is very detailed, recommendations are workable but would need
development. Response 2 has weaker analysis but fully developed recommendations.
FOR INFORMATION ABOUT EDEXCEL, BTEC OR LCCI
QUALIFICATIONS VISIT QUALIFICATIONS.PEARSON.COM
EDEXCEL IS A REGISTERED TRADEMARK OF PEARSON EDUCATION LIMITED PEARSON
EDUCATION LIMITED. REGISTERED IN ENGLAND AND WALES NO. 872828

REGISTERED OFFICE: 80 STRAND, LONDON WC2R 0RL
VAT REG NO GB 278 537121
GETTY IMAGES: ALEX BELMONLINSKY
Pearson Edexcel International A Level in Information Technology Unit 1 – Exemplar materials

Issue 1 – January 2020 © Pearson Education Limited 2020
2

IAL IT Unit 4 Exemplar Responses adSAM

Uploaded by

Copyright:

Available Formats

IAL IT Unit 4 Exemplar Responses adSAM

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IAL IT Unit 4 Exemplar Responses adSAM

Uploaded by

Copyright:

Available Formats

INTERNATIONAL ADVANCED LEVEL

Pearson Edexcel International Advanced Subsidiary in Information Technology (XIT11)

Pearson Edexcel International A Level in Information Technology Unit 3 – Exemplar materials

1.1 About this booklet

1.2 How to use this booklet

• Question number and question in full

The exemplification highlights the achievement of the Assessment Objectives alongside

1.3 Further support

Centres may find it beneficial to review this document in conjunction with:

The additional sample assessment materials use this context:

Owners can request visits between:

• one and five days a week

The walk durations depend on the number of visits each day.

If the owner requests:

• one visit each day, then the walk duration is 60 minutes

The total walk duration is always 60 minutes each day.

Full-time staff work 40 hours a week.

Part-time staff work from 22 to 32 hours a week.

All staff take 20 days holiday a year.

Mobin is finding it increasingly difficult to keep track of:

• the dogs and their owners

Set up a format check so that only postcodes in this format are

Re-save your template.

Re-save your template.

(i) One mark was awarded

(ii) Two marks awarded.

(i) One mark was awarded for a

(ii) Two marks.

(i) No mark awarded as this

Total for 1(a): 2 marks

The form must:

• open ready for data entry

A button is present. (1)

The form is clear ready for data entry. (1)

Design view macros, code etc.

Design view of the form shows that

The WalkDurationMins is correct for each of the

At least three presence checks have been applied (OwnerFirstname, OwnerSurname,

The form has a

A button has been added. (1)

Design view of the form show that it is a bound form.

WalkDurationMins is correct for each of

The form does not

The form is not clear ready for data entry. (1)

Macros, code, queries and/or properties screenprints

The form is unbound, i.e. the

A presence check has been applied

An append query is called in order to

Total for 1(b): 3 marks

All the labels are clear and understandable.

Develop the dog-walking database to add this functionality. You must

Apply validation to the data in the tables you have created.

Produce a screen print in Design view of:

• one length check

Make sure the validation can be clearly seen.

Re-save your template.

A suitable value lookup has been applied.

A suitable length check has been specified. (1)