Skip to content

PSP(sm): a Self-Improvement Process for Software Engineers

Best in textbook rentals since 2012!

ISBN-10: 0321305493

ISBN-13: 9780321305497

Edition: 2005

Authors: Watts Humphrey

List price: $69.99
Blue ribbon 30 day, 100% satisfaction guarantee!
what's this?
Rush Rewards U
Members Receive:
Carrot Coin icon
XP icon
You have reached 400 XP and carrot coins. That is the daily max!

Description:

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…    
Customers also bought

Book details

List price: $69.99
Copyright year: 2005
Publisher: Addison Wesley Professional
Publication date: 3/3/2005
Binding: Hardcover
Pages: 368
Size: 6.50" wide x 9.56" long x 1.00" tall
Weight: 1.738
Language: English

Preface
The Personal Process Strategy
The PSPs Purpose
The Logic for a Software Engineering Discipline
Using Disciplined Development Practices
Operational Processes
Defining and Using a Personal Process
Learning to Use a Personal Process
Preparing for the Team Software Process
Summary
Reference
The Baseline Personal Process
What Is a Process?
Defining Your Own Process
Baseline Process Contents
Why Forms Are Helpful
The PSP Process Elements
The PSP0 Process
PSP0 Measures
Time Recording
Defect Recording
The PSP0 Project Plan Summary
The Compile Phase
Incremental Development
PSP Tool Support
Summary
Exercises
Measuring Software Size
Size Measures
Establishing a Database Counting Standard
Establishing a Line-of-Code Counting Standard
Size Accounting
Using Size Data
Calculating Productivity
Size Counters
Other Size Measures
Summary
Exercises
References
Planning
The Planning Process
Why Make Plans?
What Is a Plan?
The Contents of a Software Plan
Planning a Software Project
The Conceptual Design
Plan Quality
Planning Issues
Summary
Reference
Software Estimating
Size Estimating Principles
The Conceptual Design
Proxy-Based Estimating
Using Proxies in Estimating
Producing the Relative-Size Table
Estimating Considerations
Summary
The PROBE Estimating Method
Estimating from Data
Proxy-Based Estimating
Estimating with Limited Data
An Estimating Example
Estimating Nonprogramming Tasks
Considerations in Using PROBE
Summary
Exercises
Software Planning
Plan Requirements
Project and Period Plans
Producing the Schedule
Making the Schedule
Earned Value
An Earned Value Example
Comments on the EV Example
Estimating Accuracy
The Prediction Interval
Alerting Management to Changes
Planning Considerations
Summary
Exercises
References
Software Quality
The PSP Quality Strategy
What Is Software Quality?
The Economics of Software Quality
Defect Types
Personal Quality Practices
Quality Measures
Quality Management
Personal Quality Management
Managing Product Quality
PSP Improvement Practices
Defect Prevention
Summary
References
Design and Code Reviews
What Are Reviews?
Why Review Programs?
Review Principles
The PSP Code Review Process
The Code Review Checklist
Design Reviews
Design Review Principles
Review Measures
Review Issues
Summary
Exercises
References
Software Design
What Is Design? 204
Why Design? 206
The Design Process 207
Design Levels 210
Design and Development Strategi