Read the following text to answer item.

Software engineering fundamentals

As long as software quality (reliability and availability attributes in particular) remains suspect, there will be a reluctance to use software in safety-critical applications involving a high cost of failure. However, there is also strong pressure from other quarters to use software in critical applications because of cost and technical advantages; this pressure drives software developers to find ways to produce software with a high reliability.

Safety considerations are also the domain of quality assurance. Some of the tools employed in software safety analyses include failure modes and effects analysis (FMEA), fault tree analysis, event tree analysis, hazard analysis, and Petri nets. Usually these analyses include comprehensive models of hardware, software, and operator performance.

The objective of FMEA is to analyze an information system’s components systematically to determine how a component might fail and evaluate the effect of such a failure on system performance under a variety of operational conditions. The objective is to identify ways in which combinations of external events, operator reactions, and/or hardware/software failures can lead to serious failure consequences. Some analytical approaches (fault tree analysis or event tree analysis, for example) begin by assuming the occurrence of a catastrophic failure and working backwards to find out what logical sequence of events would result in such a failure.

A. Behforooz and F. J. Hudson. Software engineering fundamentals.

Oxford University Press, Inc., 1996, p. 554 (with adaptations).

In the text above “comprehensive” means covering completely or broadly.

Read the following text to answer item.

Software engineering fundamentals

As long as software quality (reliability and availability attributes in particular) remains suspect, there will be a reluctance to use software in safety-critical applications involving a high cost of failure. However, there is also strong pressure from other quarters to use software in critical applications because of cost and technical advantages; this pressure drives software developers to find ways to produce software with a high reliability.

Safety considerations are also the domain of quality assurance. Some of the tools employed in software safety analyses include failure modes and effects analysis (FMEA), fault tree analysis, event tree analysis, hazard analysis, and Petri nets. Usually these analyses include comprehensive models of hardware, software, and operator performance.

The objective of FMEA is to analyze an information system’s components systematically to determine how a component might fail and evaluate the effect of such a failure on system performance under a variety of operational conditions. The objective is to identify ways in which combinations of external events, operator reactions, and/or hardware/software failures can lead to serious failure consequences. Some analytical approaches (fault tree analysis or event tree analysis, for example) begin by assuming the occurrence of a catastrophic failure and working backwards to find out what logical sequence of events would result in such a failure.

A. Behforooz and F. J. Hudson. Software engineering fundamentals.

Oxford University Press, Inc., 1996, p. 554 (with adaptations).

In the text above “high” is synonymous with tall.

Read the following text to answer item.

Software engineering fundamentals

As long as software quality (reliability and availability attributes in particular) remains suspect, there will be a reluctance to use software in safety-critical applications involving a high cost of failure. However, there is also strong pressure from other quarters to use software in critical applications because of cost and technical advantages; this pressure drives software developers to find ways to produce software with a high reliability.

Safety considerations are also the domain of quality assurance. Some of the tools employed in software safety analyses include failure modes and effects analysis (FMEA), fault tree analysis, event tree analysis, hazard analysis, and Petri nets. Usually these analyses include comprehensive models of hardware, software, and operator performance.

The objective of FMEA is to analyze an information system’s components systematically to determine how a component might fail and evaluate the effect of such a failure on system performance under a variety of operational conditions. The objective is to identify ways in which combinations of external events, operator reactions, and/or hardware/software failures can lead to serious failure consequences. Some analytical approaches (fault tree analysis or event tree analysis, for example) begin by assuming the occurrence of a catastrophic failure and working backwards to find out what logical sequence of events would result in such a failure.

A. Behforooz and F. J. Hudson. Software engineering fundamentals.

Oxford University Press, Inc., 1996, p. 554 (with adaptations).

In the text above “to use” is the same as to wear.

Read the following text to answer item.

Software engineering fundamentals

As long as software quality (reliability and availability attributes in particular) remains suspect, there will be a reluctance to use software in safety-critical applications involving a high cost of failure. However, there is also strong pressure from other quarters to use software in critical applications because of cost and technical advantages; this pressure drives software developers to find ways to produce software with a high reliability.

Safety considerations are also the domain of quality assurance. Some of the tools employed in software safety analyses include failure modes and effects analysis (FMEA), fault tree analysis, event tree analysis, hazard analysis, and Petri nets. Usually these analyses include comprehensive models of hardware, software, and operator performance.

The objective of FMEA is to analyze an information system’s components systematically to determine how a component might fail and evaluate the effect of such a failure on system performance under a variety of operational conditions. The objective is to identify ways in which combinations of external events, operator reactions, and/or hardware/software failures can lead to serious failure consequences. Some analytical approaches (fault tree analysis or event tree analysis, for example) begin by assuming the occurrence of a catastrophic failure and working backwards to find out what logical sequence of events would result in such a failure.

A. Behforooz and F. J. Hudson. Software engineering fundamentals.

Oxford University Press, Inc., 1996, p. 554 (with adaptations).

In the text above “to find out” means to obtain knowledge of something.

Read the following text to answer item.

Software engineering fundamentals

As long as software quality (reliability and availability attributes in particular) remains suspect, there will be a reluctance to use software in safety-critical applications involving a high cost of failure. However, there is also strong pressure from other quarters to use software in critical applications because of cost and technical advantages; this pressure drives software developers to find ways to produce software with a high reliability.

Safety considerations are also the domain of quality assurance. Some of the tools employed in software safety analyses include failure modes and effects analysis (FMEA), fault tree analysis, event tree analysis, hazard analysis, and Petri nets. Usually these analyses include comprehensive models of hardware, software, and operator performance.

The objective of FMEA is to analyze an information system’s components systematically to determine how a component might fail and evaluate the effect of such a failure on system performance under a variety of operational conditions. The objective is to identify ways in which combinations of external events, operator reactions, and/or hardware/software failures can lead to serious failure consequences. Some analytical approaches (fault tree analysis or event tree analysis, for example) begin by assuming the occurrence of a catastrophic failure and working backwards to find out what logical sequence of events would result in such a failure.

A. Behforooz and F. J. Hudson. Software engineering fundamentals.

Oxford University Press, Inc., 1996, p. 554 (with adaptations).

Based on the text above, judge the following item.

Serious failure consequences can be a combination of external factors and hardware/software failures.