CCEA A-Level Digital Technology 2650
Systems Analysis and Development Approaches
Design, Development and Testing
Implementation and System Security
Programming
Data, Information and Data Representation
Computer Architecture and Processing Systems
System Software, Application Software and the User Interface
Web Technology and Multimedia
Networks
Databases
Artificial Intelligence, Expert Systems and Robotics
Mobile Technology, Data Mining and Cloud Computing
Individual, Social and Legal Considerations
The Development Project: Analysis and Design
The Development Project: Build, Testing and Evaluation
Implementation and System Security
The purpose of system maintenance
- 3 things to know
- AS Unit 1
Overview
System maintenance, three events that typically trigger maintenance work and change request.
What you need to know
Answer each one before you reveal it.
Why are changes to a live system controlled formally?
What is an impact analysis?
Questions from this subtopic
Each one with the model answer underneath.
- 1
What is system maintenance?
Model answer
System maintenance is the work of changing a system after it has gone live, in order to correct faults, keep it working in a changing environment and improve it.
- 2
Why does a fully tested system still need maintenance?
Model answer
Testing cannot find every fault, and the law, the business and the hardware and software around the system all continue to change after it has been delivered.
- 3
Why does maintenance usually cost more over a system's life than the original development did?
Model answer
Maintenance continues for as long as the system is used, often many years, and every change must be analysed, designed, coded, tested and documented just as the original work was.
- 4
Name three events that typically trigger maintenance work.
Model answer
Maintenance is triggered by a fault reported by users, by a change in the law or in business rules, and by an upgrade to the hardware or operating system the software runs on.
- 5
What is a change request?
Model answer
A change request is a formal record of a requested alteration to a live system, stating what is wanted and why, so that it can be assessed and prioritised rather than made informally.
- 6
Why are changes to a live system controlled formally?
Model answer
An uncontrolled change can break other functions or be lost at the next release, so each one is assessed for its effects, tested and recorded before it is applied.
Other ways to work this
The same content, four other ways.
What is inside Levo
Six ways to work the same material.
Every question in Implementation and System Security, 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.