levo

Systems Analysis, Maintenance and Documentation

Perfective, adaptive and corrective maintenance

  • 3 things to know
  • Component 1

Overview

Corrective maintenance, adaptive maintenance and perfective maintenance.

What you need to know

Answer each one before you reveal it.

Your recallNot started
Key term

Why does software need maintenance after it has been delivered?

Key term

Describe corrective maintenance.

Key term

Give an example of corrective maintenance.

Questions from this subtopic

Each one with the model answer underneath.

  1. 1

    Why does software need maintenance after it has been delivered?

    Model answer

    Faults survive testing, the organisation changes and the surrounding technology moves on. A system that is never maintained becomes unusable within a few years.

  2. 2

    Describe corrective maintenance.

    Model answer

    Corrective maintenance repairs faults discovered after the system went live. The behaviour of the system is brought back to what the specification promised.

  3. 3

    Give an example of corrective maintenance.

    Model answer

    A report that totals a column incorrectly is traced and the calculation is fixed. The purpose of the program has not changed.

  4. 4

    Describe adaptive maintenance.

    Model answer

    Adaptive maintenance changes a system so it keeps working in a changed environment. New hardware, a new operating system or a change in the law can all force it.

  5. 5

    Give an example of adaptive maintenance.

    Model answer

    A change in the rate of VAT forces an update to every calculation that uses it. The system worked correctly before and must keep working afterwards.

  6. 6

    Describe perfective maintenance.

    Model answer

    Perfective maintenance improves a system that is already working correctly. Extra features, a better interface or faster processing are typical results.

Other ways to work this

The same content, four other ways.

What is inside Levo

Six ways to work the same material.

1Closed book
2Open book
3Closed book

The 3-step method, run for you

Answer cold, learn it, then prove it stuck. Levo tracks the jump between your first attempt and your last.

Data Structures: Arrays, Records and Hash Tables
Stacks, Queues, Linked Lists and Trees
Boolean Logic and Simplification
Algorithms, Pseudo-Code and Programming Constructs

Cram a whole paper in one sitting

Sort every topic into what you know and what you do not, then drill only the weak ones.

KDW to HAT.
decryptsencryptscompresses

Blank Blitz makes facts automatic

Rapid timed gap-fills on the terms and numbers you need to recall without thinking.

AThe two are not the same.
BOpen source refers to the availability of the code.
CMuch open source software is free of charge.

Build It gets the exam shape right

Assemble a full-mark answer from its marking points, in the order an examiner wants them.

Backup means the copy of the data.
TrueFalse

Test It catches misconceptions

Spot the fault in a statement. The traps are the mistakes students actually make.

721941163128510

Brain Breaks between sessions

Short focus games to reset attention, so the next set lands better than the last.

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.