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
The Development Project: Build, Testing and Evaluation
Documentation for the completed system
- 3 things to know
- A2 Unit 2
Overview
What is handed over with a finished system, what the technical documents must record about the data and the processing, why decisions and their reasons are written down, and the test of whether the documentation is adequate.
What you need to know
Answer each one before you reveal it.
What documentation is delivered with a completed system?
Why is technical documentation delivered to the client rather than kept by the developer?
Questions from this subtopic
Each one with the model answer underneath.
- 1
What documentation is delivered with a completed system?
Model answer
A completed system is delivered with user documentation explaining how to operate it, and technical documentation recording how it is built — the data model, the module descriptions, the algorithms, the test plan and log, and the installation details.
- 2
Why is technical documentation delivered to the client rather than kept by the developer?
Model answer
The client owns the system and may use someone else to maintain it, so the knowledge of how it works has to be handed over with it, or the client is tied to one developer for the system's life.
- 3
What should technical documentation contain about the data?
Model answer
It should contain the entity-relationship diagram, every table with its attributes, types, sizes, keys and validation, the relationships and the integrity rules, and the normalisation that produced the structure.
- 4
What should technical documentation contain about the processing?
Model answer
It should contain a description of each module and its purpose, the algorithms for anything involving calculation, decision or repetition, and the interfaces between modules, including the data each passes.
- 5
Why is the test plan and its log part of the delivered documentation?
Model answer
They are the evidence that the system was checked against its requirements, and they give a maintainer a ready set of tests with known correct answers to re-run after any future change.
- 6
What should the installation documentation record?
Model answer
It should record the hardware and software the system requires, the steps to install it, any configuration settings, the licences held, and how backups are taken and restored.
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 The Development Project: Build, Testing and Evaluation, 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.