Across
- 3. occurs when code written does not follow grammar of the programming language (stops program from running) e.g. misspelling, missing brackets
- 4. verifying the identity of a user
- 6. an error in the way a program works so the program doesn’t know what to do (program doesn’t perform as expected) e.g. incorrect bracket/Boolean usage
- 8. data that is used to test whether or not a program is functioning correctly, covering a range of possible & impossible inputs, highlighting any flaws
- 11. a list of all the tests that the programmer intends to use to ensure the program functions as intended, containing a mix of the types of test data
- 12. checking input data is sensible and in the right format
Down
- 1. carried out when all modules are complete and the program is tested as a whole to ensure that it functions as it should
- 2. hiding/protecting data so it can’t be seen or disclosed (e.g. checking entered data and removing dangerous inputs which could cause damage to a program)
- 5. checking a program for errors by running it and seeing outputs and whether results are expected
- 7. ensuring that a program is easy to understand, modify and update
- 9. ensuring that a program runs correctly and continues to run no matter what actions a user takes
- 10. carried out while a program is being developed. A section of code (module) is written and tested. The module may be amended or fixed and tested again. The process repeats (iterates) until the module works as intended