Software safety is quality assurance activity that focuses on hazards that
may cause an entire system to fail.
Software safety is a software quality assurance (SQA) activity. Pressman describes it as the identification and assessment of potential hazards that may affect software negatively and cause an entire system to fail. It matters most for embedded and safety-critical systems such as avionics, medical devices and process control, where a software fault can lead to loss of life or property.
The activity works in two stages: early in the process, hazards are identified and analysed using techniques such as fault-tree analysis; then safety-related requirements are specified so that the design either removes the hazard or keeps its consequences within acceptable limits.
Why the other choices do not describe it: hazards that merely affect the reliability of one software component are the subject of software reliability analysis, which measures failure probability rather than system-level danger; user input errors are one possible cause of a fault, not the defining focus of safety analysis; and hindering profitable marketing is a business risk handled in risk management, not a safety hazard.
may cause an entire system to fail option is correct.
Similar Questions
Maximum possible value of reliability is
Which one of the following is not a source code metric ?
In software testing, how the error, fault and failure are related to each other ?
Which design metric is used to measure the compactness of the program in terms of lines of code ?
Verification :
In which testing strategy requirements established during requirements analysis are validated against developed software ?
Which one of the following is not a definition of error ?
Assume that a program will experience 200 failures in infinite time. It has now experienced 100 failures. The initial failure intensity was 20 failures/CPU hr. Then the current failure intensity will be
Software testing is
Regression testing is primarily related to
Important Questions from Software Testing
Equivalence partitioning is a ______.
What is the other name of White-box testing?
- Arrange the following types of testing in the order they are usually performed in the software Development life cycle.
A. Integration testing
B. Unit testing
C. System Testing
D. Acceptance Testing
Choose the correct answer from the options given below: - Assertion(A):Rubber necking might be called non generative pattern
Reason(R): Non generative pattern describes a content and a problem but it does not provide any clear cut solution. - Which method can be applied to problems in which the input domain is relatively small but too large to accommodate exhaustive testing?
