Applying the Inspection Process

What Software Artifacts Are Candidates for Inspection?

• Software Requirements

• Software Designs

• Code

• Test Plans

Requirements 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?

Requirements 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.

Requirements Inspection Checklist

1. Do the requirements exhibit a clear distinction between functions and data?

2. Do the requirements define all the information that is to be displayed to the user?

3. Do the requirements address system and user response to error conditions?

4. Is each requirement stated clearly, concisely, and unambiguously?

Requirements Inspection Checklist (Cont’d)

5. Is each requirement testable?

6. Are there ambiguous or implied requirements?

7. Are there conflicting requirements?

8. Are there areas not addressed in the SRS that need to be?

9. Are performance requirements stated?

Requirements Inspection Checklist (Cont’d)

10. If the requirements involve complex decision chains, are they expressed in a form that facilitates comprehension?

11. Are requirements for performing software upgrades given?

12. Are there requirements that unnecessary level of design detail?

13. Are the real time constraints specified in sufficient detail?

Requirements Inspection Checklist (Cont’d)

14. Are the precision and accuracy of calculations specified

15. Is it possible to develop a thorough set of tests based on the information contained in the SRS? If not, what information is missing?

16. Are assumptions and dependencies clearly stated?

17. Does the document contain all information called out in the SRS outline?

Design 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?

Design 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.

Code 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?

Code 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).

Validation 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?

Validation 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.