Prepare
Practice
Interview
Aptitude
Reasoning
English
GD
Placement papers
HR
Current affairs
Engineering
MCA
MBA
Online test
Login
DRE approaches for quality approach - Software Process Improvement
Home
>>
Category
>>
Software Engineering (MCQ) questions and answers
>>
Software Process Improvement
Q. A quality objective for a software team is achieve in how many DRE approaches?
- Published on 24 Jul 15
a.
2
b.
3
c.
1
d.
4
ANSWER: 1
Related Content
Software Management (
10
)
Introduction of Software Engineering (
37
)
Software Specification & Measurement (
23
)
Software Process (
9
)
Process Modelling and SDLC (
18
)
Planning and Managing the Project (
26
)
Capturing the Requirement (
22
)
Designing the System (
20
)
Objects Design (
20
)
Program Writing (
20
)
Formal Modelling & Verification (
20
)
Delivering the System (
18
)
Maintaining the System (
21
)
Evaluating Products, Processes & Resources (
17
)
Software Process Improvement (
28
)
Improving Predictions, Products, Processes & Resources (
16
)
Discussion
Nirja Shah
-Posted on 26 Oct 15
Defect Removal Efficiency
- A quality metric that provides benefit at both the project and process level is defect removal efficiency (DRE).
- It is a measure of the filtering ability of quality assurance and control activities as they are applied throughout all process framework activities. To compute DRE:
DRE = E / (E + D)
- Where E= no. of error before release and D = defect found after release of software to end users
- 1 is the ideal value for DRE.
- That is, no defects are found in the software.
- Realistically, 0 will be greater than D, but the value of DRE can still approach 1.
- As E increases (for a given value of D), the overall value of DRE begins to approach 1.
- In fact, the final value of D will decrease as E increases (errors are filtered out before they become defects).
- DRE encourages a software project team to institute techniques for finding as many errors as possible before delivery.
- It can also be used within the project to assess a team’s ability to find errors before they are passed to the next framework activity or software engineering task.
- For example, the requirements analysis task produces an analysis model that can be reviewed to find and correct errors.
- Those errors that are not found during the review of the analysis model are passed on to the design task.
When used in this context, we redefine DRE as
DREi = Ei/(Ei + Ei+1)
- Ei is the number of errors found during software engineering activity i.
- Ei+1 number of errors found during software engineering activity i+1
- A quality objective for a software team is to achieve DREi that approaches 1.
- That is, errors should be filtered out before they are passed on to the next activity.
➨
Post your comment / Share knowledge
Enter the code shown above:
(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)
MCQs
English
Tutorials
Download
▲