Systems Analysis & Design
This topic covers systems analysis and design methodologies, including traditional and agile approaches. Learners evaluate methodologies, produce feasibility studies, and design systems to meet user requirements.
Assessment criteria
Quick Revision Summary (Key Takeaway)
The Pearson BTEC Level 5 Higher National Diploma in Computing for England covers programming, networking, databases, and software development. This qualification emphasizes practical skills and theoretical understanding for careers in computing, with units like Programming, Networking, and Database Design.
Topic Overview
The Pearson BTEC Level 5 Higher National Diploma in Computing for England is a vocational qualification equivalent to the second year of a university degree. It covers core computing concepts such as programming (using languages like Python, Java, or C#), networking (OSI and TCP/IP models, subnetting), database design (normalisation, SQL), and software development methodologies (Agile, Waterfall). The course is designed to provide both theoretical knowledge and practical skills, preparing students for roles such as software developer, network engineer, or database administrator.
This qualification is structured into mandatory units (e.g., Programming, Networking, Professional Practice) and optional specialist units (e.g., Data Analytics, Cybersecurity). Assessment is through assignments, projects, and practical tasks rather than traditional exams, emphasising real-world application. Students must demonstrate understanding of concepts like algorithms, data structures, network security, and database normalisation to succeed.
Mastery of this diploma opens pathways to top-up degrees or direct employment. The curriculum aligns with industry needs, focusing on problem-solving, teamwork, and technical proficiency. Understanding the interplay between hardware, software, and networks is crucial, as is the ability to document and present technical solutions clearly.
Key Concepts
Core ideas you must understand for this topic
- →Programming constructs: sequence, selection, iteration; data types; functions; object-oriented programming.
- →Networking models: OSI 7-layer model, TCP/IP 4-layer model; IP addressing and subnetting.
- →Database normalisation: 1NF, 2NF, 3NF; SQL queries (SELECT, JOIN, GROUP BY).
- →Software development lifecycle: Waterfall, Agile, Scrum; testing strategies.
- →Professional practice: ethical considerations, legal issues (e.g., GDPR), project management.
Learning Objectives
What you need to know and understand
- 1. Evaluate the strengths and weaknesses of the traditional and agile systems analysis methodologies.2. Produce a feasibility study for a system to be developed to solve a business-related problem.3. Assess systems analysis methodologies to effectively solve business-related problems.4. Design a system to meet user and system requirements.
- 1. Evaluate the strengths and weaknesses of the traditional and agile systems analysis methodologies.2. Produce a feasibility study for a system to be developed to solve a business-related problem.3. Assess systems analysis methodologies to effectively solve business-related problems.4. Design a system to meet user and system requirements.
Assessment Criteria
Key criteria assessors look for in your portfolio
- Evaluates strengths and weaknesses of Waterfall vs Agile methodologies.
- Produces a feasibility study covering technical, economic, and operational aspects.
- Assesses methodologies for suitability to specific business problems.
- Designs a system using appropriate diagrams (e.g., DFDs, UML).
- Evaluate strengths and weaknesses of traditional vs agile methodologies.
- Produce a comprehensive feasibility study for a business problem.
- Select and justify appropriate methodology for a given scenario.
- Design a system that meets both user and system requirements.
- Use appropriate modelling techniques in system design.
Assessment Guidance
Guidance for achieving higher grades
- 💡Use real-world examples to illustrate methodology choices.
- 💡Practice drawing context diagrams and use case diagrams.
- 💡Ensure feasibility study includes clear recommendations.
- 💡Use real-world examples to illustrate methodology comparisons.
- 💡Ensure feasibility study covers technical, economic, and operational aspects.
- 💡Practice creating UML diagrams for system design.
- 💡Always define key terms before using them in answers. For example, when discussing normalisation, state the normal forms explicitly.
- 💡Use diagrams where appropriate, such as network topology diagrams or ER diagrams, to illustrate your understanding.
- 💡In programming questions, comment your code to explain logic; examiners look for clarity and structure.
Common Mistakes
Common errors to avoid in your coursework
- Confusing feasibility study with requirements specification.
- Overlooking non-functional requirements in design.
- Applying Agile without understanding its iterative nature.
- Confusing feasibility study with project plan.
- Overlooking user requirements in system design.
- Failing to justify methodology choice with evidence.
- Misconception: The OSI model's Transport layer is the same as TCP/IP's Transport layer. Correction: While both provide end-to-end communication, OSI Transport layer includes additional services like error recovery not always present in TCP/IP.
- Misconception: Normalisation always improves database performance. Correction: Normalisation reduces redundancy but can increase join operations, potentially slowing queries. Denormalisation may be used for performance.
- Misconception: Agile means no documentation. Correction: Agile values working software over comprehensive documentation, but some documentation is still required for maintainability.
Revision Plan
How to revise this topic in 1–2 weeks
- 1Week 1: Focus on programming fundamentals. Practice writing simple programs in Python or Java, covering loops, conditionals, and functions.
- 2Week 2: Study networking concepts. Create flashcards for OSI and TCP/IP layers, practice subnetting calculations.
- 3Week 3: Dive into database design. Normalise sample datasets to 3NF, write SQL queries.
- 4Week 4: Review software development methodologies and professional practice. Work on a mini-project using Agile.
- 5Week 5: Attempt past papers or sample assignments. Time yourself and review mark schemes.
- 6Week 6: Consolidate weak areas. Use active recall and teach concepts to a peer.
Exam Question Types
How this topic typically appears in the exam
- 📋Multiple-choice questions: Test definitions and basic facts. Tip: Eliminate obviously wrong answers first.
- 📋Short-answer questions: Require brief explanations or calculations. Tip: Show all working for numerical answers.
- 📋Scenario-based questions: Describe a real-world problem and ask for a solution. Tip: Structure your answer using the scenario details.
- 📋Practical tasks: Write code or design a database schema. Tip: Plan before writing; check for syntax errors.
Command Word Expectations (PEARSON)
What examiners look for when using specific command words in this specification
Provide a balanced judgement, discussing pros and cons, and conclude with a reasoned opinion.
Give a detailed account of how or why something occurs, including reasons and causes.
Create a plan or specification, such as a network topology or database schema, with justification.
How Students Lose Marks (Examiner Pitfalls)
Common mark loss traps and how to write 100% full-mark answers
Step-by-Step Worked Solutions
Detailed solution breakdown for typical exam problems
Question: A network has a subnet mask of 255.255.255.0. How many usable host addresses are there in this subnet?
- 1.Step 1: Identify the number of host bits: 32 - 24 = 8 bits.
- 2.Step 2: Calculate total addresses: 2^8 = 256.
- 3.Step 3: Subtract network and broadcast addresses: 256 - 2 = 254 usable hosts.
Question: Convert the decimal number 45 to binary.
- 1.Step 1: Divide 45 by 2, remainder 1 (LSB).
- 2.Step 2: Continue dividing: 22 rem 0, 11 rem 1, 5 rem 1, 2 rem 0, 1 rem 1.
- 3.Step 3: Read remainders from last to first: 101101.
Active Recall Memory Test
Test your memory before revealing the key facts
Frequently Asked Questions
Common questions students ask about this topic
Pass / Merit / Distinction Evidence Checklist
How your portfolio evidence is graded for PEARSON Systems Analysis & Design
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.
- •Familiarity with mathematical concepts like binary, decimal, and hexadecimal.
- •Some experience with a programming language (e.g., from GCSE or A-level Computing).
Coursework AI Review
Self-check your coursework evidence against P/M/D criteria
Key Terminology
Essential terms to know
- 1. Evaluate the strengths and weaknesses of the traditional and agile systems analysis methodologies.2. Produce a feasibility study for a system to be developed to solve a business-related problem.3. Assess systems analysis methodologies to effectively solve business-related problems.4. Design a system to meet user and system requirements.
- 1. Evaluate the strengths and weaknesses of the traditional and agile systems analysis methodologies.2. Produce a feasibility study for a system to be developed to solve a business-related problem.3. Assess systems analysis methodologies to effectively solve business-related problems.4. Design a system to meet user and system requirements.
Ready to learn?
AI-powered learning tailored to this unit