Stakeholders — OCR A-Level Computer Science

Stakeholders are individuals, groups, or organisations that have an interest in the activities and decisions of a computer-based system or project. In the context of OCR A-Level Computer Science, understanding stakeholders is crucial for analysing how systems affect different parties and how their needs and concerns must be considered during system development. Stakeholders can include end users, clients, developers, project managers, investors, regulatory bodies, and even society at large. Each stakeholder group may have different objectives, such as usability, profitability, security, or legal compliance, which can sometimes conflict.

The study of stakeholders is integral to the systems development life cycle (SDLC) and the broader theme of legal, moral, ethical, and cultural issues in computing. For example, when developing a new healthcare app, stakeholders might include patients (who want privacy and ease of use), doctors (who need accurate data), hospital administrators (who focus on cost and efficiency), and regulators (who enforce data protection laws). Recognising these diverse perspectives helps students design systems that are not only technically sound but also socially responsible and legally compliant.

Mastering stakeholder analysis prepares students for exam questions that require them to evaluate the impact of technology on different groups, justify design decisions, and discuss ethical dilemmas. It also aligns with the OCR specification's emphasis on computational thinking and the ability to consider multiple viewpoints when solving problems. By the end of this topic, students should be able to identify stakeholders for a given scenario, analyse their interests, and propose how to balance conflicting needs.

• →Stakeholder identification: recognising all parties affected by a system, including direct users, indirect users, and external groups such as regulators or the public.
• →Stakeholder analysis: evaluating each stakeholder's power, interest, and influence to prioritise their requirements and manage conflicts.
• →Conflicts of interest: understanding that stakeholders may have opposing goals (e.g., cost vs. quality, privacy vs. functionality) and how to negotiate trade-offs.
• →Legal and ethical considerations: stakeholders' rights under laws like the Data Protection Act 2018 and the Computer Misuse Act 1990, and ethical frameworks such as the ACM Code of Ethics.
• →Impact assessment: evaluating how a system affects stakeholders socially, economically, and environmentally, often through techniques like stakeholder mapping or impact matrices.

• Identification of suitable stakeholders for the project.
• Description of stakeholders and their specific requirements.
• Explanation of how the solution is appropriate to the needs of the identified stakeholders.
• Clear link between stakeholder needs and the proposed computational solution.

• 💡Ensure stakeholders are clearly defined; use personas if necessary to add depth.
• 💡Explicitly link the features of your proposed solution to the requirements of the stakeholders identified.
• 💡Use the command words in the assessment criteria to guide the depth of your analysis.
• 💡When answering exam questions, always explicitly name specific stakeholder groups (e.g., 'patients', 'doctors', 'NHS managers') rather than using vague terms like 'users'. This shows precise understanding and gains marks for detail.
• 💡Use a structured approach: for any scenario, first list stakeholders, then for each, state their interest, potential conflict, and how you would address it. This mirrors the mark scheme for extended response questions.
• 💡Link stakeholder analysis to legal and ethical issues. For instance, if discussing data privacy, mention the Data Protection Act and how it protects stakeholders like customers. This demonstrates higher-level thinking.

• Failing to identify specific stakeholders, instead providing generic or vague groups.
• Neglecting to explain how the solution specifically addresses the needs of the identified stakeholders.
• Treating stakeholders as an afterthought rather than a core component of the analysis phase.
• Misconception: Stakeholders are only the people who use the system directly. Correction: Stakeholders include anyone affected by the system, such as investors, competitors, and society. For example, an e-commerce website affects delivery drivers and local shops, not just customers.
• Misconception: All stakeholders have equal influence. Correction: Stakeholders have varying levels of power and interest. A project manager may have high power but low interest, while end users may have low power but high interest. Prioritising requirements requires balancing these factors.
• Misconception: Stakeholder analysis is only done at the start of a project. Correction: Stakeholder needs and influence can change over time, so analysis should be revisited throughout the SDLC, especially during testing and deployment phases.