.
Design
Test cases
Requirements
Program code
Walk through
State transition testing
Decision table testing
Statement testing
Champion
Author
Project sponsor
Custodian
(i) and (v) are correct
(ii) and (iii) are correct
(i) and (iv) are correct
(iii) and (iv) are correct
Kick-off, review meeting, planning, follow-up
Kick-off, planning, review meeting, re-work
Planning, kick-off, individual preparation, review meeting
Planning, individual preparation, follow-up, re-work
(i), (ii), (vi)
(ii), (iii), (v)
(i), (iv), (v)
(i), (iii), (v)
Deviations from standards
Requirement defects
Design defects
Insufficient maintainability and incorrect interface specifications
All of the above
(i), (iii) & (iv) are true: (ii) & (v) are false
(iii) is true: (i), (ii), (iv) & (v) are false
(iii) & (iv) are true: (i), (ii) & (v) are false
(i), (iii), (iv) & (v) are true: (ii) is false
(i) & (iii) are true: (ii), (iv) & (v) are false
The use of a variable before it has been defined
Unreachable (dead) code
Whether the value stored in a variable is correct
The re definition of a variable before it has been used
Array bound violations
Inspection is most formal review process
Inspections should be lead by trained leaders
Managers can perform inspections on management documents
Inspection is appropriate even when there are no written documents
Inspections compare documents with source documents
Is not important
Increases as we move the move the product towards live use
Decrease as we move the move the product towards live use
d. Is more expansive if found in requirements than functional design
Can’t be determined
No, because they apply to development document
No, because they are normally applied before testing
No, because they don’t apply to the test documentation
Yes, because both help detect faults and improve quality
Yes, because testing includes all non-constructive activities
Static analysis tools are used only by developers
Compilers may offer some support for static analysis
Static analysis tools help find failures rather than defects
Static analysis tools require execution of the code to analyze of the code to analyze the coverage
A walkthrough does not allow a defined process
For a walkthrough individual preparation by the reviewer is optional
A Walkthrough requires meeting
A Walkthrough finds the cause of the failures while formal review finds the failure
When the code is complete
When the design is complete
When the software requirement have been approved
When the first code modules are ready for unit testing
Takes a minute of the meeting
Mediates between people
Takes a telephone calls
Writes the documents to be reviewed
Enable the code to be tested before the execution environment is ready
Can be performed by the person who wrote the code
Can be performed by inexperienced staff
Are cheap to perform
Faults in program specifications are the most expansive to fix
Faults in code are the most expensive to fix
Faults in requirements are the most expansive to fix
Faults in design are the most expansive to fix
Code inspection
Coverage Analysis
Usability Assessment
Installation test
The analysis of batch programs
The reviewing of test plans
The analysis of program code
The use of black box testing
Reviews cannot be performed on user requirements specifications
Reviews are the least effective way of testing code
Reviews are unlikely to find faults in test plans
Reviews should be performed on specifications, code, and test plans
Because they share the aim of identifying defects and find the same types of defect
Because they have different aims and differ in the types of defect they find
Because they have different aims but find the same types of defect
Because they share the aim of identifying defects but differ in the types of defect they find
i, ii, vi
Ii, iii, v
i, iv, v
i, iii, v
Same as static testing
Done by the developers
Both A and B
None of the above
I, II and IV
I, II and III
I, II, III and IV
II, III and IV
Moderator
Author
Reviewer
Recorder
S = 4, t = 3, u = 2 and 5, v = 1
S = 4 and 5, t = 3, u = 2, v = 1
S = 1 and 5, t = 3, u = 2, v = 4
S = 5, t = 4, u = 3, v = 1 and 2
S = 4 and 5, t = 1, u = 2, v = 3
S = 4 and 5, t = 1, u = 2, v = 3
Inspection is the most formal review process
Inspections should be led by a trained leader
Managers can perform inspections on management documents
Inspection is appropriate even when there are no written documents
Inspection compares documents with predecessor (source) documents
I, II and IV
I and III
III and IV
I, III and IV
Moderator
Scribe
Reviewers
Author
Formal inspection
Dynamic testing
Code walkthrough
Execution testing
Supporting reviews
Validating models of the software
Testing code executed in a special test harness
Enforcement of coding standards
Deviations from standards
Requirement defects
Design defects
All of the above
Identifying defects
Fixing defects
A and B
None of the above
Planning, Review meeting, Rework, Kick off
Planning, Individual preparation, Kick off, Rework
Planning, Review meeting, Rework, Follow up
Planning, Individual preparation, Follow up, Kick off
1 and 3 are true. 2 and 4 are false
2 is true. 1, 3 and 4 are false
2 and 3 are true. 1 and 4 are false
2, 3 and 4 are true. 1 is false
I,ii,iii,iv are true
i,ii,iii are true and iv is false
Ii,iii,iv are true and i is false
i,iv are true and ii, iii are false
L, M, N and O
L and N
L, N and O
L, M and N
ii,iii,iv are correct and i is incorrect
iii , i , iv is correct and ii is incorrect
I , iii , iv , ii is in correct
Ii is correct
I , ii,iii,iv is correct
iii ,is correct I,ii,iv are incorrect
I ,ii, iii and iv are incorrect
Iv, ii is correct
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.