Software fault tree analysis is incorrect because its purpose is to demonstrate that the software will not cause a system to reach an unsafe state, and to discover what environmental conditions will allow the system to reach an unsafe state. Software fault tree analysis is often conducted on the program code but can also be applied at other stages of the life cycle process (for example, requirements and design). This analysis is not always applied to all the program code, only to the portion that is safety critical.
Software sneak analysis is incorrect because it is based on sneak circuit analysis, which is used to evaluate electrical circuitry—hence the name software sneak circuit analysis. Sneaks are the latest design conditions or design flaws that have inadvertently been incorporated into electrical, software, and integrated systems designs. They are not caused by component failure.
75. Which of the following provides an assessment of software design quality?
a. Trace system requirements specifications to system requirements in requirements definition documentation.
b. Trace design specifications to system requirements and system requirements specifications to design.
c. Trace source code to design specifications and design specifications to source code.
d. Trace system test cases and test data designs to system requirements.
76. When executed incorrectly, which of the following nonlocal maintenance and diagnostic activities can expose an organization to potential risks?
a. Using strong authenticators
b. Separating the maintenance sessions from other network sessions
c. Performing remote disconnect verification feature
d. Using physically separated communications paths
77. Which of the following factors is an important consideration during application system design and development project?
a. Software safety
b. Completing the project on schedule
c. Spending less than budgeted
d. Documenting all critical work
78. A software product has the
a. Loss of life
b. Loss of property
c. Loss of physical attributes
d. Loss of quality
79. A dangerous misconception about software quality is that:
a. It can be inspected after the system is developed.
b. It can be improved by establishing a formal quality assurance function.
c. It can be improved by establishing a quality assurance library in the system.
d. It is tantamount to testing the software.