Software Reviews Walkthroughs and Inspections The standard technique
- Slides: 19
Software Reviews, Walkthroughs, and Inspections The standard technique to ensure quality in software development reviews 8 1
Question u What is the title of the chapter in which the material about software reviews is found? – A. SQA – B. Testing – C. Software Design reviews 8 2
Question u What do software reviews do to software? – A. correct – B. purify – C. disinfect – D. clarify reviews 8 3
Review – two definitions A formal, scheduled activity where a designer presents material about a design and a selected group of peers evaluates the technical aspects of the design. u The inclusive name for reviews, walkthroughs, and inspections u reviews 8 4
Types of Reviews u Reviews – – Requirement (SRR) Design (PDR, CDR) u Walkthroughs u Inspections – – reviews 8 Code Document 5
Walkthrough u. A formal, scheduled activity where a designer presents a design and traces the values of sample data through the design and a selected group of peers evaluates the technical aspects of the design. reviews 8 6
Inspection u. A formal, scheduled activity where a specialist checks a document for conformity with established standards (often corporate standards) reviews 8 7
540 -541 REVIEWS u Professionalism is graded on quality of effort, – professionalism, and – following standards u Materials in advance u Points will be taken off u TA and Instructor for not correcting serve as evaluators problems u Usually 50 minutes – reviews 8 be prepared be organized present good image u Team 8
Procedures for Reviews The evaluators prepare for the review by studying the prepared documents. u A formal report on the review is often required by management. u reviews 8 9
Conduct of Reviews 1 2 3 4 5 6 reviews 8 schedule review distribute materials prepare present discuss report 10
Rules for Reviews – – – – reviews 8 proper constructive attitude proper preparation proper environment no management participants should be participants producers should determine time distribute reports fast record all issues in public 11
Rules for Reviewers – – – reviews 8 prepare be friendly watch comments one positive comment, one negative raise issues, don't solve them – – – avoid style issues stick to standards stick to technical issues make certain that everybody understands do not evaluate producers 12
An Example Presentation 1 reviews 8 13
Purpose of Reviews u ensure quality through peer review u provide management visibility u encourage preparation reviews 8 14
Defect Amplification u Undetected defect “amplify” during subsequent phases u Figure 8. 2 - 8. 4 reviews 8 15
Peer Review u the primary function is to use the skill of a group of people to: – – reviews 8 1) identify needed improvements 2) certify correctness 3) encourage uniformity 4) enforce subjective rules 16
Management u secondary functions include: » » » reviews 8 1) communication 2) milestone 3) visibility to management 17
Progress u reviews 8 additional function (and not the least) is to force preparation of materials and specification (both meanings) of ideas. 18
Next Tuesday, 9/24/02 u Read about derived classes in C++ book u Stroustrup, ch 12 reviews 8 19
- Walkthroughs in software testing
- Instructional walkthroughs
- Difference between inspection and audit
- Example of unplanned inspection
- Medical equipment inspection
- Ellis island inspections
- Csh inspections
- Bridge column inspections
- Improve software economics
- Rigid inspections
- "sps inspections"
- Fvo inspections
- Cmha housing choice voucher
- Retroreflectivity inspections
- Mock osha inspections
- Max payne
- Eic software reviews
- Standard error formula
- Standard language examples
- Meaning of standard costing