Quiz 7 Flashcards
The impact of software defects is always trivial.
F
Software quality is the degree to which a software product meets the needs of its users.
T
A primary cause of poor software quality is that developers do not know how to design quality into software from the very start, or do not take the time to do so.
T
When software is well-designed, programmers make no mistakes in turning design specifications into lines of code.
F
When forced to choose between adding more user features and doing more testing, most software companies decide in favor of more testing.
F
The first release of a software product typically meets all its users’ expectations.
F
Software defects are commonly lethal and many personal injuries are related to software failures.
F
Software product liability claims are typically based on strict liability, negligence, breach of warranty, or misrepresentation.
T
There is no federal product liability law.
T
Under the doctrine of supervening event, the original seller is not liable if the software was materially altered after it left the seller’s possession and the alteration caused the injury.
T
Software suppliers attempt to limit their liability by specifying that although software is warranted to run on a given machine configuration, no assurance is given as to what that software will do.
T
A successful defense against a product liability case is typically expensive in terms of legal fees.
T
In integration testing, special software programs called static analyzers are run against the new code.
F
User acceptance testing is performed by trained end users to ensure that the system operates as they expect.
T
Capability Maturity Model Integration (CMMI) is a process improvement approach that defines the essential elements of effective processes.
T
From 2007 to June 2016, the percentage of organizations determined to be at a high-maturity level is 50.
F
When developing safety-critical systems, a key assumption must be that safety will automatically result from following an organization’s standard development methodology.
F
Risk analysis is important for safety-critical systems, but is useful for other kinds of software development as well.
T
Software developers do not typically work closely with safety and software engineers.
F
In the context of developing safety-critical systems, the safety engineer’s role is limited to producing a hazard log.
F
Black-box testing treats the software unit as a device that has expected input and output behaviors but whose internal workings are known.
F
Risk is the potential of gaining or losing something of value.
T
Risk mitigation involves the reduction in either the likelihood or the impact of the occurrence of a risk.
T
Transference is the provision of multiple interchangeable components to perform a single function in order to cope with failures and errors.
F
