1) These are mathematical tools used to predict how likely a software program is to fail under certain conditions. Imagine them as calculators for software stability. a) Robust programming b) Recovery blocks c) software reliability models d) fault-tolerant 2) This is a coding style that emphasizes building strong and reliable software. It's like building a house that can withstand harsh weather. a) exception domain b) Robust programming c) software reliability models d) fault-tolerant 3) This refers to the typical, expected conditions under which the software is designed to operate. Think of it as the "normal" usage scenario. a) Recovery blocks b) standard domain c) threshold d) expected exception domains 4) This encompasses situations where the software encounters unexpected inputs or conditions that deviate from the standard domain. Imagine unexpected events happening while using the software. a) expected exception domains b) LPM (logarithmic Poisson execution time model) c) N-version programming d) exception domain 5) These are specific, anticipated exceptions that the developers can plan for and handle gracefully. Think of foreseeable problems that the software might encounter. a) Robust programming b) expected exception domains c) BM (basic execution time model) d) software reliability models 6) This is a limit or boundary for something. In this context, it refers to the level of errors the software can tolerate before experiencing a failure. Imagine a red line - if errors exceed this line, problems arise. a) Redundancy b) threshold c) exception domain d) standard domain 7) This means the software can continue functioning even when encountering errors or failures. Imagine a car with a spare tire - it can keep moving even if one tire gets a flat. a) fault-tolerant b) Redundancy c) expected exception domains d) BM (basic execution time model) 8) These are programming techniques that allow the software to automatically recover from errors and return to a working state. Imagine a self-healing mechanism for the software. a) BM (basic execution time model) b) Redundancy c) expected exception domains d) Recovery blocks 9) This involves creating multiple, slightly different versions of the same software and running them simultaneously. If one version fails, the others can still function. Think of having multiple teams building the same bridge design - at least one might be stable even if others have issues. a) standard domain b) LPM (logarithmic Poisson execution time model) c) fault-tolerant d) N-version programming 10) This is a specific software reliability model that estimates how long a program might take to execute based on basic calculations. Think of a simple equation to predict how long it takes to cook a meal. a) expected exception domains b) Recovery blocks c) N-version programming d) BM (basic execution time model) 11) Another software reliability model, this one uses a more complex formula considering factors like error occurrences to predict execution time and reliability. Imagine a more advanced recipe that considers factors like oven temperature and ingredient variations to predict cooking time and success. a) expected exception domains b) BM (basic execution time model) c) LPM (logarithmic Poisson execution time model) d) standard domain 12) It involves incorporating additional checks, calculations, or alternative code paths to handle unexpected situations. This increases the software's ability to cope with errors without failure, similar to having backup systems in software to compensate for potential problems. a) Redundancy b) N-version programming c) threshold d) Recovery blocks

Defensive Programming quiz

印刷
埋め込み

リーダーボード

表示スタイル

オプション

テンプレートを切り替える

自動保存: を復元しますか?