Identifying requirements — OCR GCSE Design and Technology

Identifying requirements is the foundational stage of the design process in Design and Technology. It involves systematically determining what a design must achieve by analysing the needs of users, stakeholders, and the context of use. This step ensures that the final product is fit for purpose, meets user expectations, and complies with relevant standards. Without a clear set of requirements, designs risk being impractical, unsafe, or commercially unviable.

In the OCR GCSE course, this topic covers how to gather and interpret data from primary and secondary sources, including user interviews, surveys, market research, and ergonomic data. You will learn to distinguish between design specifications (what the product must do) and manufacturing specifications (how it will be made). Mastering this skill is critical for scoring high marks in the NEA (Non-Exam Assessment) where you must justify your design decisions based on identified requirements.

Identifying requirements also connects to broader themes like sustainability, inclusivity, and technological innovation. For example, requirements might include using recyclable materials or ensuring accessibility for users with disabilities. By the end of this topic, you should be able to produce a detailed design brief and specification that guides all subsequent stages of designing and making.

• →User needs and wants: Differentiate between what users need (essential functions) and what they want (desirable features). Use tools like questionnaires and observation to gather this data.
• →Primary vs secondary research: Primary research involves collecting new data (e.g., interviews, experiments), while secondary research uses existing data (e.g., market reports, online databases). Both are essential for a comprehensive requirement set.
• →Design specification: A formal document listing measurable criteria (e.g., dimensions, weight, cost, materials) that the final product must meet. It should be SMART (Specific, Measurable, Achievable, Relevant, Time-bound).
• →Ergonomics and anthropometrics: Understanding human body measurements and how people interact with products. Requirements often include comfort, safety, and ease of use based on anthropometric data.
• →Sustainability and ethics: Modern designs must consider environmental impact (e.g., carbon footprint, recyclability) and ethical factors (e.g., fair trade materials, avoiding planned obsolescence).

• Identification of challenging problems and opportunities within a context
• Clear relevance of the design brief to the context
• Identification of primary users and other stakeholders
• Objective consideration of stakeholder needs and wants
• Comprehensive and relevant information/sources of inspiration identified
• Accurate and detailed technical specification that communicates requirements to a third party

• 💡Ensure investigations are comprehensive and directly inform the design process
• 💡Use primary and secondary data to justify the identification of needs and wants
• 💡Clearly link the design brief to the contextual challenge provided by OCR
• 💡Ensure the technical specification is detailed enough for a third party to understand the requirements
• 💡Reflect on identified issues throughout the project
• 💡Tip 1: Always link your requirements directly to your research. For example, if a user survey shows that 80% of users want a lightweight product, state that as a requirement and cite the survey. This shows clear evidence-based thinking.
• 💡Tip 2: Use technical vocabulary correctly. Terms like 'anthropometric data', 'ergonomic', 'life cycle assessment', and 'user-centred design' demonstrate depth of knowledge. Define them briefly in your NEA.
• 💡Tip 3: Include conflicting requirements and explain how you would resolve them. For instance, 'lightweight' vs 'durable' – you might choose a specific material that balances both. Examiners love seeing trade-off analysis.

• Superficial investigations that fail to identify meaningful problems or opportunities
• Design briefs that lack relevance to the context or fail to identify stakeholders
• Inaccurate or incomplete technical specifications
• Failure to consider the needs of stakeholders beyond the primary user
• Lack of evidence to support the design process
• Misconception: 'Requirements are just a list of features I want to include.' Correction: Requirements must be based on evidence from research, not personal preference. They should reflect real user needs and constraints.
• Misconception: 'I can skip identifying requirements if I have a good idea.' Correction: Even the best ideas need validation. Skipping this step often leads to designs that fail in the market or do not meet user expectations.
• Misconception: 'All requirements are equally important.' Correction: Requirements should be prioritised using tools like the MoSCoW method (Must have, Should have, Could have, Won't have). This helps focus on critical features first.