Software Engineering - Critical Systems

0.0(0)
studied byStudied by 2 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/42

flashcard set

Earn XP

Description and Tags

Flashcards about critical systems, dependability, and security.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

43 Terms

1
New cards

Safety-critical systems

Failure results in loss of life, injury or damage to the environment

2
New cards

Mission-critical systems

Failure results in failure of some goal-directed activity

3
New cards

Business-critical systems

Failure results in high economic losses

4
New cards

System dependability

Reflects the user’s degree of trust in that system

5
New cards

Availability

The ability of the system to deliver services when requested

6
New cards

Reliability

The ability of the system to deliver services as specified

7
New cards

Safety

The ability of the system to operate without catastrophic failure

8
New cards

Security

The ability of the system to protect itself against accidental or deliberate intrusion

9
New cards

Repairability

Reflects the extent to which the system can be repaired in the event of a failure

10
New cards

Maintainability

Reflects the extent to which the system can be adapted to new requirements

11
New cards

Survivability

Reflects the extent to which the system can deliver services whilst under hostile attack

12
New cards

Error tolerance

Reflects the extent to which user input errors can be avoided and tolerated

13
New cards

System failure

An event that occurs when the system does not deliver a service as expected

14
New cards

System error

An erroneous system state that can lead to unexpected system behavior

15
New cards

System fault

A characteristic of a software system that can lead to a system error

16
New cards

Human error or mistake

Human behavior that results in the introduction of faults into a system

17
New cards

Fault avoidance

Techniques to minimize mistakes or trap them before they become system faults

18
New cards

Fault detection and removal

Verification and validation to detect and correct errors before the system goes into service

19
New cards

Fault tolerance

Run-time techniques to ensure system faults do not result in errors or failures

20
New cards

Safety

The system’s ability to operate without causing human injury, death, or damage to the environment

21
New cards

Primary safety-critical systems

Embedded software systems whose failure can cause hardware failure and directly threaten people

22
New cards

Secondary safety-critical systems

Systems whose failure results in faults in other systems which can threaten people

23
New cards

Accident (or mishap)

An unplanned event resulting in human death/injury, property/environmental damage

24
New cards

Hazard

A condition with the potential for causing or contributing to an accident

25
New cards

Damage

A measure of the loss resulting from a mishap

26
New cards

Hazard severity

Assessment of the worst possible damage from a hazard

27
New cards

Hazard probability

The probability of events occurring which create a hazard

28
New cards

Risk

Measure of the probability that the system will cause an accident

29
New cards

Hazard avoidance

Designing the system so that some classes of hazard cannot arise

30
New cards

Hazard detection and removal

Designing the system so that hazards are detected and removed before they result in an accident

31
New cards

Damage limitation

Including protection features to minimize the damage from an accident

32
New cards

Security

The system’s ability to protect itself from accidental or deliberate external attack

33
New cards

Exposure

Possible loss in a computing system, such as data damage or loss of time

34
New cards

Vulnerability

A weakness in a computer-based system that may be exploited

35
New cards

Attack

An exploitation of a system vulnerability, often from outside the system

36
New cards

Threats

Circumstances that have the potential to cause loss or harm

37
New cards

Control

A protective measure that reduces a system vulnerability

38
New cards

Denial of service

The system is forced into a state where normal services are unavailable or degraded

39
New cards

Corruption of programs or data

Programs or data are modified in an unauthorized way

40
New cards

Disclosure of confidential information

Confidential information is exposed to unauthorized individuals

41
New cards

Vulnerability avoidance

Designing the system so that vulnerabilities do not occur

42
New cards

Attack detection and elimination

Designing the system to detect and neutralize attacks on vulnerabilities

43
New cards

Exposure limitation

Designing the system to minimize the adverse consequences of a successful attack