Lecture – 2
Software Reliability
1. ------------ of a system is the probability, over a given period of time, that the system will
correctly deliver services as expected by the user.
(a) Availability (b) Reliability (c) Safety (d) Resilience
2. ------------ of a system is the probability that it will be up and running and able to deliver
useful services to users at any given time.
(a) Availability (b) Reliability (c) Safety (d) Resilience
3. ------------ of a system is a judgment of how likely it is that the system will cause damage to
people or its environment.
(a) Availability (b) Reliability (c) Safety (d) Resilience
4. ------------ of a system is judgment of how likely it is that the system can resist accidental or
deliberate intrusions.
(a) Security (b) Reliability (c) Safety (d) Resilience
5. ------------ of a system is judgment of how well that system can maintain the continuity of its
critical services in the presence of disruptive event.
(a) Security (b) Reliability (c) Safety (d) Resilience
6. ROCOF of ------- mean 10 failures are likely in each 1000 operational time units.
(a) 0.001 (b) 0.01 (c) 0.0001 (d) 0.1
7. MTBF of 200 hours indicates that once a failure occurs, the next failure is expected after
------- hours?
(a) 20 (b) 2000 (c) 2 (d) 200
8. Availability of 0.025 means software is available for ------- out of ------ time units.
(a) 25, 1000 (b) 25, 100 (c) 2.5, 1000 (d) 250, 1000
9. In 24-hour period, the term ‘the system is unavailable for 14.4 minutes’ is the same
availability of -------.
(a) 0.9 (b) 0.99 (c) 0.999 (d) 0.9999
10. Which of the following software reliability metric is relevant for a protection system that
monitors a chemical reactor?
(a) ROCOF (b) MTTF (c) MTTR (d) POFOD
11. Which of the following software reliability metric measures the likelihood of the system
failing when a service request is made?
(a) ROCOF (b) MTTF (c) MTTR (d) POFOD
12. Which of the following software reliability metric is relevant for systems with long
transactions?
(a) ROCOF (b) MTTF (c) MTBF (d) POFOD
13. --------- is the time between two successive failures, averaged over a large number of failures.
(a) MTTR (b) MTTF (c) MTBF (d) All of these
14. --------- of software as the probability of a user selecting the different functionalities of the
software.
(a) Functional Reliability Requirements (c) Reliability requirement
(b) Non-functional Reliability Requirement (d) Operational profile
15. --------- is a system architecture in which the system is designed to monitor its own operation
and to take some action if a problem is detected.
(a) Fault-tolerant architecture (c) Protection system architecture
(b) N-version programming architecture (d) Self-monitoring architecture
16. --------- is a specialized system that is suitable for the system on a diver less train.
(a) Fault-tolerant architecture (c) Protection system architecture
(b) N-version programming architecture (d) Self-monitoring architecture
17. --------- has been used for many years to build systems that are tolerant of hardware failures.
(a) Software diversity (b) TMR (c) Replicated server (d) All of these
18. The -------- of a software product basically represents its trustworthiness or dependability.
(a) availability (b) reliability (c) safety (d) resilience
19. The overall reliability of a diverse system is obtained by --------- the reliabilities of each
channel.
(a) subtracting (b) adding (c) multiplying (d) division
20. Which of the following guidelines are the good programming practices?
(a) Check array bounds (b) Check all inputs for validity
(c) Provide restart capabilities (d) All of these
1. Failure is nonconformance to software requirements, has degrees. T
2. If an error is removed from an instruction that is frequently executed, then a small
improvement to the product reliability. F
3. Reliability of a product depends not only on the number of latent errors but also on the exact
location of errors. T
4. The software reliability measurement depends on the observer-dependent. T
5. The failure rate of a hardware component show ‘bath tub’ diagram. T
6. The reliability of a software product increases almost linearly, each time a defect gets
detected and fixed. F
7. As testing continues, the rate of growth of reliability slows down representing a diminishing
return of reliability growth with testing effort. T
8. Modern quality assurance paradigms are centered on carrying out thorough product testing. F
9. Highly reliable software can be termed as good quality software. T
10. If sensors indicate a problem that the controlled system is not dealing with, then the
protection system can’t address this. F
11. In self-monitoring architectures, the system raises a failure exception on the status output
line. T
12. N-version programming architecture should be used in system which has a high level of
availability is required. T
13. Software reliability not depends upon how the product is used. F
14. Self-monitoring architecture may be used in system which its operation is correct, but where
availability is not essential. T
15. In situations that require high availability, you should not use self-monitoring architecture. F
16. Fault-tolerant architectures rely on software diversity. T
17. The diverse versions of the system should have dependencies. F
18. To reduce the possibility of common specification errors is to develop detailed specification
for the system by using different languages. T
19. Correction of one failure may in fact result in the introduction of other errors. T
20. Availability metric not only considers the number of failures occurring during a time interval,
but also takes into account the repair time of the system when a failure occurs. T
