1. Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent need for QA and removal can be supported by inspection Various software artifacts available at the end of the Software development can only be inspected and not tested. Various software artifacts available at the end of the Software development can only be inspected and not tested. Different degrees of inspection Different degrees of inspection

2. Generic inspection process Planning and preparation Planning and preparation Goals and objectives Software artifacts to be inspected Who are performing inspections Who else need to be involved What are the process, techniques and follow-up activities

3. Inspection or collection Corresponds to the execution of QA activities Corresponds to the execution of QA activities Inspection meeting Inspection meeting Focus on identifying faults in the software artifacts Focus on identifying faults in the software artifacts Record the inspection results Record the inspection results

4. Correction and follow up Faults to be corrected Faults to be corrected Design or code owner need to fix the design or code Design or code owner need to fix the design or code Follow up activity to verify the fix Follow up activity to verify the fix Close interaction between inspection technique and the inspection process. Close interaction between inspection technique and the inspection process.

5. Informal desk checks, reviews, and walkthroughs Informal desk checks refers to informal check and inspection of technical documents produced by oneself. Informal desk checks refers to informal check and inspection of technical documents produced by oneself. Reviews refer to informal check or inspection of technical documents produced by someone else. Reviews refer to informal check or inspection of technical documents produced by someone else. Focus should be on logical and technical problems Focus should be on logical and technical problems

6. Defect Detection Techniques Checklist based defect detection Checklist based defect detection Checklist for major features and functions Checklist for major features and functions In requirement and specification inspections. In requirement and specification inspections. Component in design inspections, data structures and data definitions. Component in design inspections, data structures and data definitions. Property based checklist Property based checklist Checklist for coding style and standard, conformance to development methodologies, coupling between different modules Checklist for coding style and standard, conformance to development methodologies, coupling between different modules

7. INSPECTIONS Quality improvement & cost reduction technique. Quality improvement & cost reduction technique. Design & code inspections Design & code inspections Cost effectiveness of the program Cost effectiveness of the program Fundamental Process and the requirement for inspections Fundamental Process and the requirement for inspections

8. INSPECTION PROCESS Primary Purpose: Primary Purpose: 1.Identify potential defects during preparation & validate. 2.Validate the fact that identified items are actual defects. 3.Record the existence of the defect. 4.Provide the record to the developer to use in making fixes

9. SECONDARY PURPOSE 1.To provide traceability of requirements to design. 2.To provide sound base for the next phase 3 To Increase programming quality. 4.To Increase product quality. 5.Lower life cycle cost. 6.To provide feel of program maintainability

10. INSPECTION PHASES Planning The moderator is responsible for the entire inspection process for the software product. 1.Assure the identification of team 2.Adequate preparation 3.Avaialability of material to be inspected and conformance to standard 4.Preparation of check list

11. PLANNING Determine the need for an overview Determine the need for an overview Place for inspection meeting Place for inspection meeting Schedule the time & place Schedule the time & place Serve a notice to all parties involved Serve a notice to all parties involved Assign the role of reader to a selected member of the inspection team Assign the role of reader to a selected member of the inspection team

12. PREPARATION At least five working days before the start of inspection meeting, the material must be provided. At least five working days before the start of inspection meeting, the material must be provided. Must not go exceed two hours. Must not go exceed two hours. Defects are recorded on inspection –defect log form. Defects are recorded on inspection –defect log form.

13. INSPECTION MEETING Defects are discussed and recorded. The moderator is responsible for proper conduct of the meeting. Verification of defects Verification of defects Defects are recorded by each team member, the defect type is noted & at the end of the inspection defects are counted. Defects are recorded by each team member, the defect type is noted & at the end of the inspection defects are counted. Must be limited to finding defects Must be limited to finding defects

14. REWORK The author correct the defects. The author correct the defects. Corrections are verified. Corrections are verified. Must discuss the corrections with moderator. Must discuss the corrections with moderator. May be recommended for further inspection. May be recommended for further inspection.

15. INSPECTION TYPES HIGH LEVEL DESIGN INSPECTION HIGH LEVEL DESIGN INSPECTION LOW LEEVEL DESIGN INSPECTION LOW LEEVEL DESIGN INSPECTION CODE INSPECTION CODE INSPECTION

16. HIGH LEVEL DESIGN INSPECTION During the high level design phase, overall design for a module function is produced. During the high level design phase, overall design for a module function is produced. For each function, the design specification will provide: For each function, the design specification will provide: 1. The source of design (new, other contract, etc) 2. A graphical presentation of the function allocation to hardware resources 3. A graphical presentation of function flow 4. A description of scheduling, timing, and synchornization 5. A definition of interfaces 6. The process of decomposition

17. HIGH LEVEL DESIGN INSPECTION 7. The design definition as follows: Retained modules: reference to the existing preliminary (i.e. high level) design specification, as applicable Retained modules: reference to the existing preliminary (i.e. high level) design specification, as applicable Modified modules: reference to the existing preliminary (i.e high level) design specification, where applicable, and a narrative description of the changes Modified modules: reference to the existing preliminary (i.e high level) design specification, where applicable, and a narrative description of the changes New modules: high level description of the interfaces and processing. New modules: high level description of the interfaces and processing.

18. LOW LEVEL DESIGN Low level reflects back on the overall design objectives. Key objectives considered in designing software are: Low level reflects back on the overall design objectives. Key objectives considered in designing software are: 1. Accuracy with high performance 2. Reliability and fault tolerance, enabling the system to continue to perform in the event of hardware intermittent failure or other unexpected occurences; 3. Flexibility to accommodate change and growth; 4. Easy testability and 5. That it be readily maintainable

19. KEY FEATURES OF LOW LEVEL DESIGN Detail design module is developed and inspections are held for all modules which meet any of the following criteria: 1. New module development; 2. Any change to the external interface or function of an existing module; 3. A structural change in an existing module; and 4. A 40 percent or greater change in the source lines of code in an existing module. This % presumes that the size requirements as specified in the military standards are adhered to. In the case of unrestricted module size, where the module is large, this percentage criterion may not be proper.

20. CODE INSPECTIONS A code inspection is held for all new codes or code from another task being modified to meet the requirements of the new task or contract. The code inspection is not performed until after there has been an error free compilation.

21. CODE INSPECTION CODE INSPECTION It serves the following purpose: 1. Verification that the code conforms to the requirements specification, design specification and interface design specification requirements for operational software. 2. Confirmation that the design has been correctly converted to the target language. 3. Early audit of code quality by the software developer’s peers. 4. Early detection of errors. 5. Verification that the code meets level to level module interface requirements.

22. INSPECTION DEFECT TYPES Design defect Design defect Logic defect Logic defect Syntax defect Syntax defect Standards defect Standards defect Data defect Data defect Interface defect Interface defect Return code/ message defect Return code/ message defect Requirements change defect Requirements change defect Performance improvement defect Performance improvement defect

23. Inspection Prerequisites A team of technically competent,trained inspectors A team of technically competent,trained inspectors A trained moderator A trained moderator Proper planning and distribution of material Proper planning and distribution of material Full preparation prior to the inspection meeting Full preparation prior to the inspection meeting Completely design or cleanly compiled code Completely design or cleanly compiled code Updated resource requirements Updated resource requirements

24. Responsibilities of the moderator Complete The SQE training course Complete The SQE training course Check the entry criteria Check the entry criteria Preview the material for conformance to standards Preview the material for conformance to standards Team size and mix is proper Team size and mix is proper Assure there are at least five days of preparation Assure there are at least five days of preparation

25. During inspection/After inspection Adequate attendance Adequate attendance Adequate preparation Adequate preparation Lead the inspection meeting Lead the inspection meeting Log defects Log defects Require re-inspection for major defects, Require re-inspection for major defects, specification changes, or greater then 50 defects per 1000 LOC

26. After Inspection Review results with the author Review results with the author Provide the manager with an estimate of rework completion data Provide the manager with an estimate of rework completion data Eliminate duplicate defect log entries and send summary to SQE Eliminate duplicate defect log entries and send summary to SQE Verify correction of all defect log entries Verify correction of all defect log entries Add completion notice and send copy to SQE Add completion notice and send copy to SQE

27. Responsibilities of Inspectors Attend the SQE training classes Attend the SQE training classes Thoroughly all material Thoroughly all material Assure understanding of function, consult author if necessary Assure understanding of function, consult author if necessary Record detected defects on inspection defect log form prior to inspection Record detected defects on inspection defect log form prior to inspection

28. Responsibilities of Manager Establish schedule Establish schedule Meet with moderator and author Meet with moderator and author Monitor individual inspection time Monitor individual inspection time Review SQE defect summary for defect trends and perform defect trends analysis Review SQE defect summary for defect trends and perform defect trends analysis