- The main steps in defect resolution are Prioritization, Scheduling, Fixing, Reporting
Your answer:
True
False
- The scheduling of fixes should be based primarily on...
Your answer:
defect counts
the overall project schedule
defect priority
- Fixing a defect involves
Your answer:
the developers making and unit testing the fix
QA retesting the fix and validating it
regression testing surrounding the fix
QA reviewing scripts, test data, etc to see if updates need to be made
all of the above
- Which of the following are ways to use the defect log to drive process improvement?
Your answer:
Go back to the process which originated the defect and find out what caused it
go back to the validation steps in that phase and find out why it wasn't caught earlier
think about what other kinds of things might have been missed, given that this bug "snuck through"
look at the fix history of the bug to find out if it could have been handled more smoothly
all of the above
- the minimum requirements for a defect management process include all but which of these?
Your answer:
defect to risk mapping
defect prevention measures
defect discovery, naming, and resolution
process improvement
deliverable baselining
- reducing the impact of a risk, should it occur, is an effective way to minimize risk.
Your answer:
True
False
- Who should be invovled in prioritizing fixes for valid defects found during system testing?
Your answer:
QA
the users
the project team
Developers
- Which of the following techniques is not a common way to minimize expected risks?
Your answer:
Training and Education (both the workforce and the customers)
Ranking risks using Pareto voting
Defensive Code
Defensive Design
Quality Assurance, Methodology and Standards
- Which is cheaper, preventing defects or fixing them?
Your answer:
preventing
fixing
- Deliverable baselining is:
Your answer:
baselining at the end of each phase and keeping change control processes in place
not counting defects caught and fixed before your phase.
identifying key variables and defining standards for each
A and C only
A, B, and C
- Which of these is not a "best practice" for defect managment?
Your answer:
automate the capture and analysis of information wherever possible
strive to correct every reported defect before release
make defect management a risk-driven process
prevent defects or at least contain them within the phase they were discovered
use defect measurement to improve development
- Which of these is not a valid purpose for reporting defects?
Your answer:
to correct the defect
to report the status of the application
to gather statistics to help develop expectations on future projects
to improve the development process
to show test coverage
- A defect is "discovered" when
Your answer:
development acknowledges a reported defect
none of the above
a tester observes a failure
development begins to work a reported defect
a tester reports a defect
- ALE stands for
Your answer:
Annual Loss Expectation - a formula for judging risk
Acceptance Level Error - an error that was not caught until user acceptance testing
Audit Legal Effort - the amount of time billed to the project by the legal and audit staff
Assertion Loop Estimation - a measure of code complexity
- Which of these refers to the "cost" of the risk?
Your answer:
priority
severity
- When reporting a defect it is important to...
Your answer:
make sure it is reproducible, if possible
get it to the developer's attention promptly
attempt to analyze the cause of hte defect
B and C only
A, B, and C
- To estimate a risk's expected impact, you should...
Your answer:
estimate the expected frequency of the event and the amount of loss that would happen each time
try to put a dollar amount on it
confer with experts on the probability and severity of the risk
a and b only
all of the above
- Along with a short title for the defect and what phase it was found in, what other data should be part of the defect's "name"
Your answer:
priority, like Urgent, High, Medium, Low
severity, like Critical, High, Medium, Low
steps to reproduce the error
data used to reproduce the error
categorization, like Missing, Inaccurate, Incomplete, Inconsistent