Eduqas A-Level Computer Science A500QS
Data Structures: Arrays, Records and Hash Tables
Stacks, Queues, Linked Lists and Trees
Boolean Logic and Simplification
Algorithms, Pseudo-Code and Programming Constructs
Variables, Scope, Parameters and Identifiers
Recursion and Modular Programming
Sorting Algorithms
Searching and Shortest-Path Algorithms
Big O Notation and Algorithm Efficiency
Validation, Verification and Testing
Data Compression
Programming Paradigms and Computer Languages
Systems Analysis, Maintenance and Documentation
System Design and Human-Computer Interaction
Software Engineering Tools and Translators
Computing, Society and the Law
Computer Architecture, the Processor and Assembly Language
Input, Output and Secondary Storage
Networks, Protocols and the Internet
Data Transmission and Network Performance
Number Systems and Binary Arithmetic
Data Types, Characters and Floating Point
Files, Records and File Organisation
Databases, Normalisation and Entity Modelling
SQL, Big Data and Distributed Systems
The Operating System and Its Modes
Interrupts, Memory Management and Scheduling
Types of Software System
Data Security, Cryptography and Attack
Systems Analysis, Maintenance and Documentation
- 9 subtopics
- 27 things to know
- Component 1
What Systems Analysis, Maintenance and Documentation covers
Systems Analysis, Maintenance and Documentation is examined in Component 1, Programming and System Development. It covers Waterfall, Agile and approaches to systems development, the feasibility study, budgets and time scales, methods of investigation, abstraction, decomposition and data flow diagrams, selecting suitable hardware and software, acceptance testing and methods of changeover, perfective, adaptive and corrective maintenance, backup and recovery procedures and user and maintenance documentation.
The 9 subtopics
Each one has its own page.
- Waterfall, Agile and approaches to systems developmentWaterfall approach to systems development, two advantages of the Waterfall approach and two disadvantages of the Waterfall approach.Open →
- The feasibility study, budgets and time scalesPurpose of a feasibility study, main areas of feasibility an analyst investigates and processes an analyst carries out during a feasibility study.Open →
- Methods of investigationInterview as a method of investigation, one advantage and one disadvantage of interviews and questionnaire as a method of investigation.Open →
- Abstraction, decomposition and data flow diagramsAbstraction as used in systems analysis, abstraction in a system model and why decomposition helps a team of developers.Open →
- Selecting suitable hardware and softwareChoice between off-the-shelf and bespoke software, two risks of choosing off-the-shelf software and role of a requirements specification in choosing software.Open →
- Acceptance testing and methods of changeoverAlpha testing, beta testing and acceptance testing.Open →
- Perfective, adaptive and corrective maintenanceCorrective maintenance, adaptive maintenance and perfective maintenance.Open →
- Backup and recovery proceduresFull backup, incremental backup and differential backup.Open →
- User and maintenance documentationFive items that user documentation should contain, four components of maintenance documentation and annotated listing.Open →
What you need to know
Answer each one before you reveal it.
What does a data flow diagram show, and what are its components?
State the purpose of a feasibility study.
Why does an analyst investigate the existing system before designing a new one?
On what basis does an analyst select hardware for a new system?
Describe alpha testing.
Why does software need maintenance after it has been delivered?
What is a backup?
Who is user documentation written for?
Describe the Waterfall approach to systems development.
Name the main areas of feasibility an analyst investigates.
Describe the interview as a method of investigation.
Define abstraction as used in systems analysis.
Why must the analyst consider future growth when specifying hardware?
Describe beta testing.
Describe corrective maintenance.
Describe a full backup.
State five items that user documentation should contain.
State two advantages of the Waterfall approach.
What does technical feasibility examine?
State one advantage and one disadvantage of interviews.
Give an example of abstraction in a system model.
Explain the choice between off-the-shelf and bespoke software.
State one benefit of beta testing that alpha testing cannot provide.
Give an example of corrective maintenance.
Describe an incremental backup.
Why does user documentation include a troubleshooting section?
Take Systems Analysis, Maintenance and Documentation further
The same content, four other ways.
Commonly confused
Pairs that lose marks when they are blurred together.
Waterfall vs Agile
Waterfall: completing each stage once and then closing it off. Agile: repeating the whole cycle in short increments.
User documentation vs Maintenance documentation
User documentation: explaining how to operate the system. Maintenance documentation: explaining how it is built.
Phased changeover vs Pilot changeover
Phased changeover: moving part of the system everywhere at once. Pilot changeover: moving all of the system to one location first.
Questions from this topic
Each one with the model answer underneath.
- 1
Describe the Waterfall approach to systems development.
Model answer
The Waterfall approach works through analysis, design, implementation, testing and maintenance as separate stages. Each stage is signed off before the next one begins.
- 2
State two advantages of the Waterfall approach.
Model answer
Deliverables and deadlines are known from the outset, which makes the project easy to manage. Full documentation is produced at every stage for later maintainers.
- 3
State two disadvantages of the Waterfall approach.
Model answer
The client sees nothing working until very late in the project. Requirements that change after sign-off are expensive to accommodate.
- 4
Describe the Agile approach to systems development.
Model answer
Agile development delivers a small working increment of the system in each short cycle. The client reviews each increment and helps set the priorities for the next.
- 5
State two advantages of the Agile approach.
Model answer
Changing requirements are absorbed easily because the plan is revisited every cycle. Continuous client involvement makes a badly misunderstood requirement obvious within weeks.
- 6
State two disadvantages of the Agile approach.
Model answer
The final cost and delivery date are hard to fix at the start. Documentation is lighter, which can make long-term maintenance harder.
What is inside Levo
Six ways to work the same material.
Systems Analysis, Maintenance and Documentation revision questions
- What does Systems Analysis, Maintenance and Documentation cover in Eduqas A-Level Computer Science?
- 9 subtopics: waterfall, agile and approaches to systems development, the feasibility study, budgets and time scales, methods of investigation, abstraction, decomposition and data flow diagrams, selecting suitable hardware and software, acceptance testing and methods of changeover, perfective, adaptive and corrective maintenance, backup and recovery procedures and user and maintenance documentation. Each one has its own page with questions and model answers.
- How is Systems Analysis, Maintenance and Documentation organised?
- By the Eduqas A500QS specification, subtopic by subtopic, so it matches the order you are taught it in.
Every question in Systems Analysis, Maintenance and Documentation, on a schedule.
Attempt a question from memory, write the correct version, then attempt it again. Levo records the jump between your first attempt and your last, and brings each question back on the day you are due to forget it.
Or £46 a year, about £3.83 a month. Cancel anytime.