Back to marketplace

Key Definitions - 2.3

No description yet. This curated deck is ready for daily study.

Total cards: 21•Content version: v4•Public deck•Updated: 8/1/2026

Card preview (21)

#1
Front (Question)

Input Sanitisation

Back (Answer)

Process of cleaning up a user’s input so it’s in a suitable format ready for processing

#2
Front (Question)

Validation

Back (Answer)

Process of checking the user has inputted data in the correct format e.g for a data it could be DD/MM/YYYY

#3
Front (Question)

Contingency Planning

Back (Answer)

The process of having a ‘back up plan’ in case the original plan fails

#4
Front (Question)

Misuse

Back (Answer)

When a user doesn’t use the program the way it was designed to be used

#5
Front (Question)

Authentication

Back (Answer)

The process of ensuring a user has the rights/permissions to access a program e.g. by getting them to enter a username and/or password.

#6
Front (Question)

Maintainability

Back (Answer)

This refers to ensuring the program can be easily updated, improved, and fixed

#7
Front (Question)

Comments

Back (Answer)

Used within a program. They help briefly identify what a section of code does

#8
Front (Question)

Naming Conventions

Back (Answer)

• A ‘rule of thumb’ programmers will use when writing in a specific language. • They follow certain rules when naming identifiers such as use of lowercase/uppercase characters, underscores etc.

#9
Front (Question)

Testing -

Back (Answer)

• The process of assessing whether a program works correctly and the way it should work. • We aim to find ‘bugs’ and rectify them so the program is faultless

#10
Front (Question)

Iterative Testing -

Back (Answer)

• A type of testing. Iterative testing is carried out throughout the development of the program. • Multiple ‘mini tests’ are carried out on sections of code

#11
Front (Question)

Final/Terminal Testing

Back (Answer)

• Final/terminal testing takes place once the program has been completed. • It tests the whole program at the end of its development

#12
Front (Question)

Syntax Error

Back (Answer)

• Means code has been incorrectly written and will stop the program from working

#13
Front (Question)

Logic Error

Back (Answer)

• Code doesn’t stop the program from working but stops the program from working the way it should do

#14
Front (Question)

Test Data

Back (Answer)

• The data that is selected to be used when testing a program.

#15
Front (Question)

Normal Data -

Back (Answer)

This data is correct and should be accepted by the program

#16
Front (Question)

Invalid Data -

Back (Answer)

Data is of the correct data type but outside of the requirements set

#17
Front (Question)

Boundary Data -

Back (Answer)

On the edge of a range specified by the program and therefore should be accepted

#18
Front (Question)

Erroneous Data

Back (Answer)

Data that is of the incorrect data type and therefore should be rejected.

#19
Front (Question)

Defensive Design Considerations

Back (Answer)

• Input Sanitisation/Validation • Contingency Planning • Anticipating Misuse • Authentication

#20
Front (Question)

What does validation check and not check?

Back (Answer)

• Checks to see if a user has inputted in the right format • Doesn’t check if it’s correct/true

#21
Front (Question)

Authentication

Back (Answer)

The process of ensuring a user has the right permission to access a computer program e.g username and password checker