Edexcel GCSE Computer Science (1CP2) Exam Questions

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

• Devices (can) understand/interpret the data they receive (1) because they follow the same set of rules for communication (1)
• Data is sent in an agreed format/structure (1) so the receiving device can interpret/understand it correctly (1)
• Devices (can) connect/communicate successfully (1) because they agree how the data is transmitted, such as the type of signal used (1)
• Errors (can) be detected/handled (1) because both devices follow the same rules for checking the data (1)

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

Do not accept 'so devices can talk/communicate with each other' or 'so they can understand each other' without saying they follow the same rules/agreed format.

Do not accept an answer that only states protocols are a set of rules, without saying what this allows (e.g. the data can be understood/interpreted).

Do not accept a faster connection/speed as a reason why protocols are needed.

Do not accept naming a protocol (e.g. TCP/IP, HTTP, Wi-Fi) without an explanation of why it is needed.

Do not accept a description of what a protocol does (e.g. 'TCP splits data into packets') without saying why this is needed.

Award one mark for each correct nibble in the correct order:

• 0100 (1)
• 0000 (1)

0 marks if the response is not 8-bit binary.

Indicative content

How files and folders are organised

• The operating system creates a folder structure, so the business can keep each client's or event's photographs together.
• The operating system allocates each image file to a folder and records its file path, so the image can be located again.
• The operating system can move, copy and delete files and folders, so staff can remove unwanted images and keep the disk tidy.
• The operating system records file attributes such as size, type and date, so staff can sort and identify images.
• A folder structure that is not used consistently can make images slow to find, because files may be saved in the wrong client folder.

How files are named and saved

• The operating system lets an employee choose a file name and extension, so an image can be identified and opened by the correct application.
• The operating system saves a file to the folder the employee chooses, so a new image is stored with the correct client.
• The operating system checks whether a file with the same name already exists and warns the employee before it is overwritten, so original photographs are not lost.
• The operating system stores the file path with the file, so the business can retrieve the image later.
• If employees choose inconsistent file names, images can be difficult to identify when the business needs them.

How access to files is controlled for the employees

• The operating system stores user accounts and passwords, so each employee must log in before opening client images.
• The operating system sets access rights, so some employees can view images but not edit or delete them, which protects original photographs.
• An administrator account can change access rights, so the business can decide who may delete or edit client files.
• If employees share passwords, access rights are not effective, so images could be changed or deleted by the wrong person.
• If access rights are too restrictive, employees may be unable to do their work, so the business must set them carefully.

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)

Additional guidance

• Accept file extensions, file paths, file attributes, directory/folder structure, read-only access, read/write access, administrator and user accounts. Do not accept 'the OS controls/organises files' without a named task, or memory management, process management or peripheral management as file management.
• Level 3 responses must cover all three bullets, with at least one benefit or drawback applied to the business and a judgement. A list of features with no application is limited to Level 1; Level 2 requires at least two bullets covered with some linkage to the business.

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.