English:Computer hardware, software and system components - Computing Year 7
Introduction

Follow a fictional image-editing task through input,processing,working memory,software,saved storage and output. Distinguish RAM from storage,trace a completed save and compare systems against explicit requirements. Year 7 allocation is editorial within England’s KS3 pathway.
Identify components through the task they support
A computer system is a collection of cooperating components. Hardware is physical equipment, such as a processor, keyboard, display, memory chip or storage device. Software is a set of programs and instructions directing what equipment does. A photograph stored as a file is data interpreted by an application; calling every digital file software hides an important distinction between a program and its input.
For our original task, imagine editing a fictional school-club poster using a locally stored photograph. The user supplies commands through a keyboard, mouse or touch interface. An image-editing application processes the chosen operation; the display shows the result. Working data and saved files have different roles. No real learner photograph or account is needed to reason about this system.

Input and output depend on the chosen system boundary. A keyboard provides input to the computer; a monitor provides visual output. A touchscreen can do both through distinct sensing and display functions. Storage can be read from and written to; a network interface sends and receives data. Avoid forcing every physical device into exactly one role just because a simple introductory diagram has separate boxes.
| Example | Classification | Role for the original task |
|---|---|---|
| Keyboard | Input hardware | Supplies key events |
| Touchscreen | Input and output hardware | Senses touch and displays images |
| CPU | Processing hardware | Executes machine instructions |
| Main RAM | Working memory hardware | Holds active instructions and data in this model |
| SSD | Non-volatile storage hardware | Retains saved data without continuous power |
| Operating system | System software | Coordinates processes,files,memory and devices |
| Image editor | Application software | Provides the chosen editing functions |
| Photo file | Data | Represents the image being edited |
The central processing unit, CPU, is not the entire computer. It executes machine instructions using processing circuitry, control logic and small fast storage such as registers and caches. Main memory supplies instructions and data needed for work. A simplified fetch,decode,execute account means obtaining an instruction,interpreting it and carrying out the required operation. Modern processors add substantial complexity; a conceptual cycle does not imply one whole program runs in one clock tick.
Main RAM in this course means the ordinary volatile working memory used while applications run. An SSD or hard drive is longer-term non-volatile storage. Both store digital information, but they serve different purposes and have different access characteristics. Increasing free disk space is not the same as increasing available working memory. Saving an edited file is a storage operation, not a promise that every value in RAM becomes a permanent file automatically.
The official Code.org How Computers Work series, on its current CodeAI channel, connects CPU,memory,input and output. Identify the role of each component in the original poster-editing task. The written roles and worked workflow remain usable without the external video or sound. Original: CodeAI, How Computers Work: CPU, Memory, Input & Output. The written explanations and native tasks work without sound or the external player.
Connections matter as well as component names. A main board and its interconnections allow components to exchange data and control signals; ports and interfaces connect suitable peripherals. A tablet may integrate many functions into a compact system rather than present removable desktop cards. The same functional question remains: what provides input,executes instructions,holds current work,retains saved data and presents output for this task?
Trace software,working state and completed saves
Applications use system software to work with hardware. The operating system manages running processes,available memory,files and access to devices. An image editor offers crop,caption and export functions for a user. Device drivers provide software support for particular hardware interfaces. These roles cooperate: the application requests services,system software coordinates them,and hardware executes instructions and handles data transfers.
Do not mistake a visible window for the whole operating system or the CPU for a program. A drawing application can be stored on a drive while not running; when launched,relevant instructions and data are made available for execution. Different applications can run under one operating system,and the same kind of task can have different software implementations. A useful system diagram names roles and data movement instead of treating product logos as explanations.

A user opens a saved image. The application asks the system to read the file,and the computer brings relevant data into working state. A crop command changes an in-memory representation; the display can update before a new saved file is written. Choosing Save requests storage of the changed version. For our model below,only a save explicitly stated as completed successfully changes the retained file.
| Event | Meaning in the stipulated model | Working version | Saved version |
|---|---|---|---|
| Open saved image | Read version A from storage into working state | A | A |
| Change a caption | Application updates working state | B | A |
| Save completes successfully | Write the new state to the saved file | B | B |
| Change another detail | Working state changes again | C | B |
| Model loses volatile state | Unsaved working state is not retained | Unavailable | B |
After changing B to C without another completed save,the saved version remains B. If the model then loses volatile working state,C is unavailable and reopening the retained file gives B. This is a deliberately simplified no-autosave,no-recovery model for reasoning,not a claim that every real application behaves identically. Autosave,temporary recovery files,cloud synchronisation and completed backups can add other retained versions; they must be stated and checked rather than assumed.
Do not demonstrate the distinction by cutting power,forcing a crash or sacrificing real work. Use the paper version ledger or a disposable fictional file under normal school procedures. Ordinary sleep may keep memory powered,and hibernation can preserve state to storage; closing a lid is not a universal experiment that proves all RAM contents are lost. Non-volatile storage is also not indestructible:failure,deletion or an interrupted write can still affect data.
Hardware and software together: the official Code.org series on its current CodeAI channel. Identify an application,system software and hardware in the explanation,then map them to the independently written poster task. The original roles table and version ledger are the offline alternative.
When diagnosing a fictional failure,use evidence to localise a role. If the file opens and a crop preview changes but saving reports a permission error,the observation does not prove a broken processor. If a touchscreen displays the page but does not sense touch,the output path may work while the input path fails. State the observed behaviour and one discriminating next check; several faults can produce superficially similar symptoms.
Networking adds another system boundary. Uploading a saved poster uses local software and a network interface,then remote computers and storage. A local saved file is not automatically a cloud backup,and a visible upload indicator does not prove a complete independently recoverable copy. For this course,keep the main task local; use the network example only to trace where another system would enter the diagram.
Evaluate capacity,performance claims and evidence
Evaluate a system against a stated task rather than one impressive number. A processor's role is instruction execution; RAM capacity limits aspects of working data; storage capacity limits retained files. Storage transfer rates,processor design,graphics acceleration,software and the workload can all affect responsiveness. A higher clock frequency alone does not prove one complete computer is faster at every task,and adding RAM does not automatically increase a processor's clock rate.
Our original image model uses an uncompressed RGB image four thousand pixels wide and three thousand high,with eight bits for each of red,green and blue. There are twelve million pixels,twenty-four bits per pixel and three bytes per pixel. Ignoring metadata,compression,alpha channels and program overhead,the raw pixel buffer is thirty-six million bytes. These are stated model assumptions,not a measurement of an actual JPEG file.
Use decimal megabytes explicitly: one MB is one million bytes,so this buffer is 36 MB. In binary units one MiB is 1,048,576 bytes,giving approximately 34.33 MiB. The different numerical displays do not imply the pixel data has changed. A stored compressed photo may have a very different file size,and an editor may need extra buffers,history and other working data beyond one raw image.
If both dimensions are halved to two thousand by fifteen hundred,the pixel count becomes three million and the raw RGB buffer nine million bytes. The area and raw size become one quarter,not one half. Under a separate stipulated three-full-buffer model,the original image uses 108 MB of pixel buffers before any other overhead. Neither calculation is a promise about a particular application's actual memory use.

Consider three fictional systems with the available capacities shown below. A stipulated task requires six GB of available working memory and eighty GB of free storage. Treat all capacities in this table as the already available values in a common declared unit; no hidden operating-system reserve needs subtracting again. This is a two-constraint reasoning task,not a hardware purchase recommendation or a benchmark.
| System | Available working memory | Free storage | Meets the two stipulated capacities? |
|---|---|---|---|
| A | 4 GB | 128 GB | No: working-memory requirement not met |
| B | 8 GB | 64 GB | No: storage requirement not met |
| C | 8 GB | 128 GB | Yes: both stated capacity requirements met |
System A has enough free storage but only four GB available working memory,so it fails the six-GB condition. System B has enough working memory but only sixty-four GB free storage,so it fails the eighty-GB condition. System C meets both. That does not prove C meets an unstated processor,graphics,accessibility,battery or software-compatibility requirement. A correct comparison names its criteria and its limits.
A separate idealised transfer example moves a forty-MB file at a constant twenty MB per second. Dividing size by rate gives two seconds before any additional overhead. If the rate is quoted in megabits instead of megabytes,units must be converted first because eight bits make one byte. Latency,protocol overhead,caching and varying rates can make actual elapsed time differ. Do not report an ideal model as a measured device result.
For a practical observation,use an ordinary approved application and a fictional disposable file. Identify an input action,a visible output,the application and an operating-system service. If your environment permits a normal task view,you may observe changing resource use without changing settings or closing someone else's work. Otherwise complete a labelled paper system diagram. Record what you actually observed and distinguish it from the hypothetical capacity and image-size calculations.
Finish with a trace from input through application,operating-system service,processing and working memory to displayed and saved output. Explain where the original file was retained,what changed in working state,and what a completed save adds. Add one evidence-based fault hypothesis and one testable improvement. A useful system explanation connects components to a task;it is more informative than memorising that a CPU is a brain or that more of every component must always be better.
Interactive Tasks
Quiz: Test Your Knowledge
Which statement best describes the CPU here? (A processing component that executes instructions within a larger system) (!The whole computer including every input and storage device) (!The image-editing application rather than hardware) (!A guarantee that every instruction takes exactly one full program cycle)
Which device has both input and output functions in this task? (A touchscreen sensing touch and displaying an image) (!A keyboard used only for typed key events) (!A printed sheet after it leaves the printer) (!A saved photo file treated as a physical device)
What is the role of ordinary main RAM in this course? (Volatile working memory holding active instructions and data) (!An automatically completed backup of every open document) (!A permanently retained file archive identical to an SSD) (!Only an operating-system logo on the screen)
How is the image editor classified? (Application software supporting the chosen user task) (!A physical processing chip) (!The same thing as its photograph data file) (!A memory socket that must be installed to draw)
What remains saved after the original ledger loses unsaved version C? (Version B because the completed save retained B before the later edit) (!Version C because every display update automatically completes a save) (!Version A because a successful save never changes storage) (!No answer can follow even under the explicitly stated no-autosave model)
What does the RAM-slot photograph actually show? (Memory sockets,without proving an installed capacity or complete system performance) (!A fully identified SSD containing the poster backup) (!Proof that every modern tablet uses removable desktop RAM) (!A safe instruction to open and modify a real device)
How large is the original raw RGB pixel buffer under the stated assumptions? (Thirty-six million bytes,or thirty-six decimal MB) (!Twelve million bytes because each pixel is always one byte) (!Thirty-six MiB exactly because MB and MiB are identical) (!The measured JPEG file size on every camera)
What happens to raw size when both original image dimensions are halved? (It becomes one quarter,or nine million bytes here) (!It becomes one half because only width affects pixel count) (!It remains unchanged because resolution cannot affect a buffer) (!It proves that all editor working-memory use is exactly quartered)
Which fictional system meets both stated capacity requirements? (C,with eight GB available memory and one hundred and twenty-eight GB free storage) (!A,because storage alone compensates for insufficient memory) (!B,because more memory makes its free storage unlimited) (!Every system because a processor can replace any missing capacity)
What does the ideal forty-MB transfer calculation establish? (Two seconds at the stated constant twenty MB per second before overhead) (!An actual measured speed for every local and remote transfer) (!Two seconds even when the rate unit changes to megabits without conversion) (!Proof of a completed recoverable cloud backup)
Memory Game
| Hardware | Physical system equipment |
| Application | Software providing a user-facing task |
| Operating system | System software coordinating processes,memory,files and devices |
| RAM | Ordinary volatile working memory in this model |
| Storage | A retained location for saved files |
| Interface | A connection through which components or users exchange information |
Drag and Drop
| The touchscreen shows the poster but misses touches | Separate the working display output from the possibly failing touch input |
| A crop is visible but saving reports a permission error | Investigate the save path rather than declaring the CPU broken |
| The task needs six GB working memory and A has four | The stated working-memory capacity is insufficient |
| Both image dimensions are halved | The stipulated raw pixel count and buffer size become one quarter |
| An edit remains unsaved after completed save B | The simplified loss model can reopen B rather than unsaved C |
Crossword Puzzle
| HARDWARE | What names the physical equipment? |
| SOFTWARE | What names programs and instructions? |
| PROCESSOR | What executes machine instructions? |
| STORAGE | Where are retained saved files kept? |
| VOLATILE | What describes working memory requiring continued power to retain its state? |
| INTERFACE | What connects cooperating parts or a user to the system? |
LearningApps
Optional extra practice. Choose an appropriate activity with your teacher. If the external collection is unavailable, use the native activities and independent tasks in this course.
Cloze Text
Open Tasks
Easy
- Classify examples: Distinguish hardware,system software,application software and data using the role table.
- Draw the system: Label input,processing,working memory,storage and output for the fictional poster task.
- Use both roles: Explain how a touchscreen can be input and output without making those functions identical.
- Trace a save: State working and saved versions after each event in the original ledger.
Standard
- Explain cooperation: Connect an application request,an operating-system service and a hardware action.
- Calculate a buffer: Use dimensions,RGB channels and bits per channel to justify the original raw byte size.
- Compare constraints: Explain separately why A and B fail and C meets the two declared capacities.
- Diagnose evidence: Choose a fault hypothesis and discriminating next observation for one stated symptom.
Advanced
- Qualify a model: Explain how autosave,recovery,sleep or hibernation can change the simplified version-loss story.
- Distinguish units: Compare decimal MB,binary MiB and megabits without treating them as interchangeable labels.
- Critique performance: Explain why clock frequency or RAM capacity alone cannot certify every workload.
- Collect honest evidence: Observe an approved fictional-file workflow if available,otherwise label a paper model and identify its limitations.
Learning Check
- Components and boundaries: Connect classifications to the original task.
- Working and saved versions: Follow the original no-autosave ledger exactly.
- Raw image-size model: Calculate bytes from the declared representation.
- Changed dimensions and capacity: Check scaling and both independent requirements.
- Units and ideal transfer: State what the arithmetic can establish.
- Observation and improvement: Use evidence instead of a single impressive label.
Worked checks and assessment guidance
- A keyboard supplies input,a CPU executes instructions,RAM holds active working data,storage retains saved files and a display presents output. A touchscreen combines distinct input and output functions. The operating system is system software,the image editor application software and the photo file data. Storage and network interfaces can both read/receive and write/send,so not every real device fits one exclusive introductory box.
- Opening saved A gives working A. An edit changes working state to B while storage stays A. A completed successful save retains B. A further edit changes only working state to C; after stipulated loss of volatile state,the retained file is B. Real autosave,recovery or synchronisation can add other versions and must be stated. Do not test the model by cutting power or risking real work.
- Four thousand times three thousand gives twelve million pixels. Three RGB channels of eight bits give twenty-four bits,or three bytes,per pixel. The stipulated raw buffer is thirty-six million bytes,36 decimal MB or approximately34.33 MiB. This excludes compression,metadata,alpha and software overhead. It is not a measured JPEG size or a complete editor memory profile.
- Two thousand by fifteen hundred gives three million pixels and nine million raw bytes,one quarter of the original. Three full original buffers give108 decimal MB before other overhead. For the separate six-GB working-memory/eighty-GB free-storage task,A fails memory,B fails storage,and C meets both capacities. That does not certify unstated processor,graphics,software or accessibility requirements.
- Forty MB divided by twenty MB per second gives two seconds under a constant-rate,zero-extra-overhead model. Eight bits make one byte,so megabits and megabytes cannot be substituted without conversion. Real latency,caching,protocol overhead and varying rates can change elapsed time. A calculated time is not an observed benchmark or proof of a recoverable backup.
- Observe an approved application and disposable fictional file,or submit an honestly labelled paper diagram. Trace an input action,application behaviour,operating-system service,processing/working state and displayed/saved output. A visible crop with a save permission error points to a save-path question rather than proving processor failure. Retain assumptions,distinguish RAM from storage and propose one testable improvement without modifying real hardware or risking another person’s work.
Learning evidence
Submit a labelled original system diagram,component-role classification,complete version ledger,image-buffer calculations,two-constraint system comparison and one justified fault hypothesis. Clearly distinguish stipulated models from actual observations. If practical observation is possible,use only a disposable fictional file and ordinary approved controls; no disassembly,power-cut test,real learner data or purchase is required.
OER and Wikipedia
Original poster workflow,component-role table,version ledger,capacity cases,image model and assessments. DfE Computing programme of study, KS3 hardware/software components and communication; Year 7 allocation is editorial. The official Code.org/CodeAI video library identifies the original How Computers Work series. Kingston: difference between memory and storage supports the ordinary working-memory/retained-storage distinction; permanence and power-loss claims are qualified for actual save/recovery behaviour and device failure. Primary sources checked13November2026. No source marketing claim is a benchmark or buying recommendation. Images retain their actual Commons credits; numbered desktop layout and empty memory sockets are qualified by what is actually visible.
Personal computer, exploded.svg, Gustavb, CC BY 2.5. Unchanged original; caption and learning activities are original.
DDR 4 SO-DIMM RAM slot PNr°0837.jpg, D-Kuru, CC BY-SA 4.0. Unchanged original; caption and learning activities are original.
Scratch 3.0 editor.png, Screenshot is own work, Scratch is by MIT and other contributors, CC BY-SA 2.0. Unchanged original; caption and learning activities are original.
Linked learning areas
aiMOOC Projects
Schulfach+


aiMOOCs


aiMOOC Projekte


MOOCwiki · Deutsch
Nach dem Lernen ist vor dem Lernen
Entdecke direkt den nächsten Lernkurs. Weitere Inhalte erscheinen, wenn Du weiter nach unten scrollst.
Zur MOOCwiki-HauptseiteMediathek
Mediathek wird aus dem Wiki geladen ...
Keine passenden Inhalte gefunden. Bitte ändere Suche oder Filter.
NEWSLernweltNOAH fragen