2.3 robust programs Key vocabulary

2.3 robust programs Key vocabulary

1. defensive design

   • planning a program from the very beginning to prevent accidental or purposeful misuse

2. input sanitization

   • removing erroneous data from a system prior to processing

3. data validation

   • enduring all data is in the correct format prior to processing

4. contingency planning

   • having built in checks and outcomes based on what happens when things go wrong

5. anticipating misuse

   • building programs which do not allow a user to deliberately break the system

6. authentication

   • having different levels of user and preventing everyday users from being able to significantly change a system

7. maintainability

   • building software which is modular to enable sections to be updated and replaced without having to write the whole program again from scratch

8. code comments

   • annotating code so that the person maintaining or working with your code in the future is able to understand your thought process

9. indentation

   • making code more readable by laying it out in a manner that keeps the code separate

10. iterative testing

    • step by step testing to ensure that small sections of the code work. before new parts are added and than rested .important to allow traceback to find out what caused any errors

11. terminal testing

    • significant testing done once a program is complete under a range of conditions and on multiple hardware - often called alpha testing

12. beta testing

    • making a small release of the software to a group of tech-literate enthusiasts to broaden the usage -testing and get lots of the feedback prior to full release

13. syntax error

    • an error in the typing of the code. missing punctuation , spacing ect

14. test data

    • data chosen to test the program. testers use a specific range of data