Systems analysis
This subtopic focuses on the initial phases of the system development life cycle, emphasizing the critical role of requirements gathering and documentation. Learners will explore various fact-finding techniques, assess the importance of clear system requirements, and develop skills in analyzing and documenting these requirements to inform system design and implementation.
Assessment criteria
Topic Overview
The Cambridge OCR Level 3 Cambridge Technical Diploma in IT is a vocational qualification designed to equip students with practical IT skills and theoretical knowledge for the workplace or further study. It covers a broad range of topics including IT systems, cyber security, web development, and data analysis, emphasising real-world application. This diploma is equivalent to two A-Levels and is highly valued by employers and universities for its hands-on approach.
Students will develop a deep understanding of how IT systems operate, from hardware components to software applications, and learn to solve complex problems using computational thinking. The course also focuses on professional practice, including project management, communication, and ethical considerations in IT. By the end, students will be prepared for roles such as IT support technician, web developer, or network administrator, or for progression to higher education in computing-related fields.
The qualification is structured into mandatory and optional units, allowing students to tailor their learning to their interests. Mandatory units cover fundamentals like IT systems, cyber security, and project management, while optional units delve into areas such as mobile app development, game design, and big data analytics. This flexibility ensures that students gain both breadth and depth in IT, making them versatile and job-ready.
Key Concepts
Core ideas you must understand for this topic
- →Understanding the components of IT systems: hardware (CPU, memory, storage) and software (operating systems, applications) and how they interact.
- →Cyber security principles: confidentiality, integrity, availability (CIA triad), common threats (malware, phishing), and mitigation strategies (encryption, firewalls).
- →Project management methodologies: waterfall and agile, including planning, risk assessment, and documentation.
- →Data modelling and analysis: using tools like spreadsheets and databases to store, manipulate, and interpret data for decision-making.
- →Web development fundamentals: HTML, CSS, and JavaScript, along with responsive design and accessibility standards.
Learning Objectives
What you need to know and understand
- Explain the stages of the system development life cycle
- Compare different fact-finding techniques used in requirements gathering
- Evaluate the importance of documenting system requirements
- Apply appropriate techniques to gather and analyze system requirements
- Produce a requirements specification document
- Develop a project plan for system development
- Understand the requirements for system development, Understand the importance of documenting system requirements, Be able to carry out a systems analysis, Be able to plan for a system development
- Understand the requirements for system development, Understand the importance of documenting system requirements, Be able to carry out a systems analysis, Be able to plan for a system development
- Understand the requirements for system development, Understand the importance of documenting system requirements, Be able to carry out a systems analysis, Be able to plan for a system development
- Understand the requirements for system development, Understand the importance of documenting system requirements, Be able to carry out a systems analysis, Be able to plan for a system development
Assessment Criteria
Key criteria assessors look for in your portfolio
- Award credit for demonstrating understanding of the system development life cycle stages
- Award credit for comparing at least two fact-finding techniques with reference to their advantages and disadvantages
- Award credit for explaining the consequences of poor documentation of system requirements
- Award credit for using appropriate fact-finding techniques in a given scenario
- Award credit for producing a requirements specification that includes functional and non-functional requirements
- Award credit for creating a project plan that includes tasks, timelines, and resources
- Identifies and documents user and system requirements clearly.
- Uses appropriate fact-finding techniques such as interviews and questionnaires.
- Creates diagrams like DFDs or use cases to model the system.
- Produces a feasibility study and project plan for system development.
- Explains the importance of accurate documentation in the development lifecycle.
- Understand requirements for system development.
- Document system requirements clearly.
- Carry out a systems analysis using appropriate techniques.
- Plan for system development based on analysis.
- Identify and categorise functional and non-functional requirements.
- Produce clear and complete system requirement documentation.
- Use appropriate techniques such as interviews or questionnaires.
- Create a project plan with timelines and resources.
- Justify the chosen system development methodology.
- Identifies stakeholders and their information needs.
- Uses appropriate fact-finding techniques (interviews, questionnaires).
- Produces clear and complete system requirements documentation.
- Creates a project plan with timelines and resources.
- Evaluates feasibility in terms of technical, economic, and operational factors.
Assessment Guidance
Guidance for achieving higher grades
- 💡Use real-world examples to illustrate the importance of requirements documentation
- 💡Practice applying fact-finding techniques to case studies
- 💡Ensure you can distinguish between functional and non-functional requirements
- 💡When planning, use Gantt charts or similar tools to show timelines and dependencies
- 💡Always justify your choice of fact-finding technique in context
- 💡Use standard notation for diagrams (e.g., UML).
- 💡Ensure requirements are SMART.
- 💡Show how analysis feeds into the planning stage.
- 💡Use diagrams like DFDs and ERDs.
- 💡Ensure requirements are SMART.
- 💡Consider technical and economic feasibility.
- 💡Use standard templates for requirement documents.
- 💡Ensure all requirements are measurable and testable.
- 💡Practice creating a simple Gantt chart for planning.
- 💡Use diagrams like DFDs and ERDs to clarify requirements.
- 💡Always validate requirements with stakeholders.
- 💡Consider the impact of constraints like budget and time.
- 💡Use specific examples from real-world scenarios to illustrate your answers, such as referencing a recent cyber attack or a successful IT project. This shows application of knowledge.
- 💡In project management questions, always mention the importance of documentation and communication with stakeholders. Examiners look for evidence of professional practice.
- 💡For web development tasks, ensure your code is well-commented and follows best practices like semantic HTML and CSS naming conventions. This demonstrates attention to detail.
Common Mistakes
Common errors to avoid in your coursework
- Confusing the terms 'requirements' and 'specification'
- Overlooking non-functional requirements such as performance and security
- Failing to involve stakeholders in the requirements gathering process
- Not documenting assumptions and constraints
- Creating a project plan without considering dependencies and risks
- Confusing functional and non-functional requirements.
- Producing incomplete or ambiguous documentation.
- Skipping validation of requirements with stakeholders.
- Incomplete or ambiguous requirements gathering.
- Poor documentation that is hard to follow.
- Skipping feasibility analysis.
- Confusing functional with non-functional requirements.
- Omitting stakeholder validation of requirements.
- Producing vague or ambiguous documentation.
- Assuming users know exactly what they want without probing.
- Writing requirements that are too vague or ambiguous.
- Ignoring non-functional requirements like security and performance.
- Misconception: 'IT is just about fixing computers.' Correction: IT encompasses a wide range of skills including programming, data analysis, cyber security, and project management, not just hardware troubleshooting.
- Misconception: 'Cyber security only involves antivirus software.' Correction: Cyber security is a holistic discipline covering policies, user training, network security, and incident response, not just technical tools.
- Misconception: 'Project management is only for managers.' Correction: All IT professionals need project management skills to plan tasks, manage time, and collaborate effectively, regardless of their role.
Frequently Asked Questions
Common questions students ask about this topic
Pass / Merit / Distinction Evidence Checklist
How your portfolio evidence is graded for CAMBRIDGE OCR Systems analysis
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, typically covered in GCSE Computer Science or equivalent.
- •Familiarity with using common software applications like word processors and spreadsheets.
- •Logical thinking and problem-solving skills, which can be developed through maths or other analytical subjects.
Coursework AI Review
Paste your assignment brief and check your draft against its P/M/D criteria
Key Terminology
Essential terms to know
- System development life cycle
- Requirements gathering techniques
- Documentation of system requirements
- Feasibility study
- Stakeholder communication
- Planning for system development
- Understand the requirements for system development, Understand the importance of documenting system requirements, Be able to carry out a systems analysis, Be able to plan for a system development
- Understand the requirements for system development, Understand the importance of documenting system requirements, Be able to carry out a systems analysis, Be able to plan for a system development
- Understand the requirements for system development, Understand the importance of documenting system requirements, Be able to carry out a systems analysis, Be able to plan for a system development
- Understand the requirements for system development, Understand the importance of documenting system requirements, Be able to carry out a systems analysis, Be able to plan for a system development
Ready to learn?
AI-powered learning tailored to this unit