Title: Applying the Inspection Process
1Applying the Inspection Process
2What Software Artifacts Are Candidates for
Inspection?
- Software Requirements
- Software Designs
- Code
- Test Plans
3Requirements InspectionObjectives
- Is each requirement in the SRS consistent with
and traceable to the document that preceded it
(if any)? - Is the SRS complete?
- Is each requirement in the SRS clear, concise,
internally consistent, unambiguous, and testable? - Are we building the right product?
4Requirements InspectionPrerequisites
- All inspection team members received inspection
process training. - The document, if any, that preceded the SRS has
been reviewed and approved. - The SRS has been internally reviewed.
- A Requirements Inspection Checklist is available.
5Requirements Inspection Checklist
- Do the requirements exhibit a clear distinction
between functions and data? - Do the requirements define all the information
that is to be displayed to the user? - Do the requirements address system and user
response to error conditions? - Is each requirement stated clearly, concisely,
and unambiguously?
6Requirements Inspection Checklist (Contd)
- Is each requirement testable?
- Are there ambiguous or implied requirements?
- Are there conflicting requirements?
- Are there areas not addressed in the SRS that
need to be? - Are performance requirements stated?
7Requirements Inspection Checklist (Contd)
- If the requirements involve complex decision
chains, are they expressed in a form that
facilitates comprehension? - Are requirements for performing software upgrades
given? - Are there requirements that unnecessary level of
design detail? - Are the real time constraints specified in
sufficient detail?
8Requirements Inspection Checklist (Contd)
- Are the precision and accuracy of calculations
specified - Is it possible to develop a thorough set of tests
based on the information contained in the SRS?
If not, what information is missing? - Are assumptions and dependencies clearly stated?
- Does the document contain all information called
out in the SRS outline?
9Design Inspection Objectives
- Does the design address all of the requirements
of the SRS? - Are all design elements traceable to specific
requirements contained in the SRS? - Does the design conform to project and company
standards? - Are we building the product correctly?
10Design Inspection Prerequisites
- The SRS has been inspected and all follow-up
actions completed. - The Design Document has been internally reviewed.
- A Design Inspection Checklist is available (see
Appendix D of the text) - If the design is done using CASE tool, relevant
reports and diagrams from such tools should be
made available.
11Code Inspection Objectives
- Is the code consistent with the design as
expressed in the Design Document. - Is the code traceable to specific design elements
identified in the Design Document? - Does the code conform to project and company
coding standards? - Are we building the product correctly?
12Code Inspection Prerequisites
- The Design Document has been inspected and all
follow-up actions completed. - The code has been compiled with no errors (and
possible been checked by a static code analyzer). - A Code Inspection Checklist is available (see
Appendix D of the text).
13Validation Test Plan Inspection Objectives
- Do the validation tests accurately reflect the
requirements defined in the SRS? - Have validation tests taken advantage of
knowledge of the design where appropriate? - Is the project ready to enter the validation
testing phase?
14Validation Test Plan Inspection Prerequisites
- The test have been reviewed internally and
executed at least once. - A Test Procedure Inspection Checklist is
available (see Appendix D of the text). - Every test has an expected result.
15(No Transcript)