Software — Edexcel GCSE Computer Science
Verified courseTeaching note checked against the official specification.
Software explained
Software covers 3 specification points, including Understand the purpose and functionality of an… and Understand the purpose and functionality of….
Read the full explanation
Open a point below for its explanation and revision guidance.
3.2.1 understand the purpose and functionality of an operating system (file management, process management, peripheral management, user management)
An operating system is system software that manages the computer's hardware and provides services so application programs and users can work with the machine. Its purpose is to control resources, provide a user interface and allow software to run without directly managing hardware. File management organises how files and folders are stored, named, located, moved, copied and deleted, and controls access rights. Process management decides which programs or processes get processor time, schedules them, shares memory between them and closes them when finished. Peripheral management uses device drivers to send data to and receive data from input, output and storage devices such as keyboards, printers and disks. User management creates and controls user accounts, sets passwords and permissions, and keeps different users' settings and files separate.
3.2.2 understand the purpose and functionality of utility software (file repair, backup, data compression, disk defragmentation, anti-malware)
Utility software keeps a computer system healthy and usable. File repair scans a damaged file's structure and rebuilds what it can, so a corrupted document may open again. Backup copies files or whole drives to another location, either fully or incrementally, so data can be restored after loss. Data compression reduces file size by removing redundancy, saving storage and speeding up transfer; it can be lossless or lossy. Disk defragmentation rearranges fragmented files on a magnetic hard disk so blocks are contiguous, improving read speed. Anti-malware detects, quarantines and removes viruses and other malicious programs, and updates its definitions to recognise new threats. Each tool has a distinct purpose, and choosing the right one depends on the problem: a slow hard disk suggests defragmentation, whereas a suspected virus suggests anti-malware.
3.2.3 understand the importance of developing robust software and methods of identifying vulnerabilities (audit trails, code reviews)
Robust software continues to work correctly under unexpected input, heavy load or partial failure, and resists attack. It matters because failures can lose data, expose personal information, break safety-critical systems and damage trust. Two methods help identify vulnerabilities before they cause harm. Audit trails record who did what and when, so unusual access or changes can be traced and investigated. Code reviews involve other developers reading code line by line to find errors, insecure patterns and logic flaws that testing may miss. Together they support early detection, accountability and improvement. For example, a review might spot a missing input check, while an audit trail could reveal an unauthorised login attempt.
Your focus
- State the purpose of an operating system in managing hardware and providing services.
- Describe the functionality of file, process, peripheral and user management.
- Classify a described operating system activity under the correct management function.
Show all 9 objectives
- Describe the purpose of file repair, backup, data compression, disk defragmentation and anti-malware.
- Explain how each utility works, including the difference between lossless and lossy compression and between full and incremental backup.
- Select an appropriate utility for a described problem and justify the choice.
- Explain why robust software is important, including consequences of failure.
- Describe how audit trails and code reviews help identify vulnerabilities.
- Apply the methods to a scenario by suggesting an appropriate technique and justifying it.
Software exam tips
Marking Points
- States that an operating system is system software that manages hardware and provides services to applications and users.
- Describes file management as organising, locating, moving, copying and deleting files and folders and controlling access to them.
- Describes process management as scheduling processor time, sharing memory and starting or stopping running programs.
- Describes peripheral management as using device drivers to communicate with input, output and storage devices.
- Describes user management as creating accounts, setting passwords and permissions, and keeping users' data separate.
- Matches a described activity to the correct management function, for example a print job to peripheral management.
- File repair: identifies and rebuilds corrupted file structures so the file can be opened again.
- Backup: creates a copy of files or a drive, full or incremental, so data can be restored after loss or damage.
- Data compression: reduces file size by removing redundancy, saving storage space and reducing transfer time; may be lossless or lossy.
- Disk defragmentation: rearranges fragmented files on a magnetic hard disk into contiguous blocks to improve read speed.
- Anti-malware: detects, quarantines and removes malicious software, and updates definitions to recognise new threats.
- Selecting the appropriate utility for a given problem, such as defragmentation for a slow hard disk or anti-malware for a suspected infection.
- Robust software continues to function correctly under unexpected input, high load or partial failure, and resists attack.
- Importance: prevents data loss, protects personal data, maintains safety and reliability, and preserves user trust.
- Audit trails record activity such as logins and file changes, providing accountability and evidence for investigating incidents.
- Code reviews involve developers examining each other's code to find errors, insecure patterns and logic flaws before release.
- Both methods help identify vulnerabilities early, when fixes are cheaper and less damaging than after deployment.
Examiner Tips
- 💡Learn the four named functions as a checklist and ask which one the scenario describes.
- 💡For each option, name the resource being managed, such as processor time, files, devices or accounts, to decide quickly.
- 💡Reject options that describe application features or hardware repair rather than operating system management.
- 💡Match each utility to a specific problem in the question, for example a slow hard disk to defragmentation and a suspected infection to anti-malware.
- 💡Use the term 'redundancy' when explaining compression, and state whether the method is lossless or lossy if the question asks.
- 💡For backup, mention what is copied and where it is stored, and note that a backup must be separate from the original to be useful.
- 💡Link each method to a specific benefit, for example audit trails to accountability and code reviews to early detection of flaws.
- 💡Use a concrete example such as a review finding a missing input validation check or an audit trail showing an unauthorised login.
- 💡When explaining importance, refer to consequences such as data loss, financial cost, legal penalties and reputational damage.
Common Mistakes
- Treating the operating system as an application such as a word processor; correction: it is system software that manages hardware and provides services for applications.
- Confusing process management with file management; correction: process management schedules processor time and memory for running programs, while file management handles stored files and folders.
- Saying peripheral management means physically repairing devices; correction: it means using device drivers to control data transfer to and from devices.
- Ignoring user management; correction: it covers accounts, passwords, permissions and keeping different users' files and settings separate.
- Confusing backup with compression: backup copies data for restoration, whereas compression reduces file size; a compressed file is not a backup unless it is stored separately.
- Thinking defragmentation applies to solid-state drives: it is intended for magnetic hard disks, and running it on an SSD causes unnecessary wear without speed benefit.
- Believing anti-malware only removes viruses: it also detects and quarantines other malware such as worms, trojans and spyware, and needs updated definitions.
- Assuming file repair can recover any file: it rebuilds damaged structures but cannot restore data that has been overwritten or physically destroyed.
- Thinking robust software means it never fails: it means it handles failure gracefully and continues to operate safely or recovers.
- Confusing audit trails with backups: audit trails record activity for accountability, whereas backups copy data for restoration.
- Believing code reviews are only for finding syntax errors: they also uncover security weaknesses, poor design and logic flaws.
- Assuming testing alone guarantees security: testing checks known cases, while reviews and audit trails can reveal unknown or insider threats.