Search CSNewbs

Learn about legislation and regulations related to application development, including the Data Protection Act, Computer Misuse Act and Freedom of Information Act. Resources based on Unit F161 (Developing Application Software) for the OCR Cambridge Advanced Nationals in Computing (H029 / H129) AAQ (Alternative Academic Qualification). Qualification: Cambridge Advanced Nationals in Computing (AAQ) Certificate: Computing: Application Development (H029 / H129) Unit: F161: Developing Application Software 6.1 - Legal Considerations Watch on YouTube : Computer Misuse Act Data Protection Act UK General Data Protection Regulation Freedom of Information Act Privacy and Electronic Communications Regulations Independent bodies UK Information Commissioner's Office You need to know the latest version and main purpose of each act /regulation , as well as actions taken to comply with the act and the impacts of not complying with it. You must also understand how Privacy and Electronic Communications Regulations (PECR ) relate to the Data Protection Act and UK General Data Protection Regulation (UK GDPR ), and the role of the Information Commissioner's Office (ICO ) in the UK. What You Need to Know Developers must ensure application software complies with relevant legislation and regulations to protect users, their data and computer systems, and to avoid legal and financial consequences. Computer Misuse Act (CMA) This act protects computer systems and data from unauthorised access and misuse and makes activities such as unauthorised access, certain forms of hacking and deliberately impairing computer systems criminal offences. Developers must only access systems and data they have permission to use, ensure any security testing is authorised, and must not develop or use software to deliberately gain unauthorised access or damage systems. If individuals do not comply with the CMA, they could face criminal prosecution, fines or imprisonment, while an organisation could also experience financial costs and reputational damage. Example: A developer must have permission before attempting to access restricted parts of a client's system, even if they claim they were only testing its security. Data Protection Act (DPA) The purpose of the DPA is to control how organisations collect, process, store and protect personal data, helping ensure people's information is handled fairly, lawfully and securely. Developers should ensure applications only collect necessary personal data, explain how it will be used, only use it for its intended purpose, keep it secure and remove it when it is no longer required. Non-compliance can result in complaints, data breaches, regulatory action, legal disputes, financial penalties, operational disruption and reputational damage. Example: A revision application should not collect a student's home address if that information is unnecessary for providing the service. UK General Data Protection Regulation (UK GDPR) This regulation provides rules and principles governing the lawful processing and protection of personal data and gives individuals rights over how organisations use their information. It operates alongside the DPA 2018 in the UK. Developers should ensure there is a lawful reason for processing personal data, collect only necessary information, clearly explain its use, keep it accurate and secure, avoid retaining it unnecessarily and allow users to exercise their data rights where applicable. If they do not comply, organisations can face investigations, enforcement action, significant fines, compensation claims and reputational damage, particularly following serious data breaches. Example: An application collecting account information should clearly tell users what personal data is collected and why it is needed. Freedom of Information Act (FOIA) This act gives people the right to request recorded information held by public authorities, such as government departments, councils, state schools and the NHS, subject to exemptions. To comply, when developing software for a public authority, developers should consider how information can be stored, organised, searched and retrieved so the organisation can respond appropriately to information requests. Non-compliance may cause a public authority to face complaints, investigations, enforcement action and reputational damage if it fails to meet its legal responsibilities. Example: A system developed for a council should allow relevant recorded information to be located when the council receives a valid FOI request. Privacy and Electronic Communications Regulations (PECR) These regulations protect people's privacy when using electronic communications, including rules covering electronic marketing, cookies and similar technologies, and the security/privacy of communications services. To comply, developers may need to ensure applications obtain appropriate consent for non-essential cookies or similar technologies, provide relevant information to users and follow the rules when enabling electronic marketing such as emails or text messages. If they don't comply, organisations could face regulatory action, financial penalties, complaints and reputational damage. Example: A website should not simply place certain advertising or analytics cookies on a user's device without providing the required information and obtaining consent where required. Independent Bodies Independent bodies are organisations that operate separately from the organisations they oversee and can provide guidance, monitor compliance and take action when rules or standards are not followed. When developing application software, independent bodies may: Provide guidance and codes of practice that developers and organisations can follow. Monitor and investigate whether organisations are meeting their legal responsibilities. Handle complaints from users or members of the public. Take or recommend enforcement action when organisations fail to comply. Help developers understand how legislation should be applied to applications and user data. Information Commissioner's Office (ICO) The Information Commissioner's Office (ICO) is the UK's independent regulator for information rights and data protection, overseeing areas including the DPA, UK GDPR, FOIA and PECR. When developing application software, the ICO is relevant because it: Provides guidance on how personal information should be collected, processed, stored and protected. Helps organisations understand how to comply with data protection and privacy legislation. Can investigate complaints and data breaches. Can take enforcement action when organisations fail to meet their legal obligations. Promotes good practice in areas such as privacy, electronic marketing, cookies and protecting users' information. Example: If developers create an application that collects users' names, email addresses and dates of birth, they can use ICO guidance to help ensure the application handles this personal data appropriately and complies with data protection requirements. Q uesto's Q uestions 6.1 - Legal Considerations: 1. State the main purposes of the CMA, DPA, UK GDPR, FOIA and PECR. [ 2 each ] 2. For each act or regulation, explain the actions developers should take to ensure application software complies with its requirements. [2 each ] 3. Explain the possible impacts on an organisation if its application software does not comply with relevant legislation or regulations. [2 each ] 4. Explain the role of independent bodies and the Information Commissioner's Office (ICO) when developing and operating application software. [4 ] 5. A revision app collects users' personal data, uses cookies and sends marketing emails. Identify the relevant legislation and explain how the developers should comply with it. [4 ] Following a 2018 cyberattack, personal data belonging to more than 400,000 British Airways customers was compromised. In 2020, the Information Commissioner's Office (ICO) fined British Airways £20 million for failing to adequately protect its customers' data, the largest data protection fine the ICO has issued. D id Y ou K now? 5.3 - Policies Topic List

Learn about application software installation methods, including clean, remote, cloud, mobile and network installation. Resources based on Unit F161 (Developing Application Software) for the OCR Cambridge Advanced Nationals in Computing (H029 / H129) AAQ (Alternative Academic Qualification). Qualification: Cambridge Advanced Nationals in Computing (AAQ) Certificate: Computing: Application Development (H029 / H129) Unit: F161: Developing Application Software 5.2 - Application Software Installation Watch on YouTube : Application installation You need to know how different installation processes (e.g. clean , remote , cloud , network and mobile installs) work as well as their advantages , disadvantages and appropriate uses . What You Need to Know Application Installation Application software can be installed using different methods depending on factors such as the number of devices, their location, network availability and the requirements of the users or organisation. Ghost / Image A master copy (known as an image) of a correctly configured system containing the required software and settings is created and then copied or deployed to other devices. This is used when the same applications and configuration need to be installed on many devices, such as computers in a school or business. It allows many devices to be configured quickly and consistently, reducing repetitive installation work and ensuring they have the same software and settings. However, creating and maintaining the image takes time, devices may need compatible hardware/configurations, and an error or outdated application in the master image could be copied to every device. Upgrade An upgrade is when a newer version is installed over an existing version, usually retaining the user's existing data, settings and configuration. It is required when users need to move to a newer version of an application without completely reinstalling it. Upgrading is usually quicker and more convenient than a clean install and allows existing settings and data to be retained. But existing problems, unnecessary files or incompatible settings may remain and compatibility issues can occur between versions. Clean Install Any previous installation is removed or ignored and a completely new copy of the application is installed. It is used when installing an application for the first time, or when an existing installation has serious problems and a fresh installation is required. A clean install provides a fresh installation without problems or unwanted settings from an older version, which can improve reliability. However, it can be more time-consuming, and existing settings or application data may be lost if they are not backed up first. Repair/Modify Install An existing installation is reopened to repair damaged or missing files, or add/remove installed features without completely reinstalling the application. This is used when an application is not functioning correctly or when its installed features need to be changed. It is usually quicker than completely reinstalling the application and can retain existing settings and data. But it may not fix more serious problems, and the required installation or repair files must be available. Remote Install An administrator installs application software onto another device from a different location, usually using remote management software or tools. It is used when IT staff need to manage devices without physically accessing them, such as employee computers across different offices. A remote install saves time and travel, allows centralised management and can enable IT staff to install software on many geographically separated devices. However, it requires network connectivity, appropriate permissions and remote management tools. Connection problems could interrupt the installation. Unattended Install The installation is automated using predefined options and settings, allowing it to complete without the user responding to installation prompts. It is used when installing the same application and settings on many devices or when installations need to occur without staff being present. Advantages are that it requires little or no user interaction, saves staff time and ensures consistent installation settings across devices. However, it requires careful configuration beforehand, and incorrect predefined settings could cause the same installation problem across multiple devices. Cloud Install Installation files are downloaded from an internet-based cloud service and then installed onto the device. It's suitable for when users or organisations need to download applications directly over the internet, particularly across different locations and devices. Cloud installs can be accessed from many locations and devices, it does not require physical installation media, can support automatic updates and may allow installations to be scheduled for convenient times. But it depends on a reliable internet connection, interrupted downloads can cause problems, large applications can use significant bandwidth, and the device must meet the software's requirements. Mobile Install An application is usually downloaded and installed through a mobile app store onto a smartphone or tablet. It's needed for applications designed for mobile devices, such as installing a revision app onto a student's tablet. It is usually simple and convenient for users, app stores can manage installation and updates, and applications can be installed directly onto the user's device. However, it requires sufficient storage and a compatible operating system, downloads can consume mobile data, connectivity problems can interrupt installation and app stores may restrict what applications can be distributed. Network Install Installation files are stored in a central location on a local network and accessed by devices connected to that network. It is used when an organisation needs to install software on multiple devices connected to the same network, such as computers around a school. Advantages are that installation files can be managed centrally, physical installation media is not required for each device, and many devices can access the same installation files. But it requires a working network connection, installing on many devices can increase network traffic and problems with the network or central server could prevent installations. Q uesto's Q uestions 5.2 - Application Software Installation: 1. Describe how each application software installation method is completed: ghost/image and deployment, upgrade, clean install, repair/modify, remote, unattended, cloud, mobile and network installation. [ 2 each ] 2. Give an example of when each installation method would be appropriate to use. [1 each ] 3. Give the advantages and disadvantages of each application software installation method. [4 each ] 4. Explain the differences between remote, unattended, cloud and network installation. [3 ] 5. For installing new software in a school, recommend a suitable installation method and justify why it would be appropriate. [ 4 ] The PC version of Baldur's Gate was originally released on five CDs in 1998, with players swapping discs during installation. As games became larger, lengthy multi-disc installations became common, sometimes leaving players waiting hours before they could start playing. D id Y ou K now? 5.1 - Testing Topic List 5.3 - Policies

Learn about security threats, including botnets and DDoS attacks and both physical and digital security mitigations. Resources based on Unit F161 (Developing Application Software) for the OCR Cambridge Advanced Nationals in Computing (H029 / H129) AAQ (Alternative Academic Qualification). Qualification: Cambridge Advanced Nationals in Computing (AAQ) Certificate: Computing: Application Development (H029 / H129) Unit: F161: Developing Application Software 4.1 - Security Considerations Watch on YouTube: Security threats Physical security Digital security You need to know the risks that specific security threats pose to applications , including botnets , DDoS attacks , hacking and malware . You need to know how both physical security mitigations (e.g. biometrics , locks and RFID ) and digital security mitigations (e.g. encryption , firewalls and anti-malware ) protect application software against threats . What You Need to Know Security Threats Common threats to application software include: Botnet A botnet is a group of compromised devices that are remotely controlled by an attacker, often without their owners knowing, and used together to carry out malicious activities. DoS / DDoS Attack A Denial of Service (DoS) attack attempts to make a system or service unavailable by overwhelming it with requests or traffic. A Distributed Denial of Service (DDoS) attack does this using many devices at the same time, often through a botnet. Hacking Hacking is gaining unauthorised access to a computer system, network or data, potentially allowing data to be viewed, changed, stolen or deleted. Lack of Supplier Support Lack of supplier support occurs when a manufacturer or developer no longer provides updates, security patches or technical assistance for hardware or software, leaving newly discovered vulnerabilities unfixed. Malicious Spam Malicious spam is unwanted messages sent to large numbers of users that contain harmful or deceptive content, such as links designed to steal information or distribute malware. Malware Malware is software intentionally designed to damage, disrupt or gain unauthorised access to systems or data. Examples include viruses, worms, ransomware and spyware. Out-of-date Software Out-of-date software may contain known security vulnerabilities that newer versions have fixed, making it easier for attackers to compromise the system. Out-of-date Hardware Out-of-date hardware may lack modern security features, be incompatible with newer security software, or no longer receive support from its manufacturer. Out-of-date Firmware Firmware is software built into a device that controls how its hardware operates. Out-of-date firmware may contain unpatched security vulnerabilities that attackers could exploit to access or interfere with the device. Physical Security Mitigations Physical security mitigations are measures used to prevent unauthorised physical access to, theft of, or damage to devices and systems that run application software. Biometrics Uses unique physical characteristics, such as fingerprints or facial features, to verify a person's identity and prevent unauthorised users from physically accessing devices and application software. Cable Locks Physically secure devices such as laptops to a fixed object, reducing the risk of equipment being stolen and the application software or data on it being accessed. Cameras Monitors and records areas containing computer equipment, helping to deter unauthorised access or theft and providing evidence if a security incident occurs. Locks Restricts physical access to rooms, cabinets or equipment to authorised people, helping prevent devices and the application software they contain from being accessed, stolen or damaged. RFID Radio Frequency Identification (RFID) can use tags or cards to identify authorised users and control physical access to restricted areas, such as server rooms. Safe Provides secure physical storage for devices or storage media, protecting them against unauthorised access, theft and potentially physical damage. Swipe Cards Requires users to swipe or scan an authorised card to enter restricted areas, preventing unauthorised people from physically accessing devices and systems containing application software. Digital Security Mitigations Digital security mitigations are measures that use software, technology and access controls to protect application software, systems and data from security threats. Access Rights Control what resources and actions different users are allowed to access, such as viewing, editing or deleting data, helping prevent unauthorised access or changes. Anti-Malware Software that detects, blocks and removes malware, helping prevent malicious software from damaging applications, stealing data or gaining unauthorised access. Back-up Creates a separate copy of data that can be restored if the original is lost, damaged or corrupted, for example following a malware attack or hardware failure. Cryptography Uses mathematical techniques to protect data and communications, helping keep data confidential, verify its authenticity and prevent unauthorised changes. 2FA Requires a user to provide two different forms of authentication before gaining access, such as a password plus a code or approval from another device, making unauthorised access more difficult if one factor is compromised. Encryption Converts data into an unreadable form that requires the correct key to decrypt, preventing unauthorised users from understanding it if they gain access. Encryption at rest: Protects stored data, such as files on a device or records in a database, if the storage is accessed or stolen. Encryption in transit: Protects data while it is being transferred across a network, reducing the risk of intercepted data being read. Firewalls A firewall monitors and controls network traffic using security rules, helping prevent unauthorised or suspicious connections. Hardware firewall: A physical network device, often built into or associated with a router, that can protect multiple devices by filtering traffic entering or leaving a network. Software firewall: Software installed on a specific device that monitors and controls network traffic for that device and its applications. Q uesto's Q uestions 4.1 - Security Considerations: 1. Describe the following security threats : botnets , DoS/DDoS attacks , hacking , lack of supplier support , malicious spam and malware . [ 2 each ] 2. Explain why out-of-date software , hardware and firmware can create security risks for application software . [3 ] 3. Explain how physical security measures , including biometrics , cable locks , cameras , locks , RFID , safes and swipe cards , can protect application software and systems. [2 each ] 4. Explain how access rights , anti-malware , backups , cryptography , encryption , firewalls and 2FA can protect application software from security threats. [2 each ] 5. For an online mobile game , recommend suitable physical and digital security mitigations and justify how they would protect against specific threats . [6 ] The WannaCry ransomware attack of 2017 affected hundreds of thousands of computers worldwide , including NHS systems . It exploited a vulnerability in older or unpatched Windows systems and resulted in an estimated 19,000 NHS appointments and operations being cancelled . D id Y ou K now? 3.2 - Protocols Topic List 5.1 - Testing

Learn about policies related to application development, including a user guide, acceptable use policy (AUP), backup, codes of practice, staying safe online and the use of information. Resources based on Unit F161 (Developing Application Software) for the OCR Cambridge Advanced Nationals in Computing (H029 / H129) AAQ (Alternative Academic Qualification). Qualification: Cambridge Advanced Nationals in Computing (AAQ) Certificate: Computing: Application Development (H029 / H129) Unit: F161: Developing Application Software 5.3 - Policies Watch on YouTube : Policies You need to know the purpose , content and application of each policy to be considered when related to developing application platforms . What You Need to Know Policies Policies provide rules, guidance and information that help ensure an application platform is developed and used safely, responsibly and effectively. Application User Guide An application user guide provides users with instructions and information about how to install, access and use the application correctly. It may include system requirements, installation instructions, explanations of features, step-by-step instructions, troubleshooting advice and contact/support information. Developers create and maintain documentation that reflects the finished application and is accessible and understandable to its intended users. System requirements are an important part of the guide as they allow users to check that their device and operating system are compatible before installation, helping prevent errors and providing useful information when troubleshooting problems. Acceptable Use Policy (AUP) An acceptable use policy (AUP) defines rules about how an application or service can and cannot be used, encouraging appropriate and responsible behaviour. It includes acceptable and unacceptable activities, user responsibilities, prohibited content or behaviour, security requirements and possible consequences of breaking the rules. Developers ensure users are given access to the AUP and may be required to agree to it before using the application or service. Features may also be designed to help enforce its rules. For example, a school's learning platform could prohibit users from sharing passwords, posting offensive content or attempting to access another student's account. Backup Policy A backup policy ensures that important application data can be recovered if the original data is lost, damaged, corrupted or affected by a security incident. The policy defines what data should be backed up, how often backups occur, where they are stored, how long they are retained and how data can be restored. Developers ensure the application supports the organisation's backup requirements, such as automatically backing up user data at scheduled intervals and securely storing backup copies. For example, a school application could automatically back up student records each day so they can be restored following data loss. Codes of Practice Codes of practice provide standards and guidelines for good professional practice when developing and operating application platforms. They may cover areas such as security, accessibility, privacy, ethical behaviour, development standards and handling user data responsibly. Developers follow relevant professional or industry guidelines throughout the development process when designing, coding, testing and maintaining the application. For example, developers could follow accessibility guidance to make an application usable by people with different accessibility needs. Staying Safe Online A staying safe online policy promotes responsible internet use and protects the safety and well-being of users, helping create a safe and respectful online environment. It includes guidance about protecting personal information, communicating safely, appropriate online behaviour, recognising suspicious content and reporting concerns. Developers can provide safety information and suitable features, such as privacy controls, reporting systems, blocking features and warnings about sharing personal information. For example, a social application could allow users to block and report other accounts and provide guidance about not sharing personal information. Use of Information This type of policy explains how an organisation collects, uses, stores and shares users' information, providing transparency, building trust and helping meet legal responsibilities. It identifies what information is collected, why it is required, how it will be used and stored, who it may be shared with, users' rights and restrictions on misuse. Developers design the application so that information is collected and processed according to the policy, including appropriate privacy controls, permissions and security measures. For example, an application collecting users' email addresses should explain why they are collected, how they will be used and who can access them. Q uesto's Q uestions 5.3 - Policies: 1. Explain the purpose of an application user guide and describe the information it should contain. [ 3 ] 2. Explain the purpose and content of an Acceptable Use Policy (AUP), including how it can be applied to an application platform. [4 ] 3. Explain the purpose of backup policies and codes of practice and how developers can apply them when developing application platforms. [4 ] 4. Explain the purpose and content of a staying safe online policy and how its requirements could influence the features of an application. [4 ] 5. Explain the purpose and content of a use of information policy, including how developers can ensure information is collected, stored, used and shared appropriately. [ 4 ] During the production of Toy Story 2, a command accidentally deleted a huge amount of the film's production data. Pixar discovered that its backups had problems too, but supervising technical director Galyn Susman had a copy of the project stored on her computer at home while working remotely, which allowed much of the deleted work to be recovered. D id Y ou K now? 5.2 - Application Installation Topic List 6.1 - Legal Considerations

Learn about the importance of testing applications, test plan structure, test types and test data. Resources based on Unit F161 (Developing Application Software) for the OCR Cambridge Advanced Nationals in Computing (H029 / H129) AAQ (Alternative Academic Qualification). Qualification: Cambridge Advanced Nationals in Computing (AAQ) Certificate: Computing: Application Development (H029 / H129) Unit: F161: Developing Application Software 5.1 - Testing Watch on YouTube : Purpose of testing Test plan structure Test data Types of testing You need to know the purpose , importance , advantages and disadvantages of testing applications , as well as the impacts of not carrying out testing . You must understand the structure and contents of test plans and the importance of testing , remedial actions and retesting during application development. You need to know the role of each type of test data (normal , extreme and erroneous ). Finally, the purpose , advantages and disadvantages of each type of testing (technical and user ) must be known as well as when and how each type should take place . What You Need to Know Testing Testing is the process of checking application software to identify problems and ensure that it works correctly and meets its requirements before it is released. Purpose of Testing Key purposes of testing application software include: Identify and fix defects such as bugs and errors before the application is released. Check that the requirements are met so the application performs the functions expected by the user or client. Check reliability and performance under different conditions and workloads. Improve security by identifying vulnerabilities that could be exploited. Check compatibility across the required devices, operating systems or screen sizes. Ensure compliance with relevant legal, regulatory or industry requirements. Support continuous improvement by identifying areas where the application could be refined or optimised. Why Testing is Important Testing is important because it helps developers produce reliable, secure and high-quality software that meets user requirements. Finding problems during development also allows them to be corrected before they affect users and can make problems cheaper and easier to fix. If application software is not properly tested: Bugs and errors may remain, causing features to work incorrectly or the application to crash. User experience may be poor, causing frustration and reducing confidence in the application. Security vulnerabilities may remain, increasing the risk of data breaches and cyberattacks. Compatibility problems may occur, meaning the application does not work correctly on some devices or operating systems. Incorrect information or results may be produced, potentially leading users to make incorrect decisions. Financial and reputational damage may occur, particularly if users stop using the application, request refunds or leave negative reviews. Requirements may not be met, meaning the finished application does not achieve its intended purpose. Testing Advantages Testing Disadvantages Improved quality: Identifies bugs and defects so they can be corrected. Greater customer satisfaction: Helps ensure the application meets users' requirements and expectations. Cost effectiveness: Finding problems early can be cheaper than fixing them after release. Reduced risk: Identifies potential problems before they cause failures for users. Improved security: Can identify vulnerabilities before attackers have an opportunity to exploit them. Better user experience: Helps ensure features work correctly and consistently. Time-consuming: Thorough testing takes time and could affect development deadlines. Additional costs: Testing requires staff, time and potentially specialist testing software. Human error: Testers may make mistakes or overlook problems. Complex testing tools: Automated testing tools can require specialist knowledge to configure and maintain. False positives: Testing tools may incorrectly identify something as a problem, wasting developers' time investigating it. Limited scope: It may be impossible to test every possible situation, so some defects may remain after release. Test Plan Structure A test plan is a structured document that outlines the tests that will be carried out on application software, including how each test will be performed and the expected and actual results. Parts of a test plan include: Test number: A unique number or identifier given to each test so it can be easily referenced and tracked. Test type: Identifies the type or category of testing being carried out, such as functional, usability or compatibility testing. Test description: A brief description of what feature or part of the application is being tested. Purpose: Explains why the test is being carried out and what it aims to check. Procedure: Describes the steps the tester must follow to carry out the test. Test data: The values or inputs entered into the application during the test. Expected result: Describes what should happen if the application works correctly. Actual result: Records what actually happened when the test was carried out. Remedial action required: Records any changes or fixes needed if the actual result does not match the expected result. Remedial action fixes errors found during initial testing to ensure the software performs as intended. Retest result: Records the outcome after the test is repeated following any remedial action, confirming whether the problem has been fixed. Types of Test Data Test data is the data entered into application software during testing to check that it handles different types of input correctly. Normal Data Normal data is valid and within the expected range or format for an input. It is used during testing to check that the application accepts and correctly processes typical data that users are expected to enter. Example: If an age field accepts values from 18 to 100, 35 would be normal test data. Extreme Data Extreme data is valid data that is at the boundaries of the permitted range, such as the minimum or maximum allowed value. It is used during testing to check that the application correctly accepts and processes values at its limits. Example: If an age field accepts values from 18 to 100, 18 and 100 would be extreme test data. Erroneous Data Erroneous data is invalid because it is outside the permitted range, has the wrong data type or does not follow the required format. It is used during testing to check that the application rejects or handles invalid data appropriately, such as by displaying an error message. Example: If an age field accepts whole numbers from 18 to 100, 17, 101 or "twenty" would be erroneous test data. Types of Testing Technical Testing Technical testing checks whether the application works correctly, reliably and securely from a technical perspective. Its purpose is to identify technical faults, bugs, performance problems and compatibility or security issues so they can be corrected. Technical testing takes place throughout development, before release and after significant updates or patches to check that changes have not introduced new problems. Developers or testers use planned tests and specialist testing tools, which may be manual or automated, to test different parts of the application and compare the results against what was expected. Technical testing can identify problems early in development, improve reliability, performance and security, and automated tests can be repeated efficiently. However, it can be time-consuming and expensive, may require specialist knowledge or tools, and cannot guarantee that every possible problem will be identified. There are three common types of technical testing: Fuzz Testing This is where the application is given large amounts of unexpected, invalid or random data to see how it responds. Its purpose is to identify weaknesses such as crashes, errors and security vulnerabilities when the application receives inputs the developers may not have anticipated. Example: Automatically entering unusual characters, extremely long inputs and unexpected values into an application's input fields. Load/Stress Testing The application is placed under high or increasing levels of demand to see how well it performs. It checks the application's performance, reliability and limits when many users, requests or large amounts of data are being handled. Example: Simulating thousands of customers attempting to use an online shop at the same time before a major sale. Migration Testing Checks that data or an application has been transferred correctly from one system, platform or version to another. It ensures that data remains complete, accurate and usable and that the application continues to function after migration. Example: Checking that all customer accounts and order histories remain correct after moving them from an old database to a new one. User Testing User testing involves intended or representative users trying the application to check that it meets their needs and is suitable for real-world use. Its purpose is to identify usability, accessibility and user-experience problems and gather feedback about whether the application meets user requirements. User testing takes place when a working version of the application is available, particularly before final release, although users can test prototypes and versions throughout development. Representative users are given the application and realistic tasks or scenarios to complete, while feedback and observations about their experience are collected. User testing provides real feedback from users, reveals how people actually interact with the application, identifies usability and accessibility problems, validates design decisions and can improve user satisfaction. However, recruiting suitable users can be time-consuming and costly, feedback can be subjective or inconsistent and a small group of testers may not represent every type of user. Q uesto's Q uestions 5.1 - Testing: 1. Explain the purpose and importance of testing application software, including the possible impacts of not testing thoroughly. [ 4 ] 2. Give advantages and disadvantages of testing application software. [4 ] 3. Describe the structure of a test plan and explain the purpose of normal, extreme and erroneous test data. [6 ] 4. Compare technical testing and user testing, including their purpose, how and when they take place, and their advantages and disadvantages. [6 ] 5. Describe fuzz testing, load/stress testing and migration testing, giving an example of when each could be used. [6 ] Bethesda's Fallout 76 experienced a number of technical problems when it launched in 2018, with players reporting bugs, crashes and performance issues. Its first major update after launch was around 47 GB on consoles, despite the game itself being around 53 GB, showing how substantial post-release fixes can become when software requires further development and testing. D id Y ou K now? 4.1 - Security Considerations Topic List 5.2 - Application Installation

Learn about protocols including FTP, HTTP, POP, SMTP, SNMP, TCP, UDP, ICMP, IP and the TCP/IP stack. Resources based on Unit F161 (Developing Application Software) for the OCR Cambridge Advanced Nationals in Computing (H029 / H129) AAQ (Alternative Academic Qualification). Qualification: Cambridge Advanced Nationals in Computing (AAQ) Certificate: Computing: Application Development (H029 / H129) Unit: F161: Developing Application Software 3.2 - Protocols Watch on YouTube: Protocols TCP/IP Stack You need to know the role and uses of specific common protocols (FTP , HTTP , POP , SMTP , SNMP , TCP , UDP , ICMP , IP ). You also need to understand the structure , content and use of the 4-layer TCP/IP stack . What You Need to Know Common Protocols A protocol is a set of rules that determines how data is communicated between devices over a network . FTP FTP (File Transfer Protocol ) is used to transfer files between computers over a network , typically between a client and a server . It is used when uploading or downloading files from a server , such as transferring website files to a web server . HTTP HTTP (HyperText Transfer Protocol ) is used to request and transfer webpages and other web content between a web browser and a web server . It is used when accessing websites or when web-based applications communicate with servers . However, HTTPS is the secure , encrypted version commonly used today. POP POP (Post Office Protocol ) is used by an email client to retrieve emails from a mail server , traditionally storing them on the user's device . It is used when emails need to be downloaded from a mail server for access through an email application , particularly where local or offline access is required . SMTP SMTP (Simple Mail Transfer Protocol ) is used to send and transfer email messages between email clients and mail servers and between mail servers . It is required when a user sends an email , including transferring that email between mail servers on its way to the recipient . SNMP SNMP (Simple Network Management Protocol ) allows network administrators and management software to monitor and manage devices on a network to collect information about their status . It is used to monitor devices such as routers , switches , servers and printers , for example checking whether a network device is operating correctly . TCP TCP (Transmission Control Protocol ) provides reliable and ordered delivery of data packets between devices . It checks that packets arrive correctly and retransmits missing packets when necessary. It is used when accuracy and reliability are more important than speed , such as transferring files , loading webpages and sending emails . UDP UDP (User Datagram Protocol ) sends data quickly , although without checking that every piece has arrived or is in the correct order , reducing delays . It is used when speed is more important than perfect delivery , such as live video/audio , online gaming and voice calls . ICMP ICMP (Internet Control Message Protocol ) is used to send network status , diagnostic and error messages between network devices . It is required when diagnosing network problems and checking whether another device can be reached , such as when using the ping command. IP IP (Internet Protocol ) addresses and routes data packets across networks by using IP addresses to uniquely identify devices . It is used when data needs to be sent between devices across networks , with IP helping packets travel from the source towards the correct destination using an appropriate route . TCP/IP Stack The TCP/IP stack is a four-layer model that describes how data is prepared , transmitted across networks and received by applications . When sending data , it travels down through the layers . When receiving data , it travels up through the layers . Different protocols are used at specific layers of the model. Application Layer This is the top layer , where network applications and services interact with the network . It includes protocols such as HTTP , FTP , SMTP , POP and SNMP . It determines how applications communicate and exchange specific types of data across a network . Example : A web browser uses HTTP to request content from a web server . Transport Layer This layer is responsible for transporting data between devices and includes TCP and UDP . It determines how data should be delivered , including whether reliability (using TCP ) or speed (using UDP ) is more important . Example : TCP can ensure that a downloaded file arrives completely and in the correct order , while UDP can prioritise speed during an online game . Internet Layer This layer is responsible for addressing and routing packets between networks and includes protocols such as IP and ICMP . It ensures packets can travel towards the correct destination using IP addresses . Example : IP is used to route packets across the internet to the destination device . Network Access Layer This is the lowest layer , concerned with how data is physically transmitted across the network using technologies such as Ethernet (a wired connection) and WiFi . It handles communication between a device and the network it is directly connected to . Example : A laptop could transmit data wirelessly to a local router using WiFi . Q uesto's Q uestions 3.2 - Protocols: 1. What is a network protocol , and why do you think protocols are needed when devices communicate ? [ 2 ] 2. State the role of FTP , HTTP , POP , SMTP and SNMP and give an example of when each would be used. [2 each ] 3. State the role of TCP , UDP , ICMP and IP and give an example of when each would be used. [2 each ] 4. Describe the structure and purpose of each of the four layers of the TCP/IP stack . [2 each ] 5. Explain how different protocols and layers of the TCP/IP stack can work together to transfer data across a network , such as sending an email on a wired connection . [ 4 ] Online games use UDP because receiving data quickly is often more important than receiving every single packet . A tiny amount of missing data may be preferable to the game pausing while it waits for it to be resent . D id Y ou K now? 3.1 - APIs Topic List 4.1 - Security Considerations

Learn about Application Programming Interfaces (APIs), including their roles, types (composite, internal, private, public, partner) and architecture (REST, SOAP, RPC). Resources based on Unit F161 (Developing Application Software) for the OCR Cambridge Advanced Nationals in Computing (H029 / H129) AAQ (Alternative Academic Qualification). Qualification: Cambridge Advanced Nationals in Computing (AAQ) Certificate: Computing: Application Development (H029 / H129) Unit: F161: Developing Application Software Watch on YouTube: API roles API architecture 3.1 - Application Programming Interface (API) You must know the role and uses of Application Programming Interfaces (APIs ) as well as the uses , advantages and disadvantages of each API type (composite , internal , private , public , partner ). You must also understand the uses , advantages and disadvantages of API architecture (REST , SOAP , RPC ). What You Need to Know Roles of an API An Application Programming Interface (API ) allows different applications or systems to communicate and exchange data using a defined set of rules . Roles of an API include: Setting communication rules by defining the methods that allow an application to communicate correctly with a server . Transferring data by allowing an application to request data from a server and receive the requested information in response. Increasing security by providing a controlled way of accessing a server's data or services , rather than giving an application direct access to the server and its data . As an example , a weather app could use an API to request today's weather data from a weather service's server , which then returns the requested information for the app to display . Types of API Composite API A composite API combines multiple API requests into a single request , allowing several pieces of data or tasks to be handled together . It is used when an application needs data from several sources or needs several related actions completed at once . Such as an online shop retrieving customer , order and delivery i nformation simultaneously . A composite API can reduce the number of separate requests , making complex operations simpler and potentially improving performance . But it can be more complex to develop and maintain , and a problem with one part of the combined request could affect the overall response . Internal API An internal API is designed for use within an organisation , allowing its own applications and systems to communicate . It is used when different systems inside the same organisation need to exchange data , such as a school's student-record system sharing data with its attendance system . An internal API can improve communication and data sharing between internal systems while allowing the organisation to control how the API works . However, it usually cannot be accessed by external organisations , and the organisation is responsible for developing , securing and maintaining it. Private API A private API is where access is restricted to authorised developers or users , usually through authentication such as credentials . It is used during private development and testing , or when developers need controlled access to confidential back-end data and services . A private API provides greater control and security , helping protect confidential data and intellectual property while allowing authorised developers (including remote developers ) to access what they need . But restricted access limits outside involvement and integration , and the organisation is responsible for developing , testing , securing and maintaining the API. Public API A public API is made available to external developers or the general public to access certain data or services . It is used when an organisation wants other applications to use its data or services , such as allowing developers to retrieve weather , mapping or transport information . Public APIs encourage third-party development and integration , potentially increasing the number of applications making use of a service . However, it creates greater security and management requirements , and heavy usage may place additional demand on servers , so access may need to be limited . Partner API A partner API is shared with selected external organisations or business partners , rather than being available to everyone . It is used when two organisations need their systems to securely share data or services , such as an online retailer communicating with a delivery company's system . A partner API allows organisations to use specialist services provided by trusted partners rather than developing everything themselves , potentially reducing development time and costs . However, it creates dependency on the API provider . Also, downtime , security problems , rate limits or limited customisation could affect the application. API Architecture API architecture describes the rules and structure used by an API . REST (Representational State Transfer) REST is an API architecture that commonly uses standard web/HTTP methods to request , add , update or delete data , often exchanging data using JSON . it is commonly used for web and mobile applications that need to communicate with servers , such as an app requesting user account information . REST is simple and easy to use , works across different platforms , uses standard web technologies , is stateless so requests can be handled independently and is scalable for applications with many users . But it provides less strict standardisation than SOAP and developers may need to implement additional security , validation and error handling themselves. SOAP (Simple Object Access Protocol) SOAP is a strict and standardised protocol for exchanging structured information between applications , usually using XML to format messages . It is often used where security , reliability and strict rules are particularly important, such as financial , payment or large business systems . SOAP has strict standards and built-in support for features such as security and error handling , making communication reliable and consistent . However, it can be more complex to develop and use and its XML messages contain lots of tags , making them larger and potentially slower to process than REST. RPC (Remote Procedure Call) RPC is an API architecture that allows an application to request that a function/procedure is carried out on another computer or server , as though it were being carried out locally . It is useful when an application needs to perform specific actions on a remote system , such as requesting a server to calculate a value and return the result . RPC can be simple and efficient for performing specific actions , as the developer can directly request the required procedure . But it can create a strong dependency between the client and server , meaning changes to procedures on the server may require changes to the application . Also, network problems can prevent the procedure from completing . Q uesto's Q uestions 3.1 - Application Programming Interface (API): 1. What is the role of an API , and how can APIs help applications and servers communicate securely ? [ 3 ] 2. Describe composite , internal , private , public and partner APIs , giving an example of when each could be used. [3 each ] 3. Give advantages and disadvantages of composite , internal , private , public and partner APIs . [4 each ] 4. Describe REST , SOAP and RPC API architectures and explain when each would be suitable . [4 each ] 5. Compare the advantages and disadvantages of REST , SOAP and RPC . [ 6 ] A single application can communicate with multiple APIs . For example, a travel app could use separate services for maps , weather , payments and transport information rather than developing every feature itself. D id Y ou K now? 2.3 - Data States Topic List 3.2 - Protocols

Learn about the three data states - at rest, in transit (in motion) and in use. Resources based on Unit F161 (Developing Application Software) for the OCR Cambridge Advanced Nationals in Computing (H029 / H129) AAQ (Alternative Academic Qualification). Qualification: Cambridge Advanced Nationals in Computing (AAQ) Certificate: Computing: Application Development (H029 / H129) Unit: F161: Developing Application Software 2.3 - Data States Watch on YouTube: Data States You need to understand the characteristics and uses of the three data states (at rest , in transit (in motion) and in use ) What You Need to Know Data States Data states describe what is happening to data at a particular time - whether it is being stored , transferred or actively used . At Rest Data is at rest when it is stored on a device or storage system and is not currently being transferred or processed . It remains in a stable state until it is accessed , changed or deleted . It is for when data needs to be stored for later use , such as files saved on an SSD , customer details in a database or photos stored on a phone . In Transit Data in transit (also known as data in motion ) is actively moving from one location or device to another , often across a network . It may be sent to multiple users but is susceptible to interception or security attacks while being transferred . It is used when data needs to be sent or shared , such as loading a webpage , sending an email , uploading a file to cloud storage or streaming a video . In Use Data in use is currently being accessed , processed or changed by a user , application or computer system . It is used when an application needs to work with data , such as editing a document , calculating values in a spreadsheet , processing a database search or editing graphics . Q uesto's Q uestions 2.3 - Data States: 1. What is meant by a data state ? [ 1 ] 2. Describe the characteristics of data at rest , data in transit and data in use . [2 each ] 3. Give two examples of when data would be at rest , in transit and in use . [2 each ] 4. Explain how the same piece of data could move between all three data states . [3 ] 5. What might data in transit be particularly susceptible to? [2 ] When you stream a film on Netflix , its data can move through different states : it is at rest on a server , in transit while being sent across the internet , and in use when your device processes it for playback . D id Y ou K now? 2.2 - Data Flow Topic List 3.1 - APIs

Learn about how data is input to an application to be converted and output as information. Covers types of data and information such as numbers, text, audio and images as well as the black box concept to show data flow in a diagram. Resources based on Unit F161 (Developing Application Software) for the OCR Cambridge Advanced Nationals in Computing (H029 / H129) AAQ (Alternative Academic Qualification). Qualification: Cambridge Advanced Nationals in Computing (AAQ) Certificate: Computing: Application Development (H029 / H129) Unit: F161: Developing Application Software 2.2 - Data Flow Watch on YouTube: Data vs Information Data Input Information Output Black Box Concept You need to know the difference between the terms 'data ' and 'information ' and how data is input to be converted to information as an output . There are specific types of input and output , including numbers , text , movement , audio and images . You need to understand how data and information flows through application software and can be stored . You must be able to represent data flow in a diagram using the black box concept . What You Need to Know Data and Information Data is raw , unprocessed facts and values , while information is data that has been processed and given meaning or context so that it is useful . Data is converted into information through processing , such as calculating , sorting , filtering , comparing or organising it. For example, individual test scores are data and then calculating the class average produces information . Data flows into an application through inputs , is processed and/or stored and then flows out as useful information through outputs . Data Input & Information Output Numbers are numerical data entered into or produced by a system, including a whole number ( integer ) and decimal values ( real ). For example, entering a person's age , recording a temperature from a sensor or displaying a player's score . Text includes letters , numbers , symbols or words entered into or displayed by a system. For example, entering a username , typing a search query , displaying instructions or showing an error message . Movement is data about the position , direction or motion of a person or object , often captured using sensors or cameras . Examples include a phone detecting that it has been tilted , a fitness tracker detecting steps or a games console detecting controller movements . Audio is sound that is captured as input or produced as output by a system. Examples are speaking into a microphone for voice recognition , recording music , playing sound effects or receiving spoken directions from a navigation app . Moving images are a sequence of images displayed rapidly to create the appearance of movement , usually as video or animation . For example, recording video with a camera , watching a video tutorial , a video call or an animation in a game . Static images are single images that do not move , such as a photograph , drawing or diagram . Examples are taking a photo with a phone camera , scanning a QR code , displaying a logo or showing an image in an app. Storage Locations See section 1.3 for information about the two main storage locations required for application software : on-site storage and cloud storage . Black Box Concept The black box concept is a way of representing a system by focusing on what data enters the system , what is stored and what information leaves the system , without needing to understand the internal processes or any code . For example, consider a school quiz application : Flow-in is data that is entered into the system from an external source . Such as when a student selects an answer to a multiple-choice question , which is sent into the quiz application . Flow to storage is data that the system saves so that it can be accessed later . For example, the student's answer and score are saved to a database so their results can be viewed later . Flow-out is information that is sent out of the system to a user or another system , such as the quiz application displaying the student's final score on the screen. Q uesto's Q uestions 2.2 - Data Flow: 1. Explain the difference between data and information , giving an example of each. [ 3 ] 2. Explain how application software can process data to turn it into useful information . [2 ] 3. Describe the following types of input/output data and give an example of each: number , text , movement , audio , moving images and static images . [2 each ] 4. Explain the black box concept and the terms flow in , flow to storage and flow out . [4 ] 5. Using an application of your choice , describe how data could flow into the application , be processed or stored , and flow out as useful information . [ 4 ] A controller isn't the only way to play a video game ! The Nintendo Wii and Nintendo Switch can use movement as input , music games like SingStar use audio from microphones , and the EyeToy on the PlayStation 2 used images from a connected camera . D id Y ou K now? 2.1 - Data Formats & Types Topic List 2.3 - Data States

Homepage for learning about computer science in school. Discover topics across GCSE and Level 3 IT subjects, plus programming languages including Python, HTML and Greenfoot. C omputer S cience Newb ie s Popular topics: Python Programming Application Development OCR Cambridge Advanced National in Computing (AAQ) A-Level Computer Science You are viewing the mobile version of CSNewbs. The site will appear better on a desktop or laptop . OCR A-Level (H446) GCSE Computer Science OCR GCSE (J277) Latest YouTube Video Latest Blog Post Links & Information YouTube Channel Last updated: Saturday 15 th August 2026 Millions of visits since 2017! About CSNewbs

An explanation and introduction to the OCR Level 3 Cambridge Advanced National in Computing specification. This certificate (H029) or extended certificate (H129) is an Alternative Academic Qualification (AAQ). Level 3 Alternative Academic Qualification (AAQ) / Cambridge Advanced National In Computing Computing: Application Development Everything you need to know about this course: The Cambridge Advanced National in Computing: Application Development is a new course that began in September 2025 . It contains both exam and NEA (coursework ) units and focuses on developing software prototypes for applications such as websites , video games and even virtual reality . The video to the left explains all the key details of this new course, but remember, things can change so the OCR website will have the latest updates . Exam Units: Unit F160: Fundamentals of Application Development F160 YouTube Playlist Unit F161: Developing Application Software F161 YouTube Playlist These pages are based on content from the OCR Cambridge Advanced National in Computing (AAQ) specification .

Learn about on-site storage and cloud storage methods such as private, public, hybrid and community. Resources based on Unit F161 (Developing Application Software) for the OCR Cambridge Advanced Nationals in Computing (H029 / H129) AAQ (Alternative Academic Qualification). Qualification: Cambridge Advanced Nationals in Computing (AAQ) Certificate: Computing: Application Development (H029 / H129) Unit: F161: Developing Application Software 1.3 - Storage Watch on YouTube : On-Site Storage Cloud Storage Locations Cloud Storage Types There are five types of on-site (local ) storage you need to know - file servers , network attached storage (NAS ) devices, portable storage devices, solid state drives (SSD ) and storage area networks (SAN ). In regards to cloud storage , you need to know the different locations (private , public , hybrid and community ) and types (file , object , block , elastic /scalable and cloud-based database services . You need to be aware of the characteristics , advantages and disadvantages of each storage location and type as well as the factors to consider when selecting a storage location and type . What You Need to Know On-Site Storage On-site storage is physically located at the same site as the user or organisation , such as in a building or office , rather than being stored over the internet in the cloud . It gives the organisation direct control over its storage devices and data . File Servers File servers are central computers that store files for users on a network , allowing multiple people to access and share data from one location . They make it easy to manage files , set user permissions and perform backups in one place . However, they can be expensive to set up and maintain , and if the server fails , all users may lose access . Performance can also slow down if too many users access it at once . NAS Devices A network attached storage ( NAS ) device is a dedicated storage unit connected to a network , designed specifically for storing and sharing files . It is usually simpler and cheaper than a full file server , making it suitable for small networks or home use as they are easy to install and useful for backups . But they are less powerful , have limited scalability and their performance depends heavily on the network speed . Portable Storage Devices Solid States Drives (SSDs) Portable storage devices , such as USB flash drives and external hard drives , are small , removable devices that connect directly to a computer . They are highly portable , affordable and convenient because they do not require a network connection . However, they are easy to lose or damage , can pose security risks if stolen or infected with malware , and typically have less storage capacity than larger systems . SSDs are storage devices that use flash memory instead of moving parts and are commonly found inside computers or used externally . They offer very fast read and write speeds , are durable , silent and energy efficient . On the downside, they are more expensive than traditional hard drives , often have lower storage capacity for the price , and can wear out over time due to a limited number of write cycles . Storage Area Networks A storage area network ( SAN ) is a high-speed network that provides access to consolidated storage , typically used by large organisations . It allows for extremely fast data access , high reliability and can be scaled to store very large amounts of data . However, SANs are very expensive to implement , complex to manage and require specialist knowledge to maintain . Cloud Storage Locations Cloud storage is a way of storing data on servers that are accessed over the internet , allowing users to access their files from anywhere with an internet connection . Private Cloud Public Cloud A private cloud is used by a single organisation , either hosted on-site or by a third party . It offers high levels of control , security and customisation , making it suitable for organisations handling sensitive data or needing to comply with data privacy regulations . However, it is expensive to set up and maintain and the organisation is responsible for managing and updating the system. A public cloud is provided by external companies and shared between multiple users or organisations over the internet . Examples include Google Drive and Dropbox . It is cost-effective , easy to access from anywhere and requires no maintenance by the user . It is also scalable if more space is required at a later time and convenient . However, it offers less control over data , may raise security and privacy concerns and depends on a reliable internet connection . Hybrid Cloud A hybrid cloud combines both private and public cloud storage , allowing data to be shared between them . Organisations can keep sensitive data in the private cloud while using the public cloud for less critical data . This provides flexibility , cost efficiency and better security control . However, it can be complex to set up and manage and integrating the two systems can be challenging . Community Cloud A community cloud is shared by several organisations with similar needs , such as schools or government departments . The advantages include cost sharing , tailored security and easier collaboration between organisations . However, it may be less flexible than other cloud types and there can be concerns about data privacy and management between different organisations . Cloud Storage Types Cloud storage types are the different ways data can be organised , stored and accessed in the cloud , with each type designed for different uses and performance needs . File Storage File storage organises data in a hierarchical structure of folders and files, similar to how files are stored on a personal computer . It is easy to understand and use , making it ideal for shared drives and everyday file access due to its compatibility with many systems. However, it can become slow or inefficient with very large amounts of data and scaling up can be more difficult compared to other cloud storage types. Object Storage Object storage stores data as individual objects , each with metadata and a unique identifier , rather than in folders. It is designed for large amounts of unstructured data such as images , videos and backups . Its advantages include excellent scalability , high durability and cost-effectiveness for large datasets . However, it is not suitable for applications that require fast, frequent updates and it can be harder to work with compared to traditional file systems. Block Storage Elastic / Scalable Storage Block storage splits data into fixed-size blocks and stores them separately . It provides very fast access and high performance , making it suitable for systems that need quick read/write operations . The advantages are speed , reliability and flexibility . However, it is more complex to manage , can be expensive , and does not include built-in file organisation like file storage. Elastic storage automatically increases or decreases capacity based on demand . It is commonly used in cloud environments where storage needs change frequently . The main benefits are flexibility , cost efficiency ( only pay for what you use ) and no need to predict storage requirements in advance . However, costs can become unpredictable and it relies heavily on a stable internet connection and provider availability . Cloud-Based Database Services These are cloud services designed specifically to store and manage structured data using databases . They handle tasks such as backups , updates and scaling automatically . The advantages include ease of use , automatic maintenance , scalability and high availability . However, they can be costly over time , offer less control than self-managed databases and may raise concerns about data security and vendor lock-in . Q uesto's Q uestions 1.3 - Storage: 1. Choose the most storage type and explain your answer. [ 4 each ] a. A school wants a central place where all teachers can save and share files . b. A photographer needs to carry thousands of photos between clients. c. A bank needs extremely fast storage for critical systems . d. A company wants storage that automatically grows as it stores more data . e. A video streaming company needs to store millions of videos . 2. For each scenario , recommend a storage location and explain why. [ 4 each ] a. A hospital storing confidential patient records . b. A small business with a limited budget . c. A university working with several partner colleges . d. A company that wants to keep sensitive data private but also use cheaper cloud storage . 3. Give two advantages and two disadvantages for each cloud storage type (file storage , object storage , block storage , elastic / scalable storage, cloud-based database services . [4 each ] Every photo , video or file you upload to the cloud is often copied to multiple servers in different locations (this is called redundancy ). So if one server fails , your data can still be recovered . D id Y ou K now? 1.2 - Devices Topic List 2.1 - Data Formats & Types