Перевод с английского
<<  Искусство перевода в эпоху Google Translate Personal Software Process Overview  >>
Personal Software ProcessSM for Engineers: Part II Tutorial: Using
Personal Software ProcessSM for Engineers: Part II Tutorial: Using
Tutorial Objectives
Tutorial Objectives
PSP2 Objectives
PSP2 Objectives
New Process Elements
New Process Elements
Design and Code Reviews
Design and Code Reviews
Quality Planning
Quality Planning
Estimating Total Defects
Estimating Total Defects
Estimating Defects by Phase
Estimating Defects by Phase
Estimating Review Time
Estimating Review Time
Estimating With Review Rates -1
Estimating With Review Rates -1
Estimating With Review Rates -2
Estimating With Review Rates -2
Estimating Considerations
Estimating Considerations
Estimating Defects Removed
Estimating Defects Removed
PSP2 Project Plan Summary
PSP2 Project Plan Summary
Derived Quality Measures
Derived Quality Measures
Defect Removal Efficiency
Defect Removal Efficiency
Defect Removal Leverage
Defect Removal Leverage
Test Defects Per KLOC
Test Defects Per KLOC
Total Defects Per KLOC
Total Defects Per KLOC
Yield
Yield
Messages to Remember
Messages to Remember

Презентация: «Personal Software ProcessSM for Engineers: Part II Tutorial: Using PSP2». Автор: Stacy Mitchell. Файл: «Personal Software ProcessSM for Engineers: Part II Tutorial: Using PSP2.ppt». Размер zip-архива: 435 КБ.

Personal Software ProcessSM for Engineers: Part II Tutorial: Using PSP2

содержание презентации «Personal Software ProcessSM for Engineers: Part II Tutorial: Using PSP2.ppt»
СлайдТекст
1 Personal Software ProcessSM for Engineers: Part II Tutorial: Using

Personal Software ProcessSM for Engineers: Part II Tutorial: Using

PSP2

2 Tutorial Objectives

Tutorial Objectives

After this tutorial, you will understand the new PSP2 process elements know how to use the PSP2 scripts and forms be prepared to use PSP2 for program 5

3 PSP2 Objectives

PSP2 Objectives

The objectives of PSP2 are to introduce design and code reviews methods for evaluating and improving the quality of your reviews

4 New Process Elements

New Process Elements

There are two new process elements. design review checklist code review checklist Design and code review checklists are described separately. PSP2 adds two key capabilities to the PSP design and code reviews quality planning The PSP2 project plan summary supports these two new capabilities.

5 Design and Code Reviews

Design and Code Reviews

Two phases have been added to the process Design reviews (DLDR) Code reviews (CR)

Time and defect data from these phases are summarized on the PSP2 Project Plan Summary.

6 Quality Planning

Quality Planning

PSP2 introduces quality planning. Quality planning involves estimating the total number of defects that will be injected estimating the number of defects that will be injected and removed in each process phase estimating the amount of time needed for design and code reviews adjusting these parameters as needed to ensure a high quality result

7 Estimating Total Defects

Estimating Total Defects

To estimate the total defects injected and removed, use the estimated program size and to-date defect density to calculate the estimated total defects. Use this formula

Planned total defects =

To-date total defects/KLOC ?

Planned Added and Modified LOC / 1000

8 Estimating Defects by Phase

Estimating Defects by Phase

To estimate defects injected and removed by phase, distribute the planned total defects injected and removed based on historical data. Planned Total Defects To Date % defects injected in each phase To Date % defects removed in each phase

9 Estimating Review Time

Estimating Review Time

These PSP benchmarks can be used to estimate design review and code review time in phase.

For manual calculations, starting with the code review rate is recommended.

10 Estimating With Review Rates -1

Estimating With Review Rates -1

Benchmark data on code review rates can be used to estimate review time. From PSP data, we know that code review rates under 200 LOC/hour generally give high yield. Using planned added and modified LOC, code review time can be calculated using this formula.

Assume a similar rate for design reviews.

11 Estimating With Review Rates -2

Estimating With Review Rates -2

To add review time to your plan increase the total minutes, and/or reduce compile and test time As a final check of your estimate, make sure that review rates are less than 200 LOC per hour defect removal rates are between 3 to 5 per hour for design review 5 to 10 per hour for code review A/FR is about 2.0

12 Estimating Considerations

Estimating Considerations

Initially no historical data are available for planning defects injected and removed in review phases. Until you have data for design and code review phases, you may want to consider defects injected are 0 defects removed should be based on your yield goal Your yield goal should be based on your interim report analysis. If you do not have a yield goal, you should try to achieve greater than 60% yield.

13 Estimating Defects Removed

Estimating Defects Removed

Defects removed in a review phase are calculated using number of defects escaping from prior phases number of defects injected in a phase percentage of defects removed, i.e. Phase Yield

Defects present

=

escapes + injected

Defects removed

=

present ? phase yield

14 PSP2 Project Plan Summary

PSP2 Project Plan Summary

Complete your estimates of Time in phase Defects injected in phase Defects removed in phase Enter these values on the PSP2 project plan summary.

1

2

3

15 Derived Quality Measures

Derived Quality Measures

PSP2 also provides the following derived quality measures. Defect removal efficiency Defect removal leverage Test defects per KLOC Total defects per KLOC Yield

16 Defect Removal Efficiency

Defect Removal Efficiency

Defect removal efficiency is calculated automatically and shows the number of defects removed per hour for Design review Code review Compile Test

17 Defect Removal Leverage

Defect Removal Leverage

Defect removal leverage is calculated automatically and compares removal efficiency for Design Review vs. Unit Test Code Review vs. Unit Test Compile vs. Unit Test

18 Test Defects Per KLOC

Test Defects Per KLOC

Test defects per KLOC is calculated automatically and is an indicator of the quality of the program that you put into test.

19 Total Defects Per KLOC

Total Defects Per KLOC

Total defects per KLOC is calculated automatically and is a measure of the total defects injected during the process.

20 Yield

Yield

Yield (actual and to-date) is calculated automatically for the entire process and is the percentage of defects injected and removed before the first compile.

21 Messages to Remember

Messages to Remember

You will see more improvement from design and code reviews than any other process change you make. Quality will improve. Productivity will increase. PSP2 provides data that allows you to plan for specific quality levels control quality during development improve the quality of your PSP increase productivity without sacrificing quality

«Personal Software ProcessSM for Engineers: Part II Tutorial: Using PSP2»
http://900igr.net/prezentacija/anglijskij-jazyk/personal-software-processsm-for-engineers-part-ii-tutorial-using-psp2-60479.html
cсылка на страницу
Урок

Английский язык

29 тем
Слайды
900igr.net > Презентации по английскому языку > Перевод с английского > Personal Software ProcessSM for Engineers: Part II Tutorial: Using PSP2