System design
System design involves using tools like DFDs, flowcharts, and ERDs to model business systems. Learners must be able to design inputs, outputs, and produce a documented prototype.
Assessment criteria
Topic Overview
The Cambridge OCR Level 3 Cambridge Technical Diploma in IT is a vocationally-related qualification designed to equip students with practical IT skills and theoretical knowledge for the modern workplace. It covers a broad range of topics including computer systems, networking, cybersecurity, database design, web development, and project management. This diploma is equivalent to two A-Levels and provides a strong foundation for university study or direct entry into IT roles such as IT support technician, network administrator, or web developer.
The qualification is structured around mandatory units that build core competencies, such as 'Fundamentals of IT', 'Global Information', and 'Project Management', alongside optional units that allow specialisation in areas like 'Cyber Security', 'Computer Networks', or 'Website Development'. Students are assessed through a mix of externally examined units and internally assessed coursework, which mirrors real-world IT tasks. This blend ensures you not only understand theory but can apply it practically, making you job-ready from day one.
In the wider context of Computer Science, this diploma emphasises the application of technology in business and society. Unlike pure A-Level Computer Science, which focuses heavily on algorithms and programming theory, the Cambridge Technical Diploma balances technical skills with business awareness. You'll learn how IT systems support organisational goals, how to manage data securely, and how to communicate technical solutions to non-technical stakeholders. This makes it an excellent choice if you're interested in the operational and strategic side of IT.
Key Concepts
Core ideas you must understand for this topic
- →Computer hardware components: CPU, memory (RAM/ROM), storage devices, and input/output peripherals, and how they interact via the system bus.
- →Networking fundamentals: LAN vs WAN, IP addressing, subnetting, protocols (TCP/IP, HTTP, FTP), and network topologies (star, mesh, bus).
- →Database design: Normalisation (1NF, 2NF, 3NF), entity-relationship diagrams (ERDs), SQL queries (SELECT, INSERT, UPDATE, DELETE), and data integrity.
- →Cybersecurity principles: CIA triad (Confidentiality, Integrity, Availability), types of threats (malware, phishing, DDoS), and mitigation strategies (firewalls, encryption, access controls).
- →Project management methodologies: Waterfall vs Agile, Gantt charts, risk assessment, and the project life cycle (initiation, planning, execution, closure).
Learning Objectives
What you need to know and understand
- Understand how system design tools are used in a business system development, Be able to use system design tools in a business system, Be able to design system inputs and outputs, Be able to produce a documented prototype for a specified system
- Explain the purpose and use of system design tools in business system development
- Apply appropriate system design tools to model a given business system
- Design system inputs and outputs that meet specified user and business requirements
- Produce a documented prototype for a specified system, including appropriate annotations and user guidance
- Understand how system design tools are used in a business system development, Be able to use system design tools in a business system, Be able to design system inputs and outputs, Be able to produce a documented prototype for a specified system
- Explain the purpose and use of system design tools in business system development
- Select appropriate system design tools for a given business scenario
- Construct data flow diagrams (DFDs) to represent system processes
- Design user inputs and outputs that meet business requirements
- Produce a documented prototype for a specified system
- Evaluate the effectiveness of a prototype in meeting user needs
- Understand how system design tools are used in a business system development, Be able to use system design tools in a business system, Be able to design system inputs and outputs, Be able to produce a documented prototype for a specified system
Assessment Criteria
Key criteria assessors look for in your portfolio
- Correctly uses system design tools such as DFDs and flowcharts.
- Designs inputs and outputs that meet user requirements.
- Produces a documented prototype with clear annotations.
- Demonstrates understanding of system development lifecycle.
- Applies appropriate validation and verification techniques.
- Award credit for demonstrating understanding of at least two different system design tools (e.g., DFDs, flowcharts, UML diagrams) and their specific uses.
- Award credit for correctly applying a design tool to represent the flow of data or processes in a business system, with accurate notation and labelling.
- Award credit for designing inputs and outputs that are clear, user-friendly, and include appropriate validation and data formats.
- Award credit for producing a prototype that is functional or interactive, and includes documentation such as user instructions, design notes, and test results.
- Selects appropriate system design tools for a given scenario.
- Creates accurate data flow diagrams and flowcharts.
- Designs system inputs and outputs that meet user requirements.
- Produces a documented prototype with clear annotations.
- Explains how design tools aid business system development.
- Award credit for correctly identifying and describing the purpose of at least three system design tools (e.g., DFD, flowchart, system flowchart).
- Award credit for selecting tools that are appropriate to the scenario and justifying their use.
- Award credit for DFDs that include correct symbols, external entities, processes, data stores, and data flows.
- Award credit for input designs that include appropriate data validation and user-friendly layout.
- Award credit for output designs that present information clearly and meet user requirements.
- Award credit for a prototype that is documented with annotations, user guide, and technical details.
- Award credit for evaluating the prototype against user requirements and suggesting improvements.
- Explain how system design tools support development.
- Use appropriate tools to design system inputs and outputs.
- Produce a documented prototype for a specified system.
Assessment Guidance
Guidance for achieving higher grades
- 💡Practice drawing DFDs and flowcharts from given scenarios.
- 💡Always label inputs, outputs, and processes clearly.
- 💡Include a brief justification for design choices.
- 💡Familiarise yourself with a range of system design tools and practise drawing them accurately, paying attention to notation and conventions.
- 💡When designing inputs and outputs, always consider the end-user and the business context; justify your choices.
- 💡For the prototype, ensure it is clearly linked to your design documents and that you can explain how it meets the requirements.
- 💡Use appropriate terminology throughout your work to demonstrate your understanding of system design concepts.
- 💡Learn standard symbols for DFDs and flowcharts.
- 💡Always link design decisions to user requirements.
- 💡Include test data in prototype documentation.
- 💡Always relate your design choices to the business scenario provided in the assessment.
- 💡Practice drawing DFDs and flowcharts to ensure accuracy and neatness.
- 💡When designing inputs, consider validation rules and user experience.
- 💡For the prototype, ensure you include a clear user interface and document each screen or function.
- 💡In evaluations, use specific examples from your prototype to justify your points.
- 💡Practice using tools like DFDs and ERDs.
- 💡Ensure your prototype meets user requirements.
- 💡For exam units like 'Fundamentals of IT', use specific technical terminology (e.g., 'von Neumann architecture', 'pipelining') to show depth of knowledge. Avoid vague descriptions like 'the computer's brain' for the CPU.
- 💡In coursework units, ensure your evidence clearly links to the assessment criteria. For example, if a criterion asks for 'analysis', don't just describe – compare alternatives, justify choices, and evaluate outcomes. Use screenshots with annotations to demonstrate practical skills.
- 💡For the 'Project Management' unit, always include a risk assessment with a probability-impact matrix. Examiners look for realistic risks (e.g., 'team member illness') and clear mitigation plans, not generic statements like 'we will work hard'.
Common Mistakes
Common errors to avoid in your coursework
- Confusing data flow diagrams with flowcharts.
- Omitting validation rules for inputs.
- Prototype lacks documentation of design decisions.
- Confusing system design tools with project management tools (e.g., Gantt charts) and using them incorrectly.
- Creating designs that are too vague or lack sufficient detail to be implemented or evaluated.
- Ignoring user requirements when designing inputs and outputs, leading to poor usability.
- Submitting a prototype without any accompanying documentation or explanation of design decisions.
- Mixing up symbols in data flow diagrams.
- Omitting validation rules for inputs.
- Prototype lacking documentation or user feedback integration.
- Confusing data flow diagrams with flowcharts; DFDs focus on data movement, not control logic.
- Creating inputs/outputs without considering user needs or business objectives.
- Producing a prototype without any documentation, such as annotations or a user guide.
- Using incorrect symbols in DFDs or flowcharts, leading to misinterpretation.
- Failing to align the design with the original system requirements.
- Choosing the wrong tool for the task.
- Incomplete documentation of the prototype.
- Misconception: 'RAM is the same as storage.' Correction: RAM is volatile memory used for temporary data while the computer is on; storage (e.g., HDD/SSD) is non-volatile and retains data when powered off. They serve different purposes.
- Misconception: 'A higher IP address class always means a larger network.' Correction: IP address classes (A, B, C) define default subnet masks, but modern networks use CIDR (Classless Inter-Domain Routing) for flexible subnetting. Class alone doesn't determine network size.
- Misconception: 'Normalisation always improves database performance.' Correction: Normalisation reduces data redundancy and improves integrity, but can slow down queries due to more joins. In practice, denormalisation may be used for performance optimisation in read-heavy systems.
Frequently Asked Questions
Common questions students ask about this topic
Pass / Merit / Distinction Evidence Checklist
How your portfolio evidence is graded for CAMBRIDGE OCR System design
Every vocational unit is marked against named criteria rather than an exam percentage. Your tutor's brief lists the exact codes for this unit — here is what each band is asking you to do.
Demonstrate baseline knowledge, accurate terminology, and core practical application.
Provide detailed analysis, structured explanations, and clear workplace reasoning.
Deliver thorough evaluation, original problem solving, and fully justified recommendations.
Before You Start
Prior knowledge that will help with this topic
- •Basic understanding of computer hardware and software (e.g., from GCSE Computer Science or IT).
- •Familiarity with using common software applications like word processors, spreadsheets, and web browsers.
- •Elementary mathematical skills for data representation (binary, hexadecimal) and logical reasoning.
Coursework AI Review
Paste your assignment brief and check your draft against its P/M/D criteria
Key Terminology
Essential terms to know
- Understand how system design tools are used in a business system development, Be able to use system design tools in a business system, Be able to design system inputs and outputs, Be able to produce a documented prototype for a specified system
- System design tools and their purpose
- Input and output design principles
- Prototyping and documentation
- Business requirements analysis
- User interface considerations
- Understand how system design tools are used in a business system development, Be able to use system design tools in a business system, Be able to design system inputs and outputs, Be able to produce a documented prototype for a specified system
- System design tools
- Input and output design
- Prototyping and documentation
- Business requirements alignment
- Understand how system design tools are used in a business system development, Be able to use system design tools in a business system, Be able to design system inputs and outputs, Be able to produce a documented prototype for a specified system
Ready to learn?
AI-powered learning tailored to this unit