levo

Systems Analysis, Maintenance and Documentation

User and maintenance documentation

  • 3 things to know
  • Component 1

Overview

Five items that user documentation should contain, four components of maintenance documentation and annotated listing.

What you need to know

Answer each one before you reveal it.

Your recallNot started
Key term

Who is user documentation written for?

Key term

State five items that user documentation should contain.

Key term

Why does user documentation include a troubleshooting section?

Questions from this subtopic

Each one with the model answer underneath.

  1. 1

    Who is user documentation written for?

    Model answer

    User documentation is written for the people who operate the system day to day. The wording avoids technical detail about how the program works internally.

  2. 2

    State five items that user documentation should contain.

    Model answer

    Installation instructions, a getting started guide, descriptions of each function, a troubleshooting section and a glossary should all appear. A list of error messages and their meanings is also expected.

  3. 3

    Why does user documentation include a troubleshooting section?

    Model answer

    Common problems can be solved by the user without contacting the help desk. Support costs fall and the user is delayed for minutes rather than days.

  4. 4

    Who is maintenance documentation written for?

    Model answer

    Maintenance documentation is written for the programmers who will change the system later. The reader is assumed to be technically skilled but new to this program.

  5. 5

    Name four components of maintenance documentation.

    Model answer

    Annotated program listings, variable lists, the algorithms used and data dictionaries are four components. Design diagrams and test results are normally included too.

  6. 6

    What is an annotated listing?

    Model answer

    An annotated listing is the source code with comments explaining the purpose of each section. A maintainer can then follow the intention as well as the code.

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.