Karteikarten
Unit 2.3 - Robust Programs
Karten in diesem Stapel (19)
- 1Data Validation (Verification)Ensures data is sensible within certain rules
- 2Data Sanitisation (Accuracy)Whatever is inout needs to be cleaned to make it consistent
- 3Anuthentication (Double Entry)Comparing against stored information
- 4Maintainability (Checking at the end)Comment on programming so it can continue to be maintained by other programmers
Comments- inform the reader
Indentation- groups together a function - 5Check DigitThe last one or two digits in a code are used to check other digits are correct
eg Bar code readers in supermarkets use check digits - 6Format CheckChecks the data is in the right format
eg. National Insurance Number in format LL999999L - 7Length CheckChecks whether it's too short or too long
eg. Password needs to be at least 6 letters long - 8Lookup TableLooks up acceptable values in a table
eg. Only seven possible days of the week - 9Presence CheckChecks data has been entered into a field
eg. In most databases a key field cannot be left blank - 10Range CheckChecks whether a value falls within a specific range
eg. Number of hours worked must be <50 and >0 - 11Spell CheckLooks up words in a dictionary
eg. MS Word uses red lines to underline misspelt words - 12ContingenciesPlanning for the unexpected;
-Limiting the number of login attempts
-Ensuring the code is robust in validating data entered
-Authentication can also be physical - 13Iterative TestingTesting code as you create it; could be completed line by line or a section at a time
(during Implementation in the system life cycle) - 14Final/ Terminal TestingCarried out at the end during testing near the end of the system life cycle
- 15System Life Cycle1) Background and Investigation
2) Analysis
3) Design; Final/Terminal Test Plan is created
4) Implementation; Iterative Testing takes place
5) Testing; Final/Terminal Testing takes place
6) Evaluation; Feedback on Iterative and Final Testing - 16Syntax ErrorsWill stop the program from running; translators can only execute a program if it is syntactically correct
- 17Logic ErrorsThe program doesn't crash but instead doesn't run and operate correctly
- 18Runtime ErrorsOnly occur when the program is running and something causes it to crash even though it seems as though nothing is wrong
eg. Running out of memory - 19Using a range of Test Data during Testing- Valid/ in range --> maximum values of the data that can be entered
- Out of range --> Out of expected range
- Boundary Value
-Null value --> No entered data
-Invalid
Informationen
- Beschreibung
- Karteikarten am Unit 2.3 - Robust Programs, erstellt von Karolina Rawdanowicz am 03/03/2019.
- Erstellt von
- Karolina Rawdanowicz · Mär 2019
- Aktualisiert
- 3 Mär 2019
- Aufrufe
- 3
- Bewertung