PSP(sm) A Self-Improvement Process for

Improve your software development process in a modern context with PSP from the SEI and Watts Humphrey, the foremost expert on this topic.

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.

PREFACE

XIII

Chapter 1 THE PERSONAL PROCESS STRATEGY

1

(10)

1.1 The PSP's Purpose

3

(1)

1.2 The Logic for a Software Engineering Discipline

4

(2)

1.3 Using Disciplined Development Practices

6

(1)

1.4 Operational Processes

6

(1)

1.5 Defining and Using a Personal Process

7

(1)

1.6 Learning to Use a Personal Process

8

(1)

1.7 Preparing for the Team Software Process

9

(1)

1.8 Summary

9

(1)

Reference

10

(1)

Chapter 2 THE BASELINE PERSONAL PROCESS

11

(24)

2.1 What Is a Process?

12

(1)

2.2 Defining Your Own Process

13

(1)

2.3 Baseline Process Contents

14

(2)

2.4 Why Forms Are Helpful

16

(1)

2.5 The PSP Process Elements

17

(1)

2.6 The PSPO Process

18

(2)

2.7 PSPO Measures

20

(1)

2.8 Time Recording

21

(3)

2.9 Defect Recording

24

(6)

2.10 The PSPO Project Plan Summary

30

(1)

2.11 The Compile Phase

31

(1)

2.12 Incremental Development

32

(2)

2.13 PSP Tool Support

34

(1)

2.14 Summary

34

(1)

2.15 Exercises

34

(1)

Chapter 3 MEASURING SOFTWARE SIZE

35

(22)

3.1 Size Measures

35

(5)

3.2 Establishing a Database Counting Standard

40

(1)

3.3 Establishing a Line-of-Code Counting Standard

40

(2)

3.4 Size Accounting

42

(3)

3.5 Using Size Data

45

(2)

3.6 Calculating Productivity

47

(1)

3.7 Size Counters

48

(5)

3.8 Other Size Measures

53

(1)

3.9 Summary

54

(1)

3.10 Exercises

54

(1)

References

55

(2)

Chapter 4 PLANNING

57

(12)

4.1 The Planning Process

58

(1)

4.2 Why Make Plans?

59

(1)

4.3 What Is a Plan?

60

(1)

4.4 The Contents of a Software Plan

60

(2)

4.5 Planning a Software Project

62

(1)

4.6 The Conceptual Design

63

(2)

4.7 Plan Quality

65

(1)

4.8 Planning Issues

65

(1)

4.9 Summary

66

(1)

Reference

67

(2)

Chapter 5 SOFTWARE ESTIMATING

69

(16)

5.1 Size Estimating Principles

69

(1)

5.2 The Conceptual Design

70

(1)

5.3 Proxy-Based Estimating

71

(4)

5.4 Using Proxies in Estimating

75

(3)

5.5 Producing the Relative-Size Table

78

(2)

5.6 Estimating Considerations

80

(4)

5.7 Summary

84

(1)

Chapter 6 THE PROBE ESTIMATING METHOD

85

(24)

6.1 Estimating from Data

85

(2)

6.2 Proxy-Based Estimating

87

(8)

6.3 Estimating with Limited Data

95

(5)

6.4 An Estimating Example

100

(2)

6.5 Estimating Nonprogramming Tasks

102

(3)

6.6 Considerations in Using PROBE

105

(3)

6.7 Summary

108

(1)

6.8 Exercises

108

(1)

Chapter 7 SOFTWARE PLANNING

109

(24)

7.1 Plan Requirements

109

(2)

7.2 Project and Period Plans

111

(2)

7.3 Producing the Schedule

113

(2)

7.4 Making the Schedule

115

(4)

7.5 Earned Value

119

(1)

7.6 An Earned Value Example

120

(3)

7.7 Comments on the EV Example

123

(2)

7.8 Estimating Accuracy

125

(1)

7.9 The Prediction Interval

126

(2)

7.10 Alerting Management to Changes

128

(1)

7.11 Planning Considerations

129

(2)

7.12 Summary

131

(1)

7.13 Exercises

132

(1)

References

132

(1)

Chapter 8 SOFTWARE QUALITY

133

(30)

8.1 The PSP Quality Strategy

135

(1)

8.2 What Is Software Quality?

135

(1)

8.3 The Economics of Software Quality

136

(5)

8.4 Defect Types

141

(1)

8.5 Personal Quality Practices

142

(1)

8.6 Quality Measures

143

(10)

8.7 Quality Management

153

(1)

8.8 Personal Quality Management

154

(2)

8.9 Managing Product Quality

156

(1)

8.10 PSP Improvement Practices

157

(1)

8.11 Defect Prevention

158

(2)

8.12 Summary

160

(1)

References

161

(2)

Chapter 9 DESIGN AND CODE REVIEWS

163

(40)

9.1 What Are Reviews?

164

(1)

9.2 Why Review Programs?

164

(4)

9.3 Review Principles

168

(5)

9.4 The PSP Code Review Process

173

(3)

9.5 The Code Review Checklist

176

(5)

9.6 Design Reviews

181

(2)

9.7 Design Review Principles

183

(4)

9.8 Review Measures

187

(7)

9.9 Review Issues

194

(7)

9.10 Summary

201

(1)

9.11 Exercises

202

(1)

References

202

(1)

Chapter 10 SOFTWARE DESIGN

203

(22)

10.1 What Is Design?

204

(2)

10.2 Why Design?

206

(1)

10.3 The Design Process

207

(3)

10.4 Design Levels

210

(6)

10.5 Design and Development Strategies

216

(4)

10.6 Design Quality

220

(3)

10.7 Summary

223

(1)

References

224

(1)

Chapter 11 THE PSP DESIGN TEMPLATES

225

(28)

11.1 Design Representation

226

(3)

11.2 The Design Templates

229

(1)

11.3 The Operational Specification Template (OST)

230

(3)

11.4 The Functional Specification Template (FST)

233

(3)

11.5 The State Specification Template (SST)

236

(4)

11.6 The Logic Specification Template (LST)

240

(1)

11.7 A State-Machine Design Example

241

(5)

11.8 Using the PSP Design Templates

246

(2)

11.9 Using the Design Templates in Large-Scale Design

248

(2)

11.10 Summary

250

(1)

11.11 Exercises

250

(1)

References

250

(3)

Chapter 12 DESIGN VERIFICATION

253

(34)

12.1 Why Verify Programs?

254

(3)

12.2 Design Standards

257

(1)

12.3 Execution-Table Verification

258

(4)

12.4 Trace-Table Verification

262

(3)

12.5 Verifying State Machines

265

(6)

12.6 Loop Verification

271

(6)

12.7 Other Analytical Verification Methods

277

(3)

12.8 Verification Considerations

280

(4)

12.9 Summary

284

(1)

12.10 Exercises

284

(1)

References

285

(2)

Chapter 13 PROCESS EXTENSIONS

287

(22)

13.1 Customizing the Development Process

289

(1)

13.2 Why Define a Process?

290

(1)

13.3 The PSP Process Strategy

291

(1)

13.4 Defining a Process

291

(3)

13.5 Process Evolution

294

(4)

13.6 Example Processes

298

(8)

13.7 Process Development Considerations

306

(1)

13.8 Summary

307

(1)

13.9 Exercises

308

(1)

References

308

(1)

Chapter 14 USING THE PERSONAL SOFTWARE PROCESS

309

(20)

14.1 Development Challenges

309

(4)

14.2 The Team Software Process (TSP)

313

(1)

14.3 The Logic of the TSP

314

(1)

14.4 Teambuilding

314

(2)

14.5 The TSP Launch Process

316

(1)

14.6 The TSP Coach

317

(1)

14.7 Managing Your Own Project

318

(4)

14.8 TSP Results

322

(1)

14.9 The Rewards of Teamwork

322

(1)

14.10 The TSP Team of One

323

(3)

14.11 Your Future in Software Engineering

326

(1)

References

327

(2)

INDEX

329

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

FREE SHIPPING

Amazon no longer offers textbook rentals. We do!

PSP(sm) A Self-Improvement Process for Software Engineers

Summary

Author Biography

Table of Contents

Supplemental Materials