1 / 13

Code/Design Inspections

Code/Design Inspections. Reference. Technical Report TR00.2763 June 10, 1976 Written by Michael E. Fagan Kingston Laboratory. Design Review. General survey of something in words Educational - a presentation of what has been done and what is planned. Design Inspection.

blossom-price
Download Presentation

Code/Design Inspections

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Code/Design Inspections

  2. Reference • Technical Report TR00.2763 June 10, 1976 • Written by Michael E. Fagan • Kingston Laboratory

  3. Design Review • General survey of something in words • Educational - a presentation of what has been done and what is planned

  4. Design Inspection • Thorough comparison of objectives vs design and test criterion to prove design • Scrutinize carefully, investigate, interrogate • All instructions addressed at least once during inspection

  5. Inspection Process • Planning • Participants designated • Schedules for inspection established • Participants briefed • Overview • For education, designer gives tutorial • Preparation • For education, inspectors prepare from distributed material

  6. Inspection Process Continued • Inspection • find errors not solutions • Inspection reader presents code • examine product against specifications • record errors • Rework • Allow time in schedule for rework • Must be complete and verified by moderator prior to start of next development phase

  7. Inspection Process Continued • Follow up • Moderator documents results in inspection report within 24 hours • Design change reports written • include results in database

  8. Moderator • Key person in successful inspection • Independent, capable, leader • Preserve objectivity • Increase integrity of inspection • Manage inspection team

  9. Moderator must counteract • Inability of participants to give/take criticism • Lack of enthusiasm for finding errors • Doing too much at one meeting • Arguments over style or technique • Author’s fear of management reprisal for errors

  10. Inspection Outline • Overview • Designer describes overall design • Designer describes detail design • Distribute design documentation to participants • Preparation • Participants “do their homework” to understand design, intent, and logic • Some errors found at this phase

  11. Inspection outline continued • Inspection • Every piece of logic covered • Every branch taken • Inspection team must find errors • Moderator controls meeting, inspection is to find not fix errors • Errors and severity documented by moderator

  12. Inspection outline continued • Rework • Errors found in inspection must be resolved by coder/designer • Follow up • Moderator ensures every error is resolved • TR states if >5% of material reworked, 100 % reinspection • <5%, moderator verifies rework or decides on reconvening of inspection team

  13. Successful approach to inspection process • Inspections limited to 2 hour sessions • Presenter of code not author • Objectivity • Programmer backup

More Related