Edexcel GCSE Computer Science (1CP2) Exam Questions

Award up to two marks for a linked description such as:

• The compiler reports all syntax errors after translation has finished (1) whereas the interpreter stops at the first error it finds (1)
• The interpreter reports a syntax error as soon as it finds one (1) and does not translate/execute any more of the program (1)
• The compiler continues translating after an error (1) and reports the errors at the end (1)
• The interpreter stops translating when it reaches an error (1) but the compiler finishes translating before reporting errors (1)

Do not accept answers about fixing/correcting errors or about object code.

Do not award 'the compiler finds more errors' without saying errors are reported at the end.

Award up to two marks for a linked explanation such as:

• Data is encrypted/scrambled (1) so it cannot be read/understood if it is intercepted (1)
• The customer's bank/personal details are kept secure/private (1) because the data is encrypted/scrambled during transmission (1)
• The customer's login details/password cannot be read by an eavesdropper (1) because HTTPS encrypts/scrambles the data sent to and from the web server (1)

For both marks, the expansion must follow/associate with the statement.

Allow 'scrambled' as an alternative to 'encrypted'.

Do not accept 'it is more secure/safe' or 'the data is secure' on its own, without saying how it is made secure (e.g. encryption/scrambling).

Do not accept faster loading/speed, or claims that HTTPS stops viruses or always proves the website is genuine.

Indicative content

Administrator accounts

• An administrator account can create new user accounts for new employees and delete accounts when employees leave.
• The administrator can reset a forgotten password, so an employee can get back to work without sharing another person's account.
• The administrator can set the access rights for each user or group, so designers get access to project folders and only directors can open salary files.
• Administrator privileges should be given to only a few trusted employees, as administrators can change any settings on the system.

Standard user accounts

• Designers should use standard user accounts, so they cannot install unauthorised software or change system settings.
• A standard user can be given permission to read and write files in the project folder that their team uses.
• Standard users should not be able to change other users' permissions, so the access rules cannot be removed by accident.
• If a standard user tries to open a file without permission, the operating system denies access.

File permissions

• Each file or folder can have permissions that allow a user to read, write or delete it.
• Project folders can be set so all designers can read and write the files inside them.
• Salary files can be set so only directors can read them, and other users are denied access.
• Permissions can be set for a group of users, such as all designers, which is quicker than setting them for each person.
• A file can be made read-only for standard users, so they can view it but cannot change it.

Levels

• Level 0 (0 marks): No rewardable content.
• Level 1 (1–2 marks): Basic, independent points are made, showing elements of understanding of key concepts/principles of computer science. (AO1) The discussion will contain basic information with little linkage between points made or application to the context. (AO2)
• Level 2 (3–4 marks): Demonstrates adequate understanding of key concepts/principles of computer science. (AO1) The discussion shows some linkages and lines of reasoning with some structure and application to the context. (AO2)
• Level 3 (5–6 marks): Demonstrates comprehensive understanding of key concepts/principles of computer science to support the discussion being presented. (AO1) The discussion is well developed, with sustained lines of reasoning that are coherent and logically structured, and which clearly apply to the context. (AO2)

Level 3 responses must cover administrator accounts, standard user accounts and file permissions, and apply them to the design company.

Do not accept general operating system functions such as managing the processor or memory unless they are explicitly linked to controlling what a user can access.

Indicative content

Control of the hardware

• Low-level languages can read and write the contents of registers and memory addresses directly, so the firmware can take the values from the distance sensors without calling a library routine.
• Assembly language instructions can read from and write to specific input/output ports on the vacuum cleaner's processor, so the motors can be switched on and off directly.
• The programmer decides exactly which processor operations are carried out and in which order, which matters when the vacuum must reverse away from a step or an obstacle.
• A low-level language puts nothing between the program and the hardware, so the programmer can control the hardware of the vacuum cleaner precisely.

Efficiency of the code

• Assembly language code can be hand-optimised instruction by instruction, so the code that checks a sensor is as short as possible.
• The programmer can choose which registers hold values that are used again and again, which cuts down the number of memory accesses the firmware needs.
• A hand-written low-level program can be made compact, so it is more likely to fit in the small amount of memory the vacuum cleaner has.
• Because each instruction does one defined job, the time taken to react to a sensor reading is predictable, which suits firmware that must not overrun.

Link between the language and the processor

• Low-level languages are processor-specific, so the instructions used are those of the exact processor in the vacuum cleaner rather than general statements that need translating.
• Each assembly language instruction maps to one machine code instruction, so the programmer knows precisely which processor operation will be carried out by each line of code.
• An assembler turns each mnemonic into its machine code equivalent, so the machine code running on the vacuum cleaner's processor is exactly what the programmer wrote.
• Code written for a different processor would have to be rewritten, which is acceptable here because the vacuum cleaner always uses the same processor.

Levels

• Level 0 (0 marks): No rewardable content.
• Level 1 (1–2 marks): Basic, independent points are made, showing elements of understanding of key concepts/principles of computer science. (AO1) The discussion will contain basic information with little linkage between points made or application to the context. (AO2)
• Level 2 (3–4 marks): Demonstrates adequate understanding of key concepts/principles of computer science. (AO1) The discussion shows some linkages and lines of reasoning with some structure and application to the context. (AO2)
• Level 3 (5–6 marks): Demonstrates comprehensive understanding of key concepts/principles of computer science to support the discussion being presented. (AO1) The discussion is well developed, with sustained lines of reasoning that are coherent and logically structured, and which clearly apply to the context. (AO2)

Within Level 1, award 1 mark for a single basic point and 2 marks for two or more independent basic points; Level 2 requires the points to be linked to the vacuum cleaner; Level 3 requires both control of the hardware and efficiency of the code, and a few concise, linked sentences can reach Level 3, so extra length is not required.

Accept registers, memory addresses, input/output ports, machine code and mnemonics as ways of describing access to the hardware, and accept 'a low-level language is faster' as a basic point on its own. Do not award 'binary is a low-level language' (machine code is written in binary, but binary is not a language), or characteristics of high-level languages such as being easy to read or portable, as characteristics of a low-level language.