ASQ CSQE Certified Software Quality Engineer Exam Practice Test

Answer : C

Configuration Status Accounting (CSA) involves recording and reporting the status of configuration items throughout the lifecycle of a project. This includes:

Status of Configuration Items: Information about the current state of items, including version numbers and change histories.

Baselined Items: Items that have been formally approved and serve as a basis for further development.

Changes and Updates: Documenting any modifications made to the baselined items.

CSA ensures that all stakeholders are informed about the status and history of configuration items.

'Software Configuration Management Patterns: Effective Teamwork, Practical Integration' by Stephen P. Berczuk and Brad Appleton

IEEE Standard for Software Configuration Management Plans (IEEE Std 828)

Answer : B

A Pareto chart should be used to identify the steps in the development process that are the source of the most software defects. The Pareto chart is a bar graph that identifies the most significant factors in a dataset and is based on the Pareto principle (80/20 rule), which suggests that 80% of problems are often due to 20% of the causes. This tool helps in pinpointing the primary sources of defects so that improvement efforts can be focused effectively.

Juran, J. M., & Godfrey, A. B. (1999). Juran's Quality Handbook (5th Edition).

Montgomery, D. C. (2009). Introduction to Statistical Quality Control (6th Edition).

Answer : B

A static analysis tool is used to identify potential problems in the code without executing it. These tools analyze the source code to detect coding errors, vulnerabilities, and adherence to coding standards. By identifying issues early in the development process, static analysis helps prevent defects that could lead to significant problems later on. It is a proactive approach to improving code quality and maintaining robust software. Reference:

Ayewah, Nathaniel, et al. 'Using Static Analysis to Find Bugs.' IEEE Software, vol. 25, no. 5, 2008.

IEEE Std 1028-2008, IEEE Standard for Software Reviews and Audits.

Answer : C

Acquirer-type stakeholders are those who acquire the software or service, which typ

y includes both indirect and direct users, as well as customers. These stakeholders are directly involved in the acquisition and usage of the software, making them key participants in determining requirements and evaluating the final product.

Answer : B

The long-term success of a software subcontractor largely depends on customer satisfaction. Satisfied customers are more likely to provide repeat business, positive referrals, and long-term contracts. While profit margin, productivity levels, and technology trends are also important, they are often secondary to maintaining strong, positive relationships with customers.

'Customer Satisfaction Measurement for ISO 9000: 2000' by Bill Self

'The Loyalty Effect: The Hidden Force Behind Growth, Profits, and Lasting Value' by Frederick F. Reichheld

Answer : D

Open Source Software (OSS) offers many benefits, such as cost savings and community support. However, it also presents challenges:

Frequent Updates: OSS often undergoes frequent updates and changes, which can be difficult to track and implement, especially in a production environment.

Compatibility Issues: New versions of OSS may introduce changes that are not backward compatible, leading to potential integration and functionality issues.

Maintenance Burden: Organizations using OSS need to dedicate resources to keep up with these updates to ensure security and functionality.

Answer : A

Software cost estimation models, such as COCOMO (Constructive Cost Model), commonly use 'Lines of Code (LOC)' as a primary input. LOC is a measure of the size of a software program by counting the number of lines in the source code. This metric is essential for estimating the amount of effort and time required to develop the software. Other inputs may include function points and other metrics, but LOC remains a fundamental component in many models. Reference: Barry W. Boehm's 'Software Engineering Economics'.