Which of the following activities is classified as data collection and storage?
Data collection and storage activities are focused on ensuring that the data is adequate, unique, and consistent. This involves:
Adequacy: Ensuring that the collected data meets the necessary requirements for its intended use.
Uniqueness: Verifying that the data is not duplicated and is uniquely identifiable.
Consistency: Ensuring that the data is consistent across different datasets and over time.
These activities are critical for maintaining the integrity and reliability of the data, which is essential for effective data analysis and decision-making.
'Data Quality: The Accuracy Dimension' by Jack E. Olson
'Data Management for Researchers' by Kristin Briney
From the auditor's perspective, which of the following actions will result in a successful internal audit?
A successful internal audit depends significantly on obtaining management's cooperation and support. This ensures that the audit findings and recommendations are taken seriously and that there is a commitment to implementing necessary changes. Reporting deficiencies, completing checklist items, and recommending corrective actions are important, but without management support, these actions may not lead to effective improvements. Reference: 'The Internal Auditing Handbook' by K.H. Spencer Pickett.
The following graphs illustrate the arrival rate and current status of software defects during system test. Which of these graphs indicates a product that is most ready for formal release to the customer?
A)
B)
C)
D)
Graph Analysis: In the provided graphs, each graph represents the status of defects over time, divided into categories: Open, Fixed, and Tested and Closed.
Option A: Shows a large number of open and fixed defects with fewer tested and closed defects.
Option B: Indicates an increasing trend in tested and closed defects but still has a substantial number of open defects.
Option C: Shows a significant decrease in open defects and a substantial increase in tested and closed defects, indicating progress.
Option D: Depicts the fewest number of open defects, with the majority of defects tested and closed, indicating that most defects have been addressed and verified.
Conclusion: The graph in Option D, with the majority of defects tested and closed and the fewest number of open defects, suggests the product is most ready for formal release to the customer. This aligns with software quality assurance principles where minimal unresolved defects indicate readiness for release.
During the design review of several sections (modules) of software, the reviewers find an unusually high number of defects After defect correction and testing, which of the following can be expected of these sections?
When a section of the software has an unusually high number of defects, even after correction and testing, it is likely that these sections might still contain additional defects. This is based on the defect clustering principle, which suggests that defects tend to cluster in certain modules of the software. Consequently, these sections require more thorough testing and scrutiny to ensure all defects are identified and resolved.
It is unrealistic to assume that these sections will be free of defects after initial corrections. They often need more comprehensive testing and more detailed test documentation to track and manage the corrections and any subsequent issues that may arise.
'Software Testing Techniques' by Boris Beizer.
'The Art of Software Testing' by Glenford J. Myers.
A sprint started with 354 requirements. As the sprint progressed, 14 requirements were introduced, 6 requirements were removed, and 28 requirements were changed. What was the requirements volatility for this sprint?
Requirements volatility is calculated as the percentage of change in the total number of requirements during a sprint. The formula to calculate volatility is:
Volatility=(Introduced+Removed+Changed)Initial100\text{Volatility} = \frac{(\text{Introduced} + \text{Removed} + \text{Changed})}{\text{Initial}} \times 100Volatility=Initial(Introduced+Removed+Changed)100
Using the given data:
Initial requirements = 354
Introduced = 14
Removed = 6
Changed = 28
Volatility=(14+6+28)35410013.5%\text{Volatility} = \frac{(14 + 6 + 28)}{354} \times 100 \approx 13.5\%Volatility=354(14+6+28)10013.5%
'Agile Estimating and Planning' by Mike Cohn, which explains the concept of requirements volatility in agile projects.
