Software Testing and Quality Control

It forces the software to fail in a variety of ways and verifies that regaining is properly performed.

It attempts to verify that protection mechanism built into a system will in fact protect it from improper penetration.

It begins at the vortex of the spiral and concentrates on each phase of the software as implemented in source code.

It is the most common and efficient method for isolating the cause of a software error.

Fault detection is a process of detecting the faults before the software is put into operation.

Software reliability is a function of the number of failures experienced by a particular user of the software.

Software reuse involves reusing existing components rather than developing them especially for an application.

Fault tolerance strategy assumes that residual faults remain in the system. Facilities are provided in the software to allow operation to continue when these faults cause system failures.

Operation generalization involve adding operations to a component or removing operations, which are very specific to some application domain.

Exception generalization may involve checking each component to see which exception it might generate and including these exceptions in the component interface.

White-box testing is also called as glass-box testing.

Top-down testing tests the high levels of a system before testing its detailed components.

Back-to-back testing is used when more than one version of a system is avaliable for testing.

Penetration testing is conducted to identify vulnerabilities in systems that need to be tested. It helps discover security weaknesses before malicious actors can exploit them. Option A is incorrect because it is not just for management awareness, and option B refers to testing detection systems rather than identifying targets.

The regression test suit contains tests that focus on software components that have been changed.