Software Reliability and Fault Tolerance

A. Available Dependability
B. Confidential Dependability
C. Maintainable Dependability
D. Integral Dependability

Explanation: Integrity is to keep the original content safe from alteration.

A. Integrity
B. Dependability
C. Redundancy
D. None of the mentioned

Explanation: All fault-tolerant techniques rely on extra elements introduced into the system to detect & recover from faults.

A. Hardware checks
B. Timing checks
C. Reversal checks
D. Coding checks

Explanation: Hardware is a part of environment detection check.

A. Fault prevention
B. Fault removal
C. Fault tolerance
D. All of the mentioned

Explanation: All the options lead to formation of a reliable system.

A. greater than 1
B. less than 1
C. greater than 2
D. less than 2

Explanation: N-version programming (NVP), also known as multiversion programming or multiple-version dissimilar software, is a method or process in software engineering where multiple functionally equivalent programs are independently generated from the same initial specifications.

A. Static
B. Dynamic
C. Domino
D. Whirlpool

A. Full Fault Tolerance
B. Graceful Degradation
C. Fail Soft
D. Fail Safe

A. Permanent
B. Transient
C. Intermittent
D. All of the mentioned

Explanation: For example many faults in communication systems are transient in nature.

A. Non Homogeneous Poisson Product
B. Non-Hetrogeneous Poisson Product
C. Non-Hetrogeneous Poisson Process
D. Non Homogeneous Poisson Process

A. Reliability
B. Efficiency
C. Functionality
D. Usability

Explanation: All the Characteristics mentioned in the question are related to achievement of the basic purpose for which the software is being engineered, which is functionality.