COVID-19 Response at Fishpond.com.au

Read what we're doing...

PSP(SM)
By

Rating

Product Description
Product Details

Table of Contents

Preface xiiiChapter 1: The Personal Process Strategy 1

1.1. The PSP's Purpose 31.2. The Logic for a Software Engineering Discipline 41.3. Using Disciplined Development Practices 61.4. Operational Processes 61.5. Defining and Using a Personal Process 71.6. Learning to Use a Personal Process 81.7. Preparing for the Team Software Process 91.8. Summary 9Reference 10

Chapter 2: The Baseline Personal Process 11

2.1. What Is a Process? 122.2. Defining Your Own Process 132.3. Baseline Process Contents 142.4. Why Forms Are Helpful 162.5. The PSP Process Elements 172.6. The PSP0 Process 182.7. PSP0 Measures 202.8. Time Recording 212.9. Defect Recording 242.10. The PSP0 Project Plan Summary 302.11. The Compile Phase 312.12. Incremental Development 322.13. PSP Tool Support 342.14. Summary 342.15. Exercises 34

Chapter 3: Measuring Software Size 35

3.1. Size Measures 353.2. Establishing a Database Counting Standard 403.3. Establishing a Line-of-Code Counting Standard 403.4. Size Accounting 423.5. Using Size Data 453.6. Calculating Productivity 473.7. Size Counters 483.8. Other Size Measures 533.9. Summary 543.10. Exercises 54References 55

Chapter 4: Planning 57

4.1. The Planning Process 584.2. Why Make Plans? 594.3. What Is a Plan? 604.4. The Contents of a Software Plan 604.5. Planning a Software Project 624.6. The Conceptual Design 634.7. Plan Quality 654.8. Planning Issues 654.9. Summary 66Reference 67

Chapter 5: Software Estimating 69

5.1. Size Estimating Principles 695.2. The Conceptual Design 705.3. Proxy-Based Estimating 715.4. Using Proxies in Estimating 755.5. Producing the Relative-Size Table 785.6. Estimating Considerations 805.7. Summary 84

Chapter 6: The PROBE Estimating Method 85

6.1. Estimating from Data 856.2. Proxy-Based Estimating 876.3. Estimating with Limited Data 956.4. An Estimating Example 1006.5. Estimating Nonprogramming Tasks 1026.6. Considerations in Using PROBE 1056.7. Summary 1086.8. Exercises 108

Chapter 7: Software Planning 109

7.1. Plan Requirements 1097.2. Project and Period Plans 1117.3. Producing the Schedule 1137.4. Making the Schedule 1157.5. Earned Value 1197.6. An Earned Value Example 1207.7. Comments on the EV Example 1237.8. Estimating Accuracy 1257.9. The Prediction Interval 1267.10. Alerting Management to Changes 1287.11. Planning Considerations 1297.12. Summary 1317.13. Exercises 132References 132

Chapter 8: Software Quality 133

8.1. The PSP Quality Strategy 1358.2. What Is Software Quality? 1358.3. The Economics of Software Quality 1368.4. Defect Types 1418.5. Personal Quality Practices 1428.6. Quality Measures 1438.7. Quality Management 1538.8. Personal Quality Management 1548.9. Managing Product Quality 1568.10. PSP Improvement Practices 1578.11. Defect Prevention 1588.12. Summary 160References 161

Chapter 9: Design and Code Reviews 163

9.1. What Are Reviews? 1649.2. Why Review Programs? 1649.3. Review Principles 1689.4. The PSP Code Review Process 1739.5. The Code Review Checklist 1769.6. Design Reviews 1819.7. Design Review Principles 1839.8. Review Measures 1879.9. Review Issues 1949.10. Summary 2019.11. Exercises 202References 202

Chapter 10: Software Design 203

10.1. What Is Design? 20410.2. Why Design? 20610.3. The Design Process 20710.4. Design Levels 21010.5. Design and Development Strategies 21610.6. Design Quality 22010.7. Summary 223References 224

Chapter 11: The PSP Design Templates 225

11.1. Design Representation 22611.2. The Design Templates 22911.3. The Operational Specification Template (OST) 23011.4. The Functional Specification Template (FST) 23311.5. The State Specification Template (SST) 23611.6. The Logic Specification Template (LST) 24011.7. A State-Machine Design Example 24111.8. Using the PSP Design Templates 24611.9. Using the Design Templates in Large-Scale Design 24811.10. Summary 25011.11. Exercises 250References 250

Chapter 12: Design Verification 253

12.1. Why Verify Programs? 25412.2. Design Standards 25712.3. Execution-Table Verification 25812.4. Trace-Table Verification 26212.5. Verifying State Machines 26512.6. Loop Verification 27112.7. Other Analytical Verification Methods 27712.8. Verification Considerations 28012.9. Summary 28412.10. Exercises 284References 285

Chapter 13: Process Extensions 287

13.1. Customizing the Development Process 28913.2. Why Define a Process? 29013.3. The PSP Process Strategy 29113.4. Defining a Process 29113.5. Process Evolution 29413.6. Example Processes 29813.7. Process Development Considerations 30613.8. Summary 30713.9. Exercises 308References 308

Chapter 14: Using the Personal Software Process 309

14.1. Development Challenges 30914.2. The Team Software Process (TSP) 31314.3. The Logic of the TSP 31414.4. Teambuilding 31414.5. The TSP Launch Process 31614.6. The TSP Coach 31714.7. Managing Your Own Project 31814.8. TSP Results 32214.9. The Rewards of Teamwork 32214.10. The TSP Team of One 32314.11. Your Future in Software Engineering 326References 327Index 329

Promotional Information

This book describes and documents the PSP (Personal Software Process) forindividual software developers, and introduces them to the TSP (TeamSoftware Process) for teams. With examples and data drawn from real-worlddevelopment projects, it shows how developers can better manage anddramatically improve their personal software process. In doing so,organizations become better able to deliver defect-free software on time andunder budget.In short, this book is the industrial version of the author's Incredibly influential"A Discipline for Software Engineering." It build upon and modernizes thattext (as well as Humphrey's previous PSP and TSP books) to present acontemporary and completely updated approach toward the highly importanttopic of software process improvement.

About the Author

Known as "the father of software quality," Watts S. Humphrey is the author of numerous influential books on the software-development process and software process improvement. Humphrey is a fellow of the Software Engineering Institute (SEI) at Carnegie Mellon University, where he founded the Software Process Program and provided the vision and early leadership for the original Capability Maturity Model (CMM). He also is the creator of the Personal Software Process (PSP) and Team Software Process (TSP). Recently, he was awarded the National Medal of Technology--the highest honor given by the president of the United States to America's leading innovators.

Ask a Question About this Product More...
Write your question below:
Look for similar items by category
People also searched for
How Fishpond Works
Fishpond works with suppliers all over the world to bring you a huge selection of products, really great prices, and delivery included on over 25 million products that we sell. We do our best every day to make Fishpond an awesome place for customers to shop and get what they want — all at the best prices online.
Webmasters, Bloggers & Website Owners
You can earn a 8% commission by selling PSP(SM): A Self-Improvement Process for Software Engineers on your website. It's easy to get started - we will give you example code. After you're set-up, your website can earn you money while you work, play or even sleep! You should start right now!
Authors / Publishers
Are you the Author or Publisher of a book? Or the manufacturer of one of the millions of products that we sell. You can improve sales and grow your revenue by submitting additional information on this title. The better the information we have about a product, the more we will sell!
Item ships from and is sold by Fishpond.com, Inc.
Back to top