ASQ CSQE Certified Software Quality Engineer Exam Practice Test

Answer : C

A Kiviat chart, also known as a radar or spider chart, is well-suited for presenting a summary view of a set of metrics that include an ideal value because:

Multi-Dimensional Data Representation: It allows for the visualization of multiple metrics simultaneously, each represented as an axis starting from the same point.

Comparison with Ideal Values: Ideal values can be plotted on the same chart, providing a clear visual comparison between actual performance and target goals.

Holistic View: This type of chart provides a comprehensive overview of performance across different metrics in a single, easily interpretable visual.

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 : C

Increased satisfaction among external stakeholders, such as customers, investors, and partners, has a direct impact on the organization's long-term success and sustainability. This is because:

Customer Loyalty: Satisfied customers are more likely to remain loyal, make repeat purchases, and recommend the organization to others.

Investor Confidence: Satisfied stakeholders, including investors, tend to have more confidence in the organization's management and future prospects, leading to increased investment and support.

Partnerships and Collaborations: Positive relationships with external stakeholders foster better business partnerships and collaborations, which can lead to new opportunities and growth.

Answer : D

Data owners are typically individuals or groups who have deep understanding and control over a specific set of data. They are well-versed in the context, nuances, and expected patterns of the data they manage. This in-depth knowledge allows them to:

Detect Anomalies: Because data owners understand what the data should look like under normal circumstances, they are more likely to spot inconsistencies or errors as data is being collected.

Increase Accuracy: By catching and correcting anomalies early in the data collection process, data owners can ensure that the data remains accurate and reliable.

Immediate Action: Anomalies can be addressed on the spot, reducing the time and effort required for post-collection data cleaning and correction.

Answer : A

For safety-critical software, it is crucial to specify how the system should react to accidents or hazardous conditions to mitigate risks and ensure safety. This type of requirement directly addresses safety concerns by defining specific actions that the system must take in response to potential safety issues.

'System Safety Engineering and Management' by Harold E. Roland and Brian Moriarty.

ISO/IEC 61508, which provides guidelines for the functional safety of electrical/electronic/programmable electronic safety-related systems.

Answer : D

Measuring the average time software performs without a problem in a production environment during regular business hours under usual workload is an example of the reliability attribute. Reliability is concerned with:

System Dependability: The probability that the software will function without failure under given conditions for a specified period.

Error-Free Operation: Ensuring continuous operation without interruptions.

Reliability is critical for user trust and satisfaction, ensuring that the software consistently meets performance expectations.

IEEE Standard for Software Reliability

Software Engineering: Theory and Practice by Shari Lawrence Pfleeger and Joanne M. Atlee

Answer : A

Concurrently developing software, where multiple developers work on different parts of the codebase simultaneously, requires more rigid version control. This is because:

Managing Changes: Ensuring that changes made by one developer do not conflict with changes made by another.

Maintaining History: Keeping a detailed record of modifications to understand the evolution of the codebase and to revert changes if necessary.

Robust version control systems (VCS) like Git facilitate concurrent development by managing branches, merges, and conflict resolution effectively.

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