Design Engineering (H404) - 1. Identifying requirements - 1.2 What can be learnt by undertaking stakeholder analysis? — OCR A-Level Design and Technology
Test yourself on Design Engineering (H404) - 1. Identifying requirements - 1.2 What can be learnt by undertaking stakeholder analysis? with OCR A-Level practice questions.
7 days Premium · Then free forever · No card, no charge
Your focus
- a. Demonstrate an understanding of methods used for investigating stakeholder requirements, such as:
Design Engineering (H404) - 1. Identifying requirements - 1.2 What can be learnt by undertaking stakeholder analysis? exam tips
Quick Revision Summary (Key Takeaway)
Stakeholder analysis systematically identifies all individuals, groups, or organisations invested in an engineering product to uncover competing needs, functional requirements, and constraints. By mapping stakeholder power, interest, and operational priorities, engineers formulate robust, user-centred design specifications that mitigate project risks.
Topic Overview
Stakeholder analysis in OCR A-Level Design Engineering explores how identifying and interrogating the needs of all invested parties informs engineering decisions. It moves beyond basic consumer profiling to encompass primary operators, secondary service personnel, production engineers, supply chain logistics, and statutory regulatory bodies.
Understanding stakeholder interactions allows engineers to discover latent functional requirements, navigate conflicting design constraints, and establish clear priorities within the Product Design Specification (PDS). This analytical foundation directly reduces project risk, product recall rates, and lifecycle costs.
Key Concepts
- →Stakeholder Classification: Differentiating between primary users (hands-on operators), secondary users (installers, maintenance teams), and tertiary entities (legislators, recyclers, community).
- →Mendelow's Power-Interest Matrix: Prioritising stakeholder influence to balance high-leverage regulatory constraints against user interface desires.
- →Requirement Conflict Mapping: Identifying direct clashes between usability, cost, manufacturability, safety, and sustainability early in the design cycle.
- →PDS Translation: Converting qualitative stakeholder desires into quantifiable, testable engineering performance metrics.
Examiner Tips
- 💡Avoid generic terms like 'cheap' or 'strong'; state exact stakeholder needs using technical metrics, such as 'production manager requires unit assembly time under 120 seconds using automated visual inspection'.
- 💡When asked about conflicts, explicitly use the phrase 'competing constraints' and illustrate how an engineering compromise is reached using standard technical solutions (e.g. snap fits vs screw fasteners for disassembly).
Common Mistakes
- Assuming the customer and the end-user are always the same entity (e.g. in assistive healthcare, the NHS trust is the customer, but the patient and nurse are the distinct users with conflicting ergonomic and sanitisation needs).
- Believing stakeholder analysis is completed only at the project start; in professional practice, it is an iterative tool revisited at every engineering stage gate.
Revision Plan
- 1Day 1-2: Review core stakeholder categories (Primary, Secondary, Tertiary) and practice categorising them across 3 varied engineering products (e.g. train door mechanism, hospital ventilator, smart energy meter).
- 2Day 3-4: Master Mendelow's Power-Interest Matrix; practice plotting at least 5 stakeholders for an infrastructure project and justify their quadrant placements.
- 3Day 5-6: Practise past paper questions focusing on stakeholder conflicts and how technical compromises are reflected in a formal PDS.
- 4Day 7: Complete timed active recall flashcards on command words and mark scheme expectations for 'Analyse' and 'Evaluate' questions.
Exam Question Types
- 📋Short-answer identification: Naming distinct stakeholders and their specific technical requirements for an engineered product (2-4 marks).
- 📋Structured conflict analysis: Explaining how two competing stakeholder needs generate technical challenges and proposing an engineering resolution (6 marks).
- 📋Extended evaluation: Assessing the effectiveness of stakeholder mapping matrices in risk mitigation and requirements management (9-12 marks).
Command Word Expectations (OCR)
Deconstruct the stakeholder needs into separate elements, examining how each distinct requirement impacts the product's engineering design and detailing the relationship or conflicts between them.
Weigh up the validity, relative priority, and limitations of different stakeholder claims or analysis tools, concluding with a fully justified engineering judgment.
Set out the causes, reasons, or mechanisms clearly, showing how a specific stakeholder need directly influences a concrete feature in the final specification.
How Students Lose Marks (Examiner Pitfalls)
Step-by-Step Worked Solutions
Question: An engineering firm is designing a public-access automated external defibrillator (AED) enclosure. Analyse the requirements of two distinct stakeholders and explain how a conflict between their needs must be resolved in the design specification. [6 marks]
- 1.Step 1: Identify two distinct stakeholders with divergent priorities (e.g. an untrained bystander/first-aider and a municipal maintenance technician).
- 2.Step 2: Detail the specific functional requirements of Stakeholder 1 (Bystander requires instantaneous, intuitive emergency access, high visibility, and clear pictorial instructions under stress).
- 3.Step 3: Detail the specific functional requirements of Stakeholder 2 (Maintenance technician requires weatherproofing, vandal resistance, secure access for battery testing, and low-cost component servicing).
- 4.Step 4: Identify the direct engineering conflict (immediate tool-free access vs. security, weather sealing, and anti-tamper mechanisms).
- 5.Step 5: Formulate a balanced engineering resolution suitable for the PDS (e.g. a shear-pin plastic break-seal or single-action emergency latch that triggers an audible local alarm while maintaining an IP66 silicone seal, paired with an RFID service override for technicians).
Question: Evaluate the use of a Power-Interest Matrix (Mendelow's Matrix) when establishing requirements for an electric vehicle (EV) roadside charging station. [6 marks]
- 1.Step 1: Define the quadrants of the Power-Interest Matrix ('Manage Closely', 'Keep Satisfied', 'Keep Informed', 'Monitor').
- 2.Step 2: Assign specific stakeholders to key quadrants (e.g. National Grid / DNO in 'Manage Closely'; Local residents in 'Keep Informed'; EV fleet drivers in 'Keep Satisfied').
- 3.Step 3: Analyse how this categorisation informs design priorities (e.g. grid connection limits power draw to 150 kW and requires harmonic filtering, while EV drivers demand contactless payment and ergonomic cable weight under 4 kg).
- 4.Step 4: Evaluate limitations of the matrix (it offers a static snapshot that overlooks shifting dynamics during public consultations or regulatory changes).