A) inspection is the most formal review process
B) inspections should be led by a trained leader
C) managers can perform inspections on management documents
D) inspection is appropriate even when there are no written documents
E) inspection compares documents with predecessor (source) documents
A) re-testing is running a test again; regression testing looks for unexpected side effects
B) re-testing looks for unexpected side effects; regression testing is repeating those tests
C) re-testing is done after faults are fixed; regression testing is done earlier
D) re-testing uses different environments, regression testing uses the same environment
E) re-testing is done by developers, regression testing is done by independent testers
A) s = 4, t = 3, u = 2 and 5, v = 1
B) s = 4 and 5, t = 3, u = 2, v = 1
C) s = 1 and 5, t = 3, u = 2, v = 4
D) s = 5, t = 4, u = 3, v = 1 and 2
E) s = 4 and 5, t = 1, u = 2, v = 3
A) No, because they apply to development documentation
B) No, because they are normally applied before testing
C) No, because they do not apply to the test documentation
D) Yes, because both help detect faults and improve quality
E) Yes, because testing includes all non-constructive activities
A) An inspection is lead by the author, whilst a walkthrough is lead by a trained moderator.
B) An inspection has a trained leader, whilst a walkthrough has no leader.
C) Authors are not present during inspections, whilst they are during walkthroughs.
D) A walkthrough is lead by the author, whilst an inspection is lead by a trained moderator.
A) Reviews cannot be performed on user requirements specifications.
B) Reviews are the least effective way of testing code.
C) Reviews are unlikely to find faults in test plans.
D) Reviews should be performed on specifications, code, and test plans.
A) v & w are true, x, y & z are false
B) w, x & y are true, v & z are false
C) w & y are true, v, x & z are false
D) w is true, v, x, y & z are false
C) management review
D) post project review
A) setting up forms and databases
B) analysing metrics and improving processes
C) writing the documents to be inspected
D) time spent on the document outside the meeting
A) to find faults in the software
B) to prove that the software has no faults
C) to give confidence in the software
D) to find performance problems
A) To ascertain that each requirement is traceable to a business need
B) To ascertain that each requirement is both testable and uniquely identifiable
C) To ascertain that each requirement is traceable to a business need, testable, and uniquely identifiable
D) To ascertain that each requirement is uniquely identifiable
A Log defects.
B. Explain the documents to the participants.
C. Gather metrics.
D. Allocate the individual roles.
A. Deviations from standards,
B. Requirement defects,
C. Design defects,
D. Insufficient maintainability and incorrect interface specifications.
E. All of the above.
A. Identifying defects.
B. Fixing defects.
C. A. and B
D. None of the above
A. Open, Assigned, Fixed, Closed
B. Open, Fixed, Assigned, Closed
C. Assigned, Open, Closed, Fixed
D. Assigned, Open, Fixed, Closed
A. Eliminate some of the requirements that have not yet been implemented.
B. Add more engineers to the project to make up for lost work.
C. Ask the current developers to work overtime until the lost work is recovered.
D. Hire more software quality assurance personnel.
A. Inexpensive way to get some benefit
B. Find defects
C. Learning, gaining understanding, effect finding
D. Discuss, make decisions, solve technical problems
A. ii is true and i,iii,iv are false
B. i,iii,iv are true and ii is false
C. i,iii,iv are false and ii is true
D. iii is true and I,ii,iv are false
A. Explaining the objectives
B. Selecting the personnel, allocating roles.
C. Follow up
D. Individual Meeting preparations