{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

CS352-Lecture_Notes-OH-L03

The effort in person hours that is dedicated to the

Info iconThis preview shows pages 7–12. Sign up to view the full content.

View Full Document Right Arrow Icon
— the effort (in person-hours) that is dedicated to the correction of those errors uncovered during the review ork product size, WPS measure of the size of the work product Dr. Omar Hamdy Spring 2011 7 Work product size, WPS —a measure of the size of the work product that has been reviewed (e.g., the number of UML models, or the number of document pages, or the number of lines of code) Minor errors found, Err minor —the number of errors found that can be categorized as minor (requiring less than some pre-specified effort to correct) Major errors found, Err major — the number of errors found that can be categorized as major (requiring more than some pre-specified effort to correct) CS352 Software Engineering II
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Example I • If past history indicates that – the average defect density for a requirements model is 0.6 errors per page, and a new requirement model is 32 pages long, rough estimate suggests that your software Dr. Omar Hamdy Spring 2011 8 – a rough estimate suggests that your software team will find about 19 or 20 errors during the review of the document. – You only found 6! Is this good or bad? • you’ve done an extremely good job in developing the requirements model or your review approach was not thorough enough. CS352 Software Engineering II
Background image of page 8
Example II • The effort required to correct a minor model error (immediately after the review) was found to require 4 person-hours . • The effort required for a major requirement error was found to be 18 person-hours . • Examining the review data collected, you find that minor errors occur about 6 times more frequently than major errors. Therefore, you can estimate that the average effort to find and correct a requirements error during review is bout person ours. How? Dr. Omar Hamdy Spring 2011 9 about 6 person-hours. How? • Requirements related errors uncovered during testing require an average of 45 person-hours to find and correct. Using the averages noted, we get: • Effort saved per error = E testing – E reviews • 45 – 6 = 39 person-hours/error • Assuming 22 errors were found during the review of the requirements model , a saving of about 660 person-hours of testing effort would be achieved. And that’s just for requirements-related errors CS352 Software Engineering II
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Overall Dr. Omar Hamdy Spring 2011 10 CS352 Software Engineering II
Background image of page 10
Informal Review • Informal reviews include: – a simple desk check of a software engineering work product with a colleague – a casual meeting (involving more than 2 people)
Background image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 12
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page7 / 21

the effort in person hours that is dedicated to the...

This preview shows document pages 7 - 12. Sign up to view the full document.

View Full Document Right Arrow Icon bookmark
Ask a homework question - tutors are online