fault tolerant systems Flashcards

1
Q

what is a function

A

a behavior or performance of a system

  • can be achieved via numerous systems
  • “perform as intended”
  • fxnl breakdown to separate staff
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

why fault tolerant systems

A
  • all systems have faults
  • we want Integrity, Reliability, Availability
  • consequences can range from operational to financial problems
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

FTS definition

A

can still proide fxn even in the presence of a limited number of faults

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

what is reliability

A

probaility of a system operating fault free at a given time

-gives MTBF

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

what is availability

A

degree of availbility to provide intended functinos

avail = MTBF/(MTBF + MTTR)

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

what is deterministic? when does it fail?

A

output can be predetermined given we know the input

system faults or
security breaches

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

how are aircraft manufacturers differentiated?

A

NOT safety (either is or isn’t)

  • TOC -> total cost of ownership (how much technical and financial means went into making product)
  • lastly is travel comfort
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

why do systems fail?

A
human error 
technical faults
    -hardware
    -software 
    -communiction

draw associated graphs

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

what is (initial) airworthiness?

A
  • def: an aircraft that receives a certification from an authority
  • part of national legislation -> many differ to larger countries
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

how do EASE, JAR, and FAA relate?

A

jar was joint of europe. THey modeled after FAR Part 25.
EASA formed recently (first is a350) with CS (certification Specification) -> also closely model for flying in several locations

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

what does CS Book 1 Subpart F Section 1309 do?

A

says system smust perform as intended

says potentially catastrophic systems failures must not be possible froma single fault

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

where is the table defining the probabilities for certain failure problem levels
as well as several definitions relating to probabilty of failures and fault tolerant systems

A

CS Part 25 Book 2 (gives AMC) Subpart F Section 1309

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

main task of DO 254

A

design assureance guidance for complex electronic hardware

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

main task of DO 178 C

A

software considerations in airbourne systems and equipment certifications

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

what is the basis of software qualification

A

high level spec -> (via driving) low level spec -> (via coding) source code -> (via compiling) executable (binary on H/W target)

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

what is required to show DAL A

A
  • complete robust performance on the proper hardware
  • full scope testing (complete unit tests)
  • s/w h/w segregation
17
Q

what does the DO-178C outline

A

objective, whether it is applicable to the given DAL, documents for how to reach it, and who it is controlled by.

18
Q

how often does the qualification process outlined in DO178C have to be completed?

A

every life cycle.

-can perform an impact analysis to show partitioning (of software and hardware) to reduce requlify

19
Q

elaborate on the software requirements process and software design process

A

high level requirements are derived from system requirements and further, derived high level requirements can be derived (not directly from system reqs). These are outlined in software requirements document

Low level requirements (and derived) LLR and specifications, functions, style etc derived from teh high level requirements. Decripbed in SDD.

20
Q

elab on software integration process

A

s/s integration: machine code from source code.

s/h machine code onto target computer

21
Q

what is redundancy

A

having more systems (functions, provisions) than needed to accomlish a task in fault-free operation

22
Q

what is the purpose of redundancy?

A
  • fault recognition (eg recording via BITE)
  • fault management (deal with fault)
    • fault correction (ex. channel coding)
    • fault mask (priority voting)
    • fault compensate (switching to another system potentially with less functionality)
23
Q

what is graceful degredation

A

switching to a system with less functionality when original is not working

24
Q

what purpuses of redundancy are possible with different levels?

A

simplex -> none (no detection of management)

duplex -> detect one fault

triplex -> detect two faults or mask/ compensate for one fault

25
Q

what is a common mode failure?

A

a failure that occurs in multiple redundancies from the same occurance.

26
Q

how can you avaid common mode failures

A

dissimilar redundancy

-sometimes defferent development cycles completely -> very costly.

27
Q

what are teh two basic methods of redundancy management

A
  • master/slave

- comand monitor

28
Q

explain master-slave principle of redundancy management

A

both fully capable. One is active(master). slave channel in stand-by mode
master send “good health signal” to slave. If not received, slave takes over.

29
Q

explain command monitor

A

onle comand can operate. Monitor checks command system and if disagreement, switch to another system.