Key Definitions - 2.3 Flashcards

1
Q

Input Sanitisation

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Validation

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Contingency Planning

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Misuse

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Authentication

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Maintainability

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Comments

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Naming Conventions

A
  • 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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Testing -

A
  • 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Iterative Testing -

A
  • 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Final/Terminal Testing

A
  • Final/terminal testing takes place once the program has been completed.
  • It tests the whole program at the end of its development
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Syntax Error

A
  • Means code has been incorrectly written and will stop the program from working
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Logic Error

A
  • Code doesn’t stop the program from working but stops the program from working the way it should do
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Test Data

A
  • The data that is selected to be used when testing a program.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Normal Data -

A

This data is correct and should be accepted by the program

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Invalid Data -

A

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

17
Q

Boundary Data -

A

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

18
Q

Erroneous Data

A

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

19
Q

Defensive Design Considerations

A
  • Input Sanitisation/Validation
  • Contingency Planning
  • Anticipating Misuse
  • Authentication
20
Q

What does validation check and not check?

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

Authentication

A

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