Types of Software and Development Methodologies - Worksheets, Questions and Revision

14 original exam-style questions - 4 pages of questions with a full mark scheme - free printable PDF.

Download PDF Jump to mark scheme (page 5)Read the revision guide

Next in this strand

Revision Library

revisionlibrary.co.uk

A-Level · Component 1: Computer Systems - Software and software development

A1.2 Types of Software and Development Methodologies

OCR H446 · Calculators not allowed · about 140 minutes

Total Marks

Name: _______________________________ Date: ____ / ____ / ______

Answer ALL questions. Show all your working.

Software can be classified into different types according to its purpose.

(a)State what is meant by the term 'system software'.(2)

(b)State three examples of system software.(3)

(c)Explain one function of an operating system that makes it an example of system software.(2)

(Total for Question 1 is 7 marks)

A company must decide whether to buy off-the-shelf software or commission bespoke (custom-written) software.

(a)State what is meant by the term 'bespoke software'.(2)

(b)State what is meant by the term 'off-the-shelf software'.(2)

(c)A regional hospital trust wants a new system to manage patient appointments across 12 sites, with several unusual workflow requirements that are not met by any existing product. Discuss whether the trust should choose off-the-shelf or bespoke software.(6)

(Total for Question 2 is 10 marks)

Software can also be classified by whether or not its source code is publicly available.

(a)State what is meant by the term 'open source software'.(2)

(b)State what is meant by the term 'closed source (proprietary) software'.(2)

(c)A small business is choosing a content management system for its website and is considering an open source option. Give two advantages and two disadvantages of using open source software in this context.(4)

(Total for Question 3 is 8 marks)

Utility software carries out specific maintenance tasks on a computer system.

(a)State what is meant by the term 'utility software'.(2)

(b)For each scenario below, identify the type of utility software that would be used.
i) Compressing a large video file before emailing it.
ii) Protecting a computer from malicious software downloaded from the internet.
iii) Reorganising fragmented files on a hard disk drive to improve access speed.
iv) Creating a copy of important files in case the originals are lost or damaged.(4)

(c)Explain why defragmentation utility software improves performance on a hard disk drive (HDD) but has little or no benefit on a solid-state drive (SSD).(3)

(Total for Question 4 is 9 marks)

The waterfall model is a traditional, linear approach to software development.

(a)List, in the correct order, the five stages of the waterfall model of software development.(5)

(b)State two characteristics of the waterfall model.(2)

(c)A software company is developing a system for a client whose requirements are likely to change significantly during development. Explain one disadvantage of using the waterfall model for this project.(3)

(Total for Question 5 is 10 marks)

Rapid Application Development (RAD) focuses on fast delivery through prototyping.

(a)State two characteristics of RAD.(2)

(b)Explain why RAD may not be suitable for a project where users are not available to give regular feedback.(3)

(c)Compare the use of prototyping in RAD with the waterfall model.(3)

(Total for Question 6 is 8 marks)

Agile methodologies are an alternative to traditional models such as waterfall.

(a)State three principles that underpin agile approaches to software development, as set out in the agile manifesto.(3)

(b)Explain two ways in which agile development handles changing requirements differently from the waterfall model.(4)

(c)A government department is planning a large IT project with a fixed contract value and a fixed delivery date set in law. Discuss whether an agile methodology would be appropriate for this project.(6)

(Total for Question 7 is 13 marks)

Scrum is a popular framework for implementing agile software development.

(a)State three roles defined in the Scrum framework.(3)

(b)Define the term 'sprint' as used in Scrum.(2)

(c)Explain the purpose of a daily stand-up (daily scrum) meeting.(2)

(d)Explain the purpose of a sprint retrospective.(2)

(Total for Question 8 is 9 marks)

Extreme Programming (XP) is an agile methodology that emphasises technical practices.

(a)State three practices associated with Extreme Programming.(3)

(b)Explain one benefit of pair programming.(3)

(c)Explain one benefit of using continuous integration in a development team.(3)

(Total for Question 9 is 9 marks)

The spiral model combines iterative development with a strong focus on risk management.

(a)Describe the four phases carried out in each loop (cycle) of the spiral model.(4)

(b)Explain why the spiral model is well suited to large, high-risk projects.(3)

(c)Explain one disadvantage of using the spiral model.(2)

(Total for Question 10 is 9 marks)

A start-up company is developing a mobile app for online banking. The app must be launched within 4 months to meet a marketing deadline, but the founders expect features to change as user feedback comes in after each release. Security and regulatory compliance are critical.

(a)Recommend and justify a suitable software development methodology for this project.(8)

(Total for Question 11 is 8 marks)

A small independent bookshop wants a new till (point-of-sale) and stock management system. The owner has a very limited budget and standard requirements similar to many other small shops, but wants some control over any future changes to the software.

(a)Discuss which combination of software type (bespoke vs off-the-shelf) and licensing model (open source vs closed source) would best meet the bookshop's needs, and justify your recommendation.(8)

(Total for Question 12 is 8 marks)

Evaluate the extent to which agile methodologies have made the waterfall model obsolete for modern software development.

(a)Evaluate the extent to which agile methodologies have made the waterfall model obsolete for modern software development.(9)

(Total for Question 13 is 9 marks)

A university is replacing its student records system, which is used by over 20,000 students and staff and must comply with strict data protection law. Errors in the new system could result in incorrect exam results being issued. The university has stated that it wants to combine techniques from more than one development methodology.

(a)Suggest one reason why a purely agile approach might be considered too risky for this project.(3)

(b)Suggest one reason why a purely waterfall approach might also be unsuitable.(3)

(c)Describe a hybrid approach the university could use, combining features of two methodologies, and explain how it addresses the risks identified in (a) and (b).(6)

(Total for Question 14 is 12 marks)

Mark scheme · A1.2 Types of Software and Development Methodologies

Question 1

(a) B1 Software that manages/controls the hardware and resources of a computer system (oe)
(a) B1 ...and provides a platform that allows application software to run (oe)
(a) Answer: System software is software that manages and controls a computer's hardware and resources, providing a platform on which application software can run.
(b) B1 Any one from: operating system / device driver / BIOS (firmware) / translator (compiler, interpreter, assembler or linker), 1 mark each up to 3
(b) Answer: Operating system, device driver, BIOS (firmware); (compiler/interpreter/assembler/linker also acceptable).
(c) B1 Identifies a valid OS function, e.g. memory management / process management / file management / peripheral (device) management / user interface (oe)
(c) B1 Explains how this manages hardware/resources on behalf of application software/users, e.g. allocates and deallocates RAM to running processes so each has the space it needs and programs do not conflict (oe, ft from function named)
(c) Answer: Memory management: the OS allocates and deallocates RAM to running processes, ensuring each program has the memory it needs and preventing conflicts between programs.

Question 2

(a) B1 Software written specifically for a single customer/organisation (oe)
(a) B1 ...to meet their exact requirements/specification (oe)
(a) Answer: Bespoke software is software written specifically for a single customer or organisation to meet its exact requirements.
(b) B1 Software that already exists / has been pre-written (oe)
(b) B1 ...and is available for anyone to buy/use, usually without modification (oe)
(b) Answer: Off-the-shelf software is pre-written software that is already available to buy and use, generally without modification, by any customer.
(c) L3 (5-6): A well-balanced discussion that considers both bespoke and off-the-shelf options with clear application to the hospital scenario (unusual workflows, patient safety, multi-site use, budget, timescale) and reaches a reasoned, justified conclusion. Technical terms used accurately throughout.
(c) L2 (3-4): Some discussion of both options with partial application to the scenario; points may be generic or only loosely linked to the hospital's specific needs. A conclusion may be present but not fully justified.
(c) L1 (1-2): Basic, mostly one-sided or generic statements about bespoke/off-the-shelf software with little or no application to the scenario given.
(c) L0 (0): No creditable content.
(c) Answer: Model answer: bespoke software is likely the better recommendation given the unusual, safety-relevant workflows across 12 sites that no existing package supports, despite the higher cost and longer development time; off-the-shelf remains a valid alternative only if it can be customised to cover the unusual requirements within budget.

Question 3

(a) B1 Source code is made publicly available/can be viewed by anyone (oe)
(a) B1 ...and can usually be modified and redistributed freely (often at no cost) (oe)
(a) Answer: Open source software is software whose source code is publicly available so that it can be viewed, modified and redistributed freely.
(b) B1 Source code is kept private/hidden by the owner/developer (oe)
(b) B1 ...and users cannot legally view, modify or redistribute it without permission/a licence (oe)
(b) Answer: Closed source (proprietary) software is software whose source code is kept private by the owner, and cannot legally be viewed, modified or redistributed by users without permission.
(c) B1 Advantage 1: any one from - free/low cost to acquire; can be customised to fit the business's needs; large community support/development; code can be inspected for security flaws; no vendor lock-in
(c) B1 Advantage 2: a second distinct point from the list above
(c) B1 Disadvantage 1: any one from - may lack official/guaranteed technical support; may require in-house technical expertise to customise/maintain; documentation may be poor or inconsistent; security vulnerabilities may be publicly known before being patched
(c) B1 Disadvantage 2: a second distinct point from the list above
(c) Answer: Advantages: low/no cost; can be freely customised to the business's needs. Disadvantages: no guaranteed official support; may need in-house technical skill to maintain.

Question 4

(a) B1 Software designed to help maintain, configure, analyse or optimise a computer system (oe)
(a) B1 ...it carries out a single specific task, rather than a general task requested by the user (oe)
(a) Answer: Utility software is software designed to carry out a specific task that helps maintain, configure or optimise a computer system.
(b) B1 i) Compression/archiving utility (oe)
(b) B1 ii) Anti-virus/anti-malware utility (oe)
(b) B1 iii) Defragmentation utility (oe)
(b) B1 iv) Backup utility (oe)
(b) Answer: i) Compression utility ii) Anti-virus/anti-malware utility iii) Defragmentation utility iv) Backup utility
(c) B1 HDDs use a moving read/write head over spinning platters, so fragmented data (split into non-contiguous blocks) increases seek/access time (oe)
(c) B1 Defragmentation reorders data into contiguous blocks, reducing head movement and so reducing access time (oe)
(c) B1 SSDs have no moving parts and can access any memory location in (near) constant time, so fragmentation does not increase access time / reorganising data brings little benefit and may cause unnecessary wear (oe)
(c) Answer: HDDs suffer from fragmentation because the read/write head must physically move further to reach scattered data, increasing seek time; defragmentation groups files into contiguous blocks to reduce this. SSDs have no moving head and access any location in roughly the same time, so fragmentation barely affects performance and defragmenting can add unnecessary wear.

Question 5

(a) B1 1. Requirements analysis/gathering
(a) B1 2. (System) design
(a) B1 3. Implementation (coding)
(a) B1 4. Testing (verification)
(a) B1 5. Maintenance (deployment/evaluation); accept equivalent stage names, but marks lost if order is incorrect (award marks for stages named correctly regardless of exact wording, ft position)
(a) Answer: Requirements analysis, design, implementation, testing, maintenance.
(b) B1 Any one from: each stage must be completed before the next begins; stages do not overlap; requires full documentation at each stage; no return to a previous stage once it is complete (without formal change control), 1 mark each up to 2
(b) Answer: Each stage must be finished before the next stage starts; there is normally no return to an earlier, completed stage.
(c) B1 Waterfall fixes requirements at the start and does not allow easy return to an earlier stage (oe)
(c) B1 If requirements change during development, this leads to costly and time-consuming rework, since design/implementation/testing would need to be redone (oe, ft)
(c) B1 The client may end up receiving a system that no longer meets their (changed) needs, or the project is delayed/over budget as a result (oe, ft)
(c) Answer: Because waterfall fixes requirements at the outset and does not easily allow a return to an earlier stage, any changes to requirements during development force costly and time-consuming rework of design, implementation and testing, risking delays, extra cost, or a final system that no longer matches the client's actual needs.

Question 6

(a) B1 Any one from: heavy/repeated use of prototyping, refined based on user feedback; short development time/fast delivery; makes use of reusable components/tools; requires active, continuous user involvement, 1 mark each up to 2
(a) Answer: RAD makes heavy use of prototyping that is refined through repeated user feedback, and aims for fast delivery of a working system.
(b) B1 RAD depends on regular/continuous input and feedback from users to refine prototypes at each stage (oe)
(b) B1 Without this feedback, prototypes cannot be validated or improved against real user needs (oe, ft)
(b) B1 This can lead to a final system that does not meet requirements, or to delays while the team waits for input, undermining the speed that is RAD's main benefit (oe, ft)
(b) Answer: RAD relies on continuous user feedback to refine each prototype; without available users, prototypes cannot be validated against real needs, risking a final system that does not meet requirements or delays that remove RAD's main speed advantage.
(c) B1 RAD uses prototyping throughout/repeatedly, central to the process, refined via user feedback across the whole project (oe)
(c) B1 Waterfall does not typically use prototyping, or uses it (if at all) only briefly at the start, since each stage is completed once, in order, before moving on (oe)
(c) B1 Comparative point: RAD can therefore adapt to user feedback more easily/quickly than waterfall, which is more rigid once requirements/design are signed off (oe)
(c) Answer: RAD uses prototyping repeatedly and continuously throughout the project, refined by ongoing user feedback, whereas waterfall makes little or no use of prototyping since each stage is completed once before moving to the next; as a result RAD can adapt to user feedback far more easily than the more rigid waterfall model.

Question 7

(a) B1 Any one from: individuals and interactions valued over processes and tools; working software valued over comprehensive documentation; customer collaboration valued over contract negotiation; responding to change valued over following a fixed plan; iterative/incremental delivery in short cycles (sprints); continuous customer/user feedback, 1 mark each up to 3
(a) Answer: e.g. working software is valued over comprehensive documentation; customer collaboration is valued over contract negotiation; responding to change is valued over following a fixed plan.
(b) B1 Point 1: agile develops software in short iterations/sprints, each delivering a working increment (oe)
(b) B1 Development of point 1: so requirements can be reviewed and adjusted between sprints without restarting the whole project, unlike waterfall (oe, ft)
(b) B1 Point 2: agile involves continuous/frequent feedback from the customer/user throughout development (oe)
(b) B1 Development of point 2: so changes can be incorporated as they arise, rather than (as in waterfall) only being possible before design begins (oe, ft)
(b) Answer: Agile develops software in short sprints, each producing a working increment, so requirements can be reviewed and changed between sprints without restarting the project; agile also involves continuous customer feedback throughout, so changes can be incorporated as they arise, unlike waterfall where requirements are effectively fixed once the design stage begins.
(c) L3 (5-6): A well-balanced discussion that applies agile's characteristics directly to the fixed-price, fixed-deadline, legally constrained context, weighing genuine advantages and disadvantages, and reaching a reasoned, justified conclusion.
(c) L2 (3-4): Some balanced discussion of agile's suitability, but with limited application to the fixed contract/legal deadline context; conclusion may be weak or generic.
(c) L1 (1-2): Basic or one-sided statements about agile with little or no application to the scenario.
(c) L0 (0): No creditable content.
(c) Answer: Model answer: agile could be made to work within a fixed contract by time-boxing sprints and letting scope flex (delivering the highest-priority features first to meet the legal deadline), but its evolving scope sits awkwardly with a fixed-price contract and heavy documentation/audit requirements, so a hybrid approach (e.g. fixed requirements and budget agreed upfront, delivered via agile sprints) may be the most balanced recommendation.

Question 8

(a) B1 Product Owner
(a) B1 Scrum Master
(a) B1 Development team (member(s))
(a) Answer: Product Owner, Scrum Master, Development team.
(b) B1 A fixed, short time period (typically 1 to 4 weeks) (oe)
(b) B1 ...during which a specific set of work/features is completed, producing a potentially shippable increment (oe)
(b) Answer: A sprint is a fixed, short period of time (typically 1 to 4 weeks) during which a specific set of work is completed, producing a potentially shippable increment of the product.
(c) B1 A short (e.g. 15 minute) meeting held each day where team members report progress, plans and blockers (oe)
(c) B1 ...so the team can quickly identify and address problems and coordinate work, keeping everyone up to date (oe)
(c) Answer: The daily stand-up is a short daily meeting where each team member reports what they have done, what they plan to do, and any blockers, so problems can be identified quickly and the team's work stays coordinated.
(d) B1 A meeting held at the end of each sprint where the team reflects on how the sprint went (oe)
(d) B1 ...to identify what worked well and what could be improved, so future sprints can be run more effectively (continuous improvement) (oe)
(d) Answer: The sprint retrospective is a meeting held at the end of each sprint where the team reflects on what went well and what could be improved, so future sprints can be run more effectively.

Question 9

(a) B1 Any one from: pair programming; test-driven development (writing tests before code); continuous integration; refactoring; collective code ownership; small/frequent releases; on-site customer; simple design; coding standards, 1 mark each up to 3
(a) Answer: e.g. pair programming, test-driven development, continuous integration.
(b) B1 Description: two developers work together at one workstation, one writing code (driver) while the other reviews it in real time (navigator) (oe)
(b) B1 Errors/bugs are spotted and corrected earlier, as code is reviewed as it is written (oe)
(b) B1 Knowledge of the codebase is shared between developers, reducing dependency on a single person and aiding training (oe; any one further distinct benefit acceptable)
(b) Answer: In pair programming, two developers share one workstation, with one writing code (driver) and the other reviewing it as it is written (navigator). Errors are caught earlier because the code is reviewed continuously, and knowledge of the codebase is shared between developers, reducing reliance on any one individual.
(c) B1 Description: code changes are merged into a shared repository and automatically built/tested frequently, e.g. several times a day (oe)
(c) B1 Integration problems/conflicts between different developers' code are identified quickly, while they are small and easy to fix (oe)
(c) B1 This reduces the risk of large, difficult-to-diagnose integration problems occurring near the end of the project (oe)
(c) Answer: Continuous integration merges developers' code into a shared repository and automatically builds/tests it frequently. This means integration problems between different developers' code are found quickly while they are small, reducing the risk of large, difficult integration problems appearing near the end of the project.

Question 10

(a) B1 1. Determine objectives, alternatives and constraints for that iteration (oe)
(a) B1 2. Identify and evaluate/resolve risks (risk analysis), often using prototyping (oe)
(a) B1 3. Develop and test/verify the next level (increment) of the product for that iteration (oe)
(a) B1 4. Review the iteration and plan the next loop (oe)
(a) Answer: Each loop: (1) determine objectives, alternatives and constraints; (2) identify and analyse/resolve risks, often via prototyping; (3) develop and test the next increment of the product; (4) review the results and plan the next loop.
(b) B1 Each loop/iteration includes an explicit risk analysis phase, often using prototypes (oe)
(b) B1 This allows risks to be identified and addressed early, before large amounts of time/money have been committed (oe, ft)
(b) B1 Reducing the chance of costly failure later in a large, unfamiliar or technically complex project (oe, ft)
(b) Answer: Because every loop of the spiral includes a dedicated risk-analysis phase, often supported by prototyping, risks are identified and dealt with early, before large amounts of time and money have been committed, reducing the chance of costly failure later in a large or technically complex project.
(c) B1 Requires specialist risk-assessment expertise/skills to be carried out properly (oe)
(c) B1 It can be more expensive and time-consuming than simpler models due to the repeated risk analysis and prototyping, which may not suit smaller or low-risk projects (oe; any distinct valid disadvantage acceptable)
(c) Answer: The spiral model requires specialist risk-assessment expertise and repeated prototyping/analysis in every loop, making it more expensive and time-consuming than simpler models, which is not justified for smaller or low-risk projects.

Question 11

(a) L4 (7-8): A clear, justified recommendation that explicitly applies methodology characteristics to multiple scenario constraints (tight deadline, evolving features, security/regulatory needs), with balanced consideration of at least one alternative and a coherent, well-structured argument.
(a) L3 (5-6): A reasonable recommendation with justification linked to most scenario factors, but with less developed evaluation of alternatives.
(a) L2 (3-4): Some relevant points made with partial application to the scenario; justification is limited or one-sided.
(a) L1 (1-2): Basic or generic statements about a methodology with little or no application to the scenario.
(a) L0 (0): No creditable content.
(a) Answer: Model answer: recommend an agile (e.g. Scrum) approach for the evolving features and tight 4 month deadline, combined with a fixed, non-negotiable security/regulatory specification validated at each sprint (a hybrid model), since pure waterfall would not meet the deadline or accommodate expected changes, and pure agile alone risks under-specifying compliance requirements.

Question 12

(a) L4 (7-8): A clear, well-justified recommendation combining a software type and licensing model, with detailed application to the bookshop's budget, standard requirements and desire for future control, and balanced consideration of trade-offs.
(a) L3 (5-6): A reasonable recommendation linked to most scenario factors, with some consideration of trade-offs, but less fully developed.
(a) L2 (3-4): Some relevant points with partial application to the scenario; justification limited or one-sided.
(a) L1 (1-2): Basic or generic statements about software types/licensing with little or no application to the scenario.
(a) L0 (0): No creditable content.
(a) Answer: Model answer: recommend an open source, off-the-shelf point-of-sale package, since off-the-shelf suits the limited budget and standard requirements, while the open source licence gives the owner some ability to adapt the software in future without being locked to one vendor; the main trade-off is reduced guaranteed technical support compared with a closed-source commercial product.

Question 13

(a) L3 (7-9): A sustained, well-evidenced evaluation considering multiple project contexts (e.g. safety-critical/regulated systems vs consumer apps), with a balanced argument on both sides and a clear, well-supported overall judgement. Technical vocabulary used accurately throughout.
(a) L2 (4-6): Some evaluation with valid points on both sides, applied to at least one context; an overall judgement is present but less developed or not fully consistent.
(a) L1 (1-3): Mostly one-sided or a generic list of features of agile and/or waterfall with little evaluative comment; a weak or absent judgement.
(a) L0 (0): No creditable content.
(a) Answer: Model answer: agile has largely displaced waterfall for consumer/web/app development where requirements evolve and fast, iterative feedback is valuable, but waterfall (or waterfall-like staged approaches) remains appropriate and often required for safety-critical, heavily regulated or fixed-price contractual projects with well-understood, stable requirements; therefore waterfall is not obsolete overall, and the appropriate methodology depends on the nature of the specific project.

Question 14

(a) B1 Agile does not require a full specification/documentation to be produced upfront (oe)
(a) B1 For a system handling sensitive personal data and exam results under strict legal (data protection/compliance) requirements, incomplete upfront analysis could result in security or compliance issues (or errors) being missed (oe, ft)
(a) B1 Agile's flexible/evolving scope makes it harder to guarantee, in advance, that all legal/compliance requirements will definitely be met by a fixed deadline (oe; any distinct valid risk acceptable)
(a) Answer: Agile does not require a complete specification to be documented upfront; for a system with strict data-protection and exam-accuracy requirements, this could allow compliance or security issues to be missed until late in development, and agile's evolving scope makes it hard to guarantee in advance that all legal requirements will be met.
(b) B1 Waterfall fixes requirements early and does not allow easy return to an earlier stage (oe)
(b) B1 For a large, complex system like this, it is likely that not all requirements can be foreseen at the start, so errors/omissions in the specification may not be discovered until late testing, where they are costly to fix (oe, ft)
(b) B1 Stakeholders (students/staff) get no working system to give feedback on until very late in the project, increasing the risk of a mismatch with actual needs (oe; any distinct valid risk acceptable)
(b) Answer: Waterfall fixes requirements early with no easy return to a previous stage; for such a large, complex system it is unlikely all requirements can be foreseen at the start, so errors may only be found in late testing, where they are expensive to fix, and stakeholders get no working system to react to until very late in the project.
(c) L3 (5-6): A coherent, plausible hybrid approach is described with clear features drawn from two named methodologies, and the answer clearly explains how it mitigates both the agile-related risk from (a) and the waterfall-related risk from (b).
(c) L2 (3-4): A hybrid approach is described with some relevant features from two methodologies, with partial explanation of how it addresses the risks in (a) and/or (b).
(c) L1 (1-2): A vague or generic reference to combining methodologies, with little detail or explanation of how the risks are addressed.
(c) L0 (0): No creditable content.
(c) Answer: Model answer: use a waterfall-style stage first to fix and formally document the legal/data-protection/exam-accuracy requirements, then build the system through agile sprints within that fixed specification, giving stakeholders working increments to review throughout. This fixes compliance requirements upfront (addressing the agile risk from (a)) while still giving early, iterative feedback (addressing the waterfall risk from (b)).

Question 1

7 marks

Your answer

Question 2

10 marks

Your answer

Question 3

8 marks

Your answer

Question 4

9 marks

Your answer

Question 5

10 marks

Your answer

Question 6

8 marks

Your answer

Question 7

13 marks

Your answer

Question 8

9 marks

Your answer

Question 9

9 marks

Your answer

Question 10

9 marks

Your answer

Question 11

8 marks

Did your answer earn the marks?

Question 12

8 marks

Did your answer earn the marks?

Question 13

9 marks

Did your answer earn the marks?

Question 14

12 marks

Your answer

Mark my answers