Introduction to the Personal Software Process(sm) (SEI Series in Software Engineering)

Software Processes 1. • A process is a series of steps involving activities, In the late s, the Software Engineering Institute (SEI), Carnegie SM Personal Software Process and PSP are service marks of Carnegie Mellon University.
Table of contents

Keeping Time Logs in the Engineering Notebook. Hints on Logging Your Time. Period and Product Planning. Period and Product Plans. The Weekly Activity Summary. Calculating Period Times and Rates. Using the Weekly Activity Summary. The Need for Product Plans. Why Product Plans Are Helpful. What is a Product Plan? Product Planning in this Book. The Job Number Log.

Using Product Times and Rates Data. The Product Planning Process. Some Cautions on Using Size Measures. Making a Larger Size Estimate. Elements of Time Management. Gather Data on Time Spent by Activity. Evaluating Your Time Distribution. Making a Time Budget. Managing Your Time Budget. Suggestions on Managing Variable Time. Your Time Management Objective. Example of a Commitment.


  • Clientes que compraram este item também compraram.
  • The Collected Stories, The Legend of Drizzt (Forgotten Realms: the Legend of Drizzt).
  • .
  • Last in Their Class: Custer, Pickett and the Goats of West Point (Encounter Broadsides).
  • Love Lessons.

An Example in Industry. The Importance of Managing Commitments.

The Consequences of Not Managing Commitments. The Way to Manage Commitments. The Need for Schedules. Making a Project Schedule. The Need for Project Plans. The Project Plan Summary.

Introduction to the Personal Software Process - Watts S. Humphrey - Google Книги

The Software Development Process. Why We Use Processes. An Example of To Date Calculations. What is Software Quality? The Defect Recording Log.

Using the Defect Recording Log. A Personal Commitment to Quality. The Steps in Finding Defects. Ways to Find and Fix Defects. Why Find Defects Early? The Costs of Finding and Fixing Defects.

Introduction to the Personal Software Process(sm)

Using Reviews to Find Defects. Data on Compile and Test Defects. Other Kinds of Reviews. The Code Review Checklist. Why Do Checklists Help?

An Example of a Code Review Checklist. Leia mais Leia menos. Habilitado Otimizado para telas maiores Idioma: Detalhes do produto Formato: Compartilhe seus pensamentos com outros clientes. I think this book is a very good reference book. You can accomplish all basic steps in Team Software Process through this book. It is clear and detailed. This is a good introduction to working in a team and using good software engineering techniques such as planning and inspections.

It is geared for undergraduate students, therefore the managerial roles have been created. This would probably not work out of the box for an organization that is already set up. For students, the manager roles give each team member ownership in the product while making sure each aspect of good engineering has an advocate. The processes are written as scripts. These are very easy to follow and take the guesswork out of how to do each step in the lifecycle.

Detalhes do produto

This is a process book therefore there is not a lot of technically-oriented information in the book. For example, the book tells you that you must design your software. It does not give many guidelines on what a good object-oriented, client-server, real time, etc. In addition, some of the data bookkeeping is long and involved.

Description

A good tool would help with this. Overall, this is a good tutorial and a good reference book. I used this book as a graduate student, and I continue to pull ideas out of it for use in my work.