Software Testing and Quality Management

A. Version Control
B. Access control
C. CM Process
D. Version Control and Access control

Explanation: It allows software engineers to continue development along a branch even when a line of development is frozen.

A. Log the changes
B. Estimate impact on effort and schedule
C. Review impact with stakeholders
D. None of the mentioned

Explanation: All are required for a change.

A. By reviews
B. By inspections
C. By testing of code
D. All of the mentioned

Explanation: Testing verifies the agreed-to description.

A. A compliant product
B. Good quality output
C. Delivery within budget and schedule
D. All of the mentioned

Explanation: This focuses on how well the implementation follows the design and how well the resulting system meets its requirements .

A. SCM procedures
B. Source code
C. Software design descriptions
D. All of the mentioned

Explanation: All are covered in CM.

A. Change Control Board
B. Change Control Baseline
C. Cumulative Changes in Baseline
D. None of the mentioned

A. Prevention
B. Internal Failure
C. External Failure
D. Appraisal

Explanation: Inspections, equipment calibration, maintenance and testing appraisal costs is quality management.

A. SQA
B. SQM
C. SQI
D. SQA and SQM

Explanation: Quality Management is also called software quality assurance (SQA. which serves as an umbrella activity that is applied throughout the software process.

A. Reasons for making the changes
B. A description of the proposed changes
C. List of other items affected by the changes
D. All of the mentioned

Explanation: A baseline is an agreed-to description of the product, changes require multiple reasons

A. 60, 40
B. 70, 30
C. 80, 20
D. No such principle exists

Explanation: The Pareto principle (also known as the 80–20 rulE. states that, for many events, roughly 80% of the effects come from 20% of the causes.