Testing and Documentation (Evaluation (Efficient Use of Coding Constructs:…
Testing and Documentation
Comprehensive test Plan:
The process of testing normal, exceptional and extreme data.
Data that is on the limit of the acceptable range.
Data that shouldn't be accepted but should trigger a response.
Data that should accepted and handled correctly
The program will work but will result in incorrect outcome. A result of incorrect code being used.
Occurs when a program is asked to do something it cannot, resulting in a crash.
Spelling or grammar error.
Trace tables are used to allow programmers to trace the value of variables as each line of code is executed. The values of the variables are displayed in a table and assist the programmer in identifying any potential errors.
A specified point in the program where the code will stop working, to check the program is working correctly.
The process of programmer manually working through their code, with no software, to trace the values of variables.
The code will stop working when a specified variable reaches a specified value.
Efficient Use of Coding Constructs:
The programmer using coding constructs such as arrays, loops and selection statements.
Fitness for Purpose:
Software is deemed fit for purpose if it meets the requirements determined at the analysis phase.
Compares how usable software is in relation to it's intended purpose.
Code that can cope with unexpected or incorrect input.
Use of comments, indentation and meaningful identifiers so a piece of code can be easily read by another programmer.