1 / 10

Inspection of Software Requirements to support Project/Quality Management an Empirical Study

Inspection of Software Requirements to support Project/Quality Management an Empirical Study. Stefan Biffl Institut für Softwaretechnik Technische Universität Wien. The inspection process as part of QM in the project and organization. Experimentation with inspection

Download Presentation

Inspection of Software Requirements to support Project/Quality Management an Empirical Study

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. Inspection of Software Requirementsto support Project/Quality Management an Empirical Study Stefan Biffl Institut für Softwaretechnik Technische Universität Wien

  2. The inspection process as part ofQM in the project and organization

  3. Experimentation with inspection Built up on work on defect detection and defect content estimation with inspection data from UMD, IESE, and Lund Cooperation with IESE Influence of reading techniques on inspection data that is input to defect content estimation technqiues Cost-Benefit of Inspection Inspection of requirements Method Reading Techniques Inspection Planning Inspectors Techniques Defect Content Estimation Objective Subjective Feedback to Project/Quality Management for Planning Reinspection Decision Product Quality Prior Work in Empirical SE

  4. Process of Defect Detection, Estimation, and Matching • 169 inspectors in 31 teams: 16 CBR, 15 Scenario-based reading • Two inspection cycles, defect classes, defect detection time logging

  5. On average defect detection rate of 46% (same as inspection). Most teams find less defects during reinspection. Teams who found few defects during inspection found more defects during reinspection. Less effort, lower efficiency. Net gain positive for reasonable cost-benefit assumptions (1 hour for a minor defect, 8 hours for a major defect). Weighted defects found at inspection and reinspection Scatterplot to compare E1 with E2 . Biffl S., Halling M., and Köhle M., "Investigating the Effect of a Second Software Inspection Cycle", 2000, Figure 3

  6. Overview of Defect Content Estimation Techniques

  7. Accuracy of DCETs

  8. In-process inspection control • Estimate the ‘ceiling’ of defects to be found in with an inspection process using software reliability growth models. • Individual detection process. • Team detection process. • Multiple inspection cycles.

  9. Inspection techniques Reinspection with different reading techniques for each inspector. Work with professional subjects. Tool support for inspection Time logging of inspection tasks and defect detection events. Defect identification as preparation for defect content estimation. In-process control of inspection Feedback to inspection management on current estimates: on the number of defects still in the product and on the number of defects the inspection team is likely to find in a given time period with the current process. Process for subjective defect content estimation which uses inspection data more formally. Future Work in Empirical SE

  10. Benefits from ISERN Membership • Contact to colleagues who work in the same area. • Share experiment practices, tools, and results • Joint research initiatives. • Establish ESE as part of professional SE practice and education.

More Related