We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byGeorge Parker
Modified about 1 year ago
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department of Defense © 2006 by Carnegie Mellon University October 2006 Pittsburgh, PA PSP II - Using PSP2 - 1 Personal Software Process SM for Engineers: Part II Tutorial: Using PSP2
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP2 - 2 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
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP2 - 3 PSP2 Objectives The objectives of PSP2 are to introduce design and code reviews methods for evaluating and improving the quality of your reviews
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP2 - 4 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.
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP2 - 5 Design and Code Reviews Two phases have been added to the process 1.Design reviews (DLDR) 2.Code reviews (CR) Time and defect data from these phases are summarized on the PSP2 Project Plan Summary.
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP2 - 6 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
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP2 - 7 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
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP2 - 8 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
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP2 - 9 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.
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP 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.
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP 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
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP 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.
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP 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
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP PSP2 Project Plan Summary Complete your estimates of 1.Time in phase 2.Defects injected in phase 3.Defects removed in phase Enter these values on the PSP2 project plan summary
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP 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
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP Defect Removal Efficiency Defect removal efficiency is calculated automatically and shows the number of defects removed per hour for 1.Design review 2.Code review 3.Compile 4.Test
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP Defect removal leverage is calculated automatically and compares removal efficiency for 1.Design Review vs. Unit Test 2.Code Review vs. Unit Test 3.Compile vs. Unit Test Defect Removal Leverage
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP Test Defects Per KLOC 1.Test defects per KLOC is calculated automatically and is an indicator of the quality of the program that you put into test.
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP Total Defects Per KLOC 1.Total defects per KLOC is calculated automatically and is a measure of the total defects injected during the process.
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP Yield 1.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.
© 2006 by Carnegie Mellon University October 2006 PSP II - Using PSP 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
Software Quality Management CIS 376 Bruce R. Maxim UM-Dearborn.
Process Improvement CIS 376 Bruce R. Maxim UM-Dearborn.
Software Quality Engineering Software Metrics-II.
Ch-5 Process Database and Process Capability Baseline.
McGraw-Hill/Irwin © The McGraw-Hill Companies 2010 Audit Sampling: An Overview and Application to Tests of Controls Chapter Eight.
Productivity Funding Understanding the Student Credit Hour (SCH) Funding Model at the University of Utah Please click with your mouse button to advance.
2 Welcome To Defect Management Training Objective: The objective of this course is to learn about standards that emphasize a best practice approach for.
1 Advanced Information Systems Development (SD3043) Quality Management.
Introduction New Form Stage 1 Stage 2 Stage 3 Feedback Conversation Career Development SMART Goals Competency Framework Documents There are also links.
Ch-6 Effort Estimation and Scheduling. Introduction A proper effort estimation method is a requirement for the software project planning KPA of CMM level.
+ Program Evaluation Planning & Data Analysis ScWk 242 – Session 11 Slides.
Discretionary Grant Application Constructing the Budget New Jersey Department of Education Office of Grants Management and Development.
Improvement SAE Book The Improvement Project is designed to be used by anyone attempting to improve the value or appearance of the home, place of employment,
CS101: INTRODUCTION TO COMPUTER PROGRAMMING LECTURE-1: INTRODUCTION TO PROBLEM SOLVING - CS002: REVIEW -
UNIT-V DEFECT PREVENTION 1Defect prevention (Arun)
SIVA 1 Construction Management-Lec3 Planning and Scheduling-II Dr. Attaullah Shah.
> SKED 3.2 Overview Presentation November Reasons for SKED 3.2 >Data model moving towards ERP requirements >Continue to tackle the configuration.
Testing Relational Database. Overview Once the design of a database system has been completed, the developers are ready to move into the implementation.
Using the STARS-SES Provider Annual Reporting System (PARS) Illinois State Board of Education.
1 Computer Systems & Architecture Lesson 3 5. Designing the Architecture.
Chapter 1 Principles of Control in a Foodservice Operation.
Ch-10 Configuration Management. Introduction A software project produces a number of items during its execution including various documents, manuals,
1 Target Costing If you cannot find the time to do it right, how will you find the time to do it over?
Work Planning and Scheduling Striving for Efficiency and Cost-Effectiveness.
Manage an IT Project. Aim This presentation is prepared to support and give a general overview of the ‘How to Manage and IT Project’ Guide and should.
Lecture 6: Software Design (Part I) Dr Valentina Plekhanova University of Sunderland, UK
Basic SDLC Models. Agenda SDLC definition Waterfall SDLC V-Shape SDLC Spiral SDLC RUP SDLC Agile methods.
Project Management and Software Quality See accompanying Word file “Software PM tools 3”
Unit-V -SOFTWARE QUALITY. To develop and deliver robust system, we need a high level of confidence that Each component will behave correctly Collective.
CH 4: Finding Your Unique Selling Point 14 January 2014 Lectured by: OR Vitou.
© 2016 SlidePlayer.com Inc. All rights reserved.