DOC PREVIEW
UMD CMSC 735 - Improving Software Inspections by Using Reading Techniques

This preview shows page 1-2-23-24 out of 24 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

5 Defining PBR5 Defining PBR3 Requirements 3 Requirements defectsdefectsContentsContentsSlide 17 The PBR “tester“ 7 The PBR “tester“ scenarioscenario1 Goals1 Goals2 Inspections:2 Inspections:Definition & DataDefinition & Data4 Reading techs4 Reading techsfor improvingfor improvinginspectionsinspections8 Discussion8 Discussion6 Applying PBR6 Applying PBRJeff CarverUniversity of MarylandForrest Shull, Victor BasiliFraunhofer Center for Experimental Software Engineering, MarylandJose Maldanado, Sandra FabbriCNPq/NSF Readers Project AffiliatesImproving Software Inspections by Using Reading Techniques5 Defining PBR5 Defining PBR3 Requirements 3 Requirements defectsdefectsContentsContentsSlide 27 The PBR “tester“ 7 The PBR “tester“ scenarioscenario1 Goals1 Goals2 Inspections:2 Inspections:Definition & DataDefinition & Data4 Reading techs4 Reading techsfor improvingfor improvinginspectionsinspections8 Discussion8 Discussion6 Applying PBR6 Applying PBRPretest• 10 Minutes• Pre-test, not part of your grade, used to gauge previous knowledge and experience• Each person received a requirements excerpt with two questions on the back • Read through the requirements, and then answer the two questions on a separate sheet of paper. (It is ok to look back at requirements when answering the questions.)• For question 1, note that each of the marked statements may or may not have a problem, so if you do not see a problem, then it is OK to indicate that the statement is correct.• For question 2, if you cannot write a test case or describe how you would test the requirement, then leave the answer blank.5 Defining PBR5 Defining PBR3 Requirements 3 Requirements defectsdefectsContentsContentsSlide 37 The PBR “tester“ 7 The PBR “tester“ scenarioscenario1 Goals1 Goals2 Inspections:2 Inspections:Definition & DataDefinition & Data4 Reading techs4 Reading techsfor improvingfor improvinginspectionsinspections8 Discussion8 Discussion6 Applying PBR6 Applying PBRContents• Goals• Inspections: Definition and data• Requirements defects• Reading: A key technical dimension of inspections• PBR: Reading techniques for requirements inspections– Defining the techniques– Applying the techniques– Example: the PBR “user” scenario• Application & discussion5 Defining PBR5 Defining PBR3 Requirements 3 Requirements defectsdefectsContentsContentsSlide 47 The PBR “tester“ 7 The PBR “tester“ scenarioscenario1 Goals1 Goals2 Inspections:2 Inspections:Definition & DataDefinition & Data4 Reading techs4 Reading techsfor improvingfor improvinginspectionsinspections8 Discussion8 Discussion6 Applying PBR6 Applying PBRGoalsThe primary goal of this class is to provide awareness, training, and skill development in the use of reading techniques embedded in inspectionswith specific emphasis on reading requirementsusing perspective based reading (PBR)5 Defining PBR5 Defining PBR3 Requirements 3 Requirements defectsdefectsContentsContentsSlide 57 The PBR “tester“ 7 The PBR “tester“ scenarioscenario1 Goals1 Goals2 Inspections:2 Inspections:Definition & DataDefinition & Data4 Reading techs4 Reading techsfor improvingfor improvinginspectionsinspections8 Discussion8 Discussion6 Applying PBR6 Applying PBRGoalsTo that end we will provide:– an overview of inspections– the ideas behind scenario-based reading– a classification of defects in requirements documents – specific training in PBR for requirements documentsWe hope this class will be interactive to understand and learn the techniques5 Defining PBR5 Defining PBR3 Requirements 3 Requirements defectsdefectsContentsContents7 The PBR “tester“ 7 The PBR “tester“ scenarioscenario1 Goals1 Goals2 Inspections:2 Inspections:Definition & DataDefinition & Data4 Reading techs4 Reading techsfor improvingfor improvinginspectionsinspections8 Discussion8 Discussion6 Applying PBR6 Applying PBRInspections Background5 Defining PBR5 Defining PBR3 Requirements 3 Requirements defectsdefectsContentsContentsSlide 77 The PBR “tester“ 7 The PBR “tester“ scenarioscenario1 Goals1 Goals2 Inspections:2 Inspections:Definition & DataDefinition & Data4 Reading techs4 Reading techsfor improvingfor improvinginspectionsinspections8 Discussion8 Discussion6 Applying PBR6 Applying PBRWhat is an inspection?• Definition:– Inspection is a static analysis method to verify quality properties of software products.• Dimensions:– Structured, well-defined process– Technical personnel– Well-defined roles– Reading techniques for detecting defects– Documented results5 Defining PBR5 Defining PBR3 Requirements 3 Requirements defectsdefectsContentsContentsSlide 87 The PBR “tester“ 7 The PBR “tester“ scenarioscenario1 Goals1 Goals2 Inspections:2 Inspections:Definition & DataDefinition & Data4 Reading techs4 Reading techsfor improvingfor improvinginspectionsinspections8 Discussion8 Discussion6 Applying PBR6 Applying PBRPlanningDetectionDefectReportFormCollectionCorrectionSoftwareArtifactPlanningFormDefect CorrectionForm1234organizerinspectormoderatorinspectorsauthorauthorCorrectedSoftwareArtifactSoftware InspectionDefectCollectionFormRolesActivitiesProductsReading TechniquesInspection outline5 Defining PBR5 Defining PBR3 Requirements 3 Requirements defectsdefectsContentsContentsSlide 97 The PBR “tester“ 7 The PBR “tester“ scenarioscenario1 Goals1 Goals2 Inspections:2 Inspections:Definition & DataDefinition & Data4 Reading techs4 Reading techsfor improvingfor improvinginspectionsinspections8 Discussion8 Discussion6 Applying PBR6 Applying PBRBenefits of inspections: Early defect detection• Theory: Inspections support early quality improvement by detecting more defects early in the requirements process.153025151051525201010304530150102030405060708090ReqDesCodeMod TestSys TestUse5030105414551055303510450102030405060708090ReqDesCodeMod TestSys TestUseWithout inspections With inspections¢ Reqs. defects ¢ Design defects ¢ Code Defects5 Defining PBR5 Defining PBR3 Requirements 3 Requirements defectsdefectsContentsContentsSlide 107 The PBR “tester“ 7 The PBR “tester“ scenarioscenario1 Goals1 Goals2 Inspections:2 Inspections:Definition & DataDefinition & Data4 Reading techs4 Reading techsfor improvingfor improvinginspectionsinspections8 Discussion8 Discussion6 Applying PBR6 Applying PBRBenefits of inspections: Early defect detection• Inspection results from Alaska SAR, JPL, where inspections conducted in requirements and


View Full Document

UMD CMSC 735 - Improving Software Inspections by Using Reading Techniques

Download Improving Software Inspections by Using Reading Techniques
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Improving Software Inspections by Using Reading Techniques and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Improving Software Inspections by Using Reading Techniques 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?