Important ASQ CSQE Exam Questions

Answer: C

Explanation:

In a situation where a software quality engineer (SQE) identifies a critical flaw and the immediate superior decides to proceed despite the risk, the most appropriate next step is to discuss the issue with top management. This involves:

Documenting the Issue: Clearly outlining the flaw, its potential impact, and the SQE's objections.

Escalating the Concern: Bringing the issue to the attention of higher management levels who have the authority to reconsider the decision.

Focusing on Safety: Emphasizing the critical nature of the flaw, especially in a system used for monitoring critically ill patients.

This step ensures that the concerns are heard at the highest level, potentially preventing a decision that could endanger lives and the company's reputation.

'Software Quality Assurance: Principles and Practice' by Nina S. Godbole

IEEE Code of Ethics

Answer: B

Explanation:

Preventing or eliminating the causes of injury and damage is primarily aimed at addressing product liability. Product liability refers to the legal responsibility of a manufacturer or vendor to compensate for injury or damage caused by a defective product. By focusing on prevention and elimination of potential hazards, companies can mitigate the risk of lawsuits and claims related to product liability. This proactive approach ensures that products are safe for consumers and helps maintain the company's reputation and financial stability.

'Product Liability: Prevention, Practice and Process' by Gene R. Laczniak.

ISO 31000:2018 - Risk management.

Answer: C

Explanation:

Setting Goals: Before data can be effectively collected and utilized, it's essential to have clear goals. This ensures that the data collection process is aligned with the organization's objectives.

Importance of Goals: Establishing the data collection goal ensures that the team collects relevant and meaningful data, which can be analyzed to improve processes and products.

Sequential Process: After setting goals, the team can then determine what specific data to collect, how to collect it, and which metrics to report. This ensures a systematic approach to metrics program development.

Answer: C

Explanation:

When the requirements group does not control changes to software specifications, a basic requirement is to assign explicit responsibility for software configuration management (SCM) for each project. Here's why:

Clear Accountability: Assigning explicit responsibility ensures that someone is accountable for managing and controlling changes.

Consistency in Process: This ensures consistent application of SCM practices across different projects.

Improved Control: Clear responsibility helps in better monitoring and controlling changes, reducing the risk of unauthorized or untracked changes.

Policy Enforcement: Facilitates the enforcement of SCM policies and procedures, ensuring compliance and integrity of the project.

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

'Software Configuration Management Strategies and Rational ClearCase: A Practical Introduction' by Brian A. White.

Answer: A

Explanation:

Outsourcing is a business practice where a company hires an external organization to perform tasks, handle operations, or provide services. One key advantage of outsourcing is that it allows the primary company to focus its resources on its core competencies. By delegating non-core activities to external specialists, the company can concentrate on what it does best, thereby enhancing efficiency, innovation, and competitive advantage in its primary market.

'The Outsourcing Revolution' by Michael F. Corbett

IEEE Software Engineering Body of Knowledge (SWEBOK), Chapter on Software Engineering Management