Topic 1 - Types of software
1.1 Programs vs applications
A program is a set of instructions that performs a specific, individual task. It may have no user interface (e.g. a background OS process) and is written in a language like Python or Java.
An application is made up of one or more programs, designed to be user-friendly and help users complete tasks. Examples: Microsoft Word, Chrome, Instagram.
Written in a programming language (e.g. Python, Java).
Designed to perform a specific task.
Can be run by the computer or operating system; it does not need an application to run.
Modular: can be built from sub-programs and reused in other applications.
Can be command line based or GUI based.
Every application is made up of programs, but not every program is part of an application.
Has a user interface (menus, buttons, etc.).
May be designed for a specific OS (e.g. iOS app).
May involve multiple programs working together.
Devices: desktops/laptops, consoles, smart TVs, smart speakers, smartphones, AR/VR devices, and embedded systems (washing machines, cars).
1.2 Operating systems
Advantages: centralised management, so administrators control access and resources from one place; efficient sharing of storage and printers for collaborative working; scalable, as new devices can be added easily.
Disadvantages: hardware and software must be compatible with it; complex to set up, needing technical knowledge; licensing costs for large deployments; ongoing maintenance and support costs; performance can degrade under high load.
Advantages: free or low cost; can be customised to the client's needs; large community support. Disadvantages: less formal support; fewer compatible commercial applications; needs technical skill to set up and maintain.
Advantages: official support and regular security updates; wide application compatibility; easy for general users. Disadvantages: licence cost; cannot be modified; the client depends on the vendor.
Justify OS choice based on the client scenario, e.g. building an iOS app = must use proprietary; museum terminal = open OS (customisable and low cost).
1.3.1 Application types (8 types)
1.3.2 Software categories (5)
Advantages: free; can be modified to fit the client; community fixes. Disadvantages: support relies on the community; quality and documentation vary.
Advantages: official support and updates; tested and reliable. Disadvantages: licence cost; cannot be modified; locked to the vendor.
Advantages: try before buying. Disadvantages: features or time limited; reminders to pay.
Advantages: no cost. Disadvantages: cannot be modified; support and updates may stop; may carry adverts or bundled software.
Advantages: efficient and reliable for one task; runs on low-power hardware. Disadvantages: hard or impossible to update; cannot be used for other tasks.
1.3.3 Software types (3)
Advantages: faster to develop than bespoke (the core is already written); lower up-front cost (only the custom part is developed); more reliable (the core is already used by other companies); tailored to the client's requirements; support network and regular security updates for the core.
Justify choice against the client scenario, e.g. dental surgery bookings = bespoke (unique needs); general office = off-the-shelf (cost-effective).
Custom off-the-shelf is not the same as off-the-shelf. In June 2026 many candidates compared bespoke with plain off-the-shelf and lost marks. Describe it as an off-the-shelf base with custom features added.
Topic 2 - Software development models
2.1 Software development models
The spec groups the seven models into three families: traditional (Waterfall), prototyping (Rapid Throwaway, Incremental, Evolutionary) and iterative (RAD, Spiral, Agile). Using a model at all gives the team a clear structure, defined stages and deliverables, and makes progress easier to track; the drawback is that a poorly chosen model adds cost and slows the project. You also need to recognise and draw a simple diagram of each model.
Advantages: simple to understand and manage; clear milestones and documentation. Disadvantages: hard to go back once a phase is complete; the user sees nothing until the end; late changes are expensive.
Advantages: clarifies requirements early; users give feedback before the real build. Disadvantages: time spent on prototypes that are discarded; users may expect the finished product to arrive as fast.
Advantages: working parts delivered early; easier to test smaller parts. Disadvantages: needs good planning to split the system; parts may not integrate well later.
Advantages: users are involved throughout; no work is thrown away. Disadvantages: hard to know when it is finished; the structure can become messy after many changes.
Advantages: fast delivery; constant user feedback. Disadvantages: needs users to be available often; less suited to large or safety-critical systems; less documentation.
Advantages: risks identified early so mitigation is put in place; flexible, so changes can be made at different stages; stakeholder and user feedback is built into each cycle, improving usability; feedback loops give a high level of quality assurance; scales to large, complex projects.
Disadvantages: complex and resource intensive, so higher cost; needs a skilled, experienced team to carry out risk analysis; time consuming because of the multiple iterations; money is wasted if risks are identified wrongly; needs continuous user engagement at each review; not suited to small projects.
Advantages: adapts quickly to change; usable features delivered each sprint. Disadvantages: hard to predict final cost and timescale; needs close, ongoing client involvement; less documentation.
Throwaway vs evolutionary: both use prototypes, but throwaway discards them after gathering feedback; evolutionary refines the prototype until it becomes the final product.
2.2 Phases of software development
Seven phases that interact and iterate (e.g. testing may reveal design issues, requiring you to return to the design phase).
Phased: rolled out in stages.
Parallel: old and new systems run simultaneously until the new one is trusted.
Big bang (crash): old system replaced all at once.
Topic 3 - Planning development projects
3.1 Importance of planning
Identifies required resources (time, money, people, tools).
Better organisation, as team members know their roles.
Improves time management via deadlines and milestones.
Plans may become outdated if requirements unexpectedly change mid-project.
Unclear goals leading to confusion and delays.
Risk of delivering an unusable or incomplete product.
Planning considerations (things that must be evaluated in the planning phase):
The spec lists six: budget (how much money is available), constraints (limits such as hardware, software or integration with existing systems), legislation, resources (people, hardware, software, equipment), success criteria (measurable targets used to judge whether the project worked) and time (deadlines and timescales). Each affects development: too small a budget or too little time limits features, missing resources cause delays, and unclear success criteria make it impossible to show the project succeeded.
Three types of legislation to be aware of (the spec excludes the details of specific acts for F160; F161 Topic 6 covers the acts by name):
- Copyright: protecting original work from unauthorised use.
- Data protection: how personal data must be collected, handled and stored.
- Electronic communication: rules around sending digital messages, cookies and electronic marketing.
3.2 Project planning tools (6)
Components: arrows for tasks, nodes (circles) for events, task durations. Advantages: shows dependencies and the critical path clearly. Disadvantages: hard to read on large projects; does not show dates.
Components: tasks, durations, dependencies, earliest and latest start times, float, the critical path. Advantages: shows which tasks must not slip and where there is float. Disadvantages: relies on accurate time estimates; complex for large projects.
Disadvantages: becomes large and hard to follow for complex systems; time consuming to draw and update.
Why it is effective for planning: clarifies the logic of a process; helps identify problems and bottlenecks; shows how parts of the application connect, so you can see where to modularise; shows inputs and the paths they lead to; a visual communication tool between teams and the client; an industry standard, so all developers understand it.
Components: task list, horizontal time axis, bars for task duration, milestones, dependencies. Advantages: easy to read; shows progress against the plan; good for communicating with the client. Disadvantages: does not show the critical path clearly; must be updated whenever the plan changes; cluttered on large projects.
Disadvantages: can be overwhelming in detail on a large development; focuses on time, not resources, so bottlenecks appear when resources are unavailable; needs expert skills to create and understand; complicated to create, so mistakes or missing tasks are likely; times are only estimates and can be inaccurate; time consuming to create.
Opportunities & Threats = external (outside control).
Guides decision-making by highlighting advantages, weaknesses to address and potential risks.
Components: a 2x2 grid of the four headings. Advantages: quick and simple; considers internal and external factors. Disadvantages: subjective; does not prioritise the points or give timings.
Topic 4 - Application design scoping
4.1 Gathering client requirements (9 methods)
4.2 Client requirement specifications
A client requirement specification formally documents exactly what the system must do and how it must operate. Know all elements:
4.3 Decomposition methods (4)
Decomposition breaks complex problems into smaller, manageable parts, making development easier to plan, understand and implement. Reduces errors and improves efficiency.
Purpose: simplifies a complex application so the processes are easier to understand; makes problems easier to locate and solve; lets modules be reused in other applications; lets separate teams build parts at the same time, supporting incremental or phased development. Disadvantages: needs the whole system understood at the start; modules may not fit together if the design is wrong.
Top-down = start broad, go specific. Bottom-up = start specific, build up. Abstraction = filter out irrelevant detail. Parsing = break requirements into actionable tasks.
Topic 5 - Human-Computer Interface (HCI)
5.1.1 Types of human-computer interaction
The spec groups GUI and command line together as visual interaction, alongside audio, movement/gesture and touch.
GUI vs CLI: GUI is accessible, visual, and suited to general users. CLI is powerful, efficient for experts, but has a steep learning curve and no visual interface.
5.1.2 Types of device
Know the characteristics of each device type that uses application software and how those characteristics influence which HCI types are appropriate.
5.2 Visual design considerations
5.3 HCI design documents and diagrams (4)
Level 0: context diagram, high-level overview.
Level 1: more detailed breakdown of individual processes.
Components: external entity (a source or destination of data outside the system, e.g. Customer), process (something that changes the data), data store (where data is held, e.g. Orders file), data flow (a labelled arrow). Level 0 shows the whole system as one process with its external entities.
Symbols: terminator (rounded rectangle, start/stop); process (rectangle); sub-process or subroutine (rectangle with double sides); decision (diamond, yes/no); input/output (parallelogram); arrows show the flow.
Components: title; text; annotations; colour scheme; images, graphics, logos and icons; positioning and layout (positions and sizes); typography.
Conventions: alignment and spacing; clear labels and legends; minimal design elements, so the focus is on content.
Wireframe = structure only, no styling. Visualisation diagram = shows what it will look like. DFD = data flow, not logic or decisions. Flowchart = step-by-step sequence and decision paths.
When asked to analyse a given visualisation diagram, go through the components and conventions above and comment on the diagram in front of you: is each one included, and is it clear to the person using it? A learnt, generic answer about visualisation diagrams scored nothing in June 2026. Improvements must add something, not just restate a weakness.
Topic 6 - Job roles & communication skills
6.1 Job roles in application development (7)
UXD = how users experience it (personas, site maps, wireframes, usability testing). UID = how it looks (visual design). Application designer = architecture and functionality. Systems analyst = requirements gathering. Systems designer = technical architecture.
The mark scheme does not accept "makes it easy to use", "user friendly" or "a good experience" for the UXD, and does not accept interface or appearance answers for the application designer. Name a specific responsibility and say how it helps the development.
6.2 Communication skills (5)
Closed questions: yes/no, confirm specific facts.
Probing questions: explore detail further.
Clarifying questions: check understanding is correct.
Characteristics of questioning and how each helps research: adaptable (questions can be altered to fit the audience or expanded to explore a topic in depth); open (detailed, qualitative answers giving greater insight into opinions); closed (specific answers that are easy to analyse and present as graphs); purposeful (each question is asked for a reason, so the data gathered is relevant).
Topic 1 - Application software considerations
1.1 Application platforms
The spec defines three application platforms. Know the uses, advantages and disadvantages of each.
AR overlays digital content on the real world, usually through a phone or tablet camera. VR replaces the real world with a virtual one through a headset. MR mixes the two, so virtual objects interact with the real environment.
AR advantages: runs on mobile devices most people already own, unlike VR, which needs specialised equipment; contextual, as details appear on the real object or location; enhances learning with explanations and animations; improves accessibility (audio cues, translations, visual enhancements); the user does not need to look away from the real world.
VR advantages: fully immersive, hands-on learning and training without real-world risk.
Disadvantages: VR and MR need expensive headsets; VR can cause motion sickness and discomfort; development is complex; AR needs a good camera and processing power and drains the battery.
Advantages: accessible on any browser, no installation, easy to update. Disadvantages: requires internet, may be slower than native apps, security risks (spoofing).
Do not answer an AR question with VR points. "Expensive hardware" is a VR disadvantage; for an AR app on a phone it is wrong. "It is immersive" on its own earned no mark in June 2026: link the advantage to the app in the question.
Note: the spec's platform categories are AR/VR/MR, Websites, and Computer games. "Mobile app" or "desktop app" are NOT platform categories. Those are devices (1.2), not platforms.
1.2 Devices
Know the characteristics, advantages and disadvantages of each device that application platforms run on.
1.3 Storage locations
On-site storage: physical storage at the organisation's own location.
Cloud storage: data stored on remote servers accessed via the internet. Two things to know: locations and types.
Cloud storage locations:
Cloud storage types:
Factors when selecting a storage location or cloud storage type: cost, capacity and scalability, speed of access, security and sensitivity of the data, legal requirements on where data is held, internet dependence, and backup and recovery needs.
For hybrid cloud questions, say why the mix of private and public helps (security split, scalability, cost, continuity). General cloud benefits such as remote access, file sharing or automatic backup apply to any cloud and were held at Level 2 in June 2026.
The spec distinguishes cloud storage locations (private/public/hybrid/community) from cloud storage types (file/object/block/elastic/database). Know both sets separately.
Topic 2 - Data and flow in application software
2.1 Data formats and data types
Data formats: how data is structured and encoded for storage or transmission:
For the exam: standard ASCII is 7-bit (128 characters), but OCR's June 2026 mark scheme describes ASCII as a character encoding standard using 8 bits per character, giving 256 symbols (this is extended ASCII). Use OCR's 8-bit wording if a question gives it.
To describe a data format, say how it structures the data (e.g. JSON uses key-value pairs and arrays; CSV separates fields with commas, one record per line). "Lightweight and scalable" on its own only earned the identification mark in June 2026.
Data types: the kind of value a variable stores in a program:
2.2 Data flow
Data vs information: data is raw, unprocessed facts (e.g. "42", "Liverpool"). Information is data that has been processed and given context and meaning (e.g. "42 students are enrolled at Liverpool campus"). Data is converted to information by processing it: sorting, calculating, combining with other data.
Types of input data that flow into an application:
Black box concept: a model where the system's internal processing is hidden. Only inputs and outputs are visible to the user. Data flows in, is processed internally, then flows out as information, or flows to storage. Used to diagrammatically represent data flow without showing the internal logic.
Name the actual data from the scenario. For an app that identifies a photographed road sign, the flow in is the captured image of the road sign and the flow out is the name and details of the sign. "Data", "information" or "output" alone scored nothing in June 2026.
The three flows: flow in (input data enters the system), flow to storage (data saved to on-site or cloud), flow out (information produced as output: number, text, audio, image, movement).
2.3 Data states
Topic 3 - APIs and protocols
3.1 Application Programming Interfaces (APIs)
An API sets the rules enabling one application to communicate with another, defining how requests and responses are structured. Role: enables communication between a server and application; transfers data between systems; increases security by controlling access.
API types (the spec lists five: composite, internal, private, public, partner):
API architectures:
REST = flexible, lightweight, widely used. SOAP = strict, XML-based, enterprise-grade security. RPC = calling a remote function directly.
3.2 Protocols and the TCP/IP stack
A protocol is a set of rules governing how data is transmitted and received. The spec lists nine protocols to know:
TCP/IP stack - 4 layers (top to bottom):
The spec says "does not include OSI model": only the 4-layer TCP/IP stack is needed, not the 7-layer OSI model.
Topic 4 - Application software security
4.1 Security threats and mitigations
Threats to application security (spec says no need for detailed workings; know the risk each poses):
Physical security mitigations:
Match the mitigation to the device. For a smartphone or portable smart device: biometrics (face or fingerprint) suit it; a camera supports biometrics; cable locks do not suit a device carried around; a safe or locks stop the app being used at all; swipe cards are not used with smartphones; CCTV, alarms and guards deter but do not stop someone using the app. A privacy screen stops others seeing the screen but does not prevent access.
Digital security mitigations:
The spec says "does not include details of specific threats or the specific workings of mitigations": focus on the risk each threat poses and how each mitigation protects against it.
Topic 5 - Operational considerations
5.1 Testing
Purpose of testing: to find and fix errors and check the application meets the client requirements before release. Testing during development catches problems early, when they are cheaper to fix. Impact of not testing: bugs and crashes, security vulnerabilities, compatibility problems on some devices, poor user experience, loss of trust and money. Advantages of testing: higher quality and reliability. Disadvantages: takes time and money, and cannot prove there are no errors. Remedial action and retesting fix the faults found and confirm the fix works without breaking anything else.
Test plan structure: know all fields:
Types of test data:
Test data (normal, extreme, erroneous) is the input values used in a test. Testing types (automated, fuzz, load/stress, migration, alpha, beta) are ways of testing. Do not mix them: in June 2026 "migration testing" given as a type of test data, and "high usage testing to find performance limits" given as the role of extreme data, both scored 0. The role of extreme data is to test the boundaries of acceptable data, i.e. the validation at the edge between valid and invalid.
Types of testing:
5.2 Types of application software installation
Use the spec names exactly: "Unattended install", not "silent install". In June 2026 "silent install" justified by pushing the app to every device on a network got no marks; that describes a network or remote install. Your justification must match the install type you name.
The spec says "does not include completing software installations": you need to know the process, advantages/disadvantages and when to use each type, not how to physically do it.
5.3 Policies
Know the purpose and content of each policy that must be considered when developing and deploying application platforms.
Topic 6 - Legal considerations
6.1 Legislation and the ICO
For F161 you must know specific Acts by name, their main purpose, what compliance requires, the impact of non-compliance, and how they relate to each other. The spec says "does not include knowing the detailed content": know the purpose and obligations, not every clause.
Non-compliance: fines up to £17.5m or 4% of global turnover, reputational damage, enforcement notices.
Enforced by the ICO. The latest version is the DPA 2018 and UK GDPR as amended by the Data (Use and Access) Act 2025.
Non-compliance: criminal prosecution, imprisonment, fines.
Relationship to DPA/UK GDPR: PECR works alongside UK GDPR. UK GDPR sets the standard for how consent must be obtained; PECR specifies when consent is required for electronic communications.
Non-compliance: ICO fines up to £17.5m or 4% of global turnover, whichever is higher (raised from £500,000 by the Data (Use and Access) Act 2025).
Non-compliance: ICO enforcement, mandatory disclosure orders, reputational damage.
Key relationship to know: PECR requires consent for electronic marketing; UK GDPR defines what valid consent looks like. They work together. Both are enforced by the ICO.