Institutionen f÷r datavetenskap
The PSPSM (Personal Software Process)
The PSP is an approach to help individual software developers to
continuously improve their software development performances. By means
of controlling and measuring their individual performances software
developers learn to
Concrete results can be found at the Software
Engineering Institute's (SEI) PSP Results pages
Please check the PSP
pages at the SEI for more
information on the PSP. Further
information on the PSP can for example be found at the PSP Resources Page at the University of Karlsruhe,
- make accurate predictions of the effort required to develop
- make accurate predictions of the quality of the produced
- improve their software development processes;
- improve the quality of the software produced;
There are several PSP versions, which are organised hierarchically. In
each version some activities are added and/or refined. The simplest
version is called PSP0 (the baseline process).
Please check http://www.sei.cmu.edu:80/activities/psp/WhatPSP.htm
Software Development Using PSP
The PSP comprises
The PSP process flow is summarised in the figure below:
- scripts that guide you through the development phases;
- forms that help you to carry out certain tasks;
- instructions that help you to fill in/ use the forms;
- standards that help you to evaluate your work.
For our purposes we have chosen to make a few modifications to the
original PSP and defined a new version by taking away a few things
from PSP1, but added design and code reviews, which are first introduced in
PSP2. We will call this new version UPSP (Umeň's version of the PSP ;-)).
UPSP is supported by PSPToolkit, a tool that was developed in Java at
our department (, ). PSPToolkit automates
some of the task of UPSP like
time and defect logging and the generation of summary forms. Please
check the PSPToolkit User
Manual for more information on the tool and its usage.
Please note that we do not have a Postmortem Script, since
most of the postmortem activities are now automated by means of our
tool. On the other hand, we have added a Report Script to
emphasize the importance of written communication. We do not provide
any detailed form-fill-in instructions for those forms that are
filled in or generated by our tool.
The documents listed below have been adapted from the original PSP
documents to match the changes we made.
It might be useful to have available all documents. The
process as a whole might be easier to understand. Furthermore we might
even use USPS manually.
Written in Java, works on UNIX (at least Solaris) and Windows
(at least 98/NT).
Combined desktop/handheld version. Desktop version can be used
stand-alone and is written in Java and uses an Access
database. The handheld version is written in WABA for the Palm
Pilot and supports logging/summary functions only. New projects
can only be created in the desktop version. Synchronization
utility is provided.
Go to PSP2000 homepage
- D. Frankovich: Automated
Support for a Custom Personal Software Development Process,
Master's thesis, University of Calgary, 1998.
- J. Forsman: Tool support for PSP, Master's thesis, Umeň
University, UMNAD 227.98, Jun 1998.
- J. Frankovich: The
One Person Project Software Process, Master's thesis,
University of Calgary, 1998.
- W. S. Humphrey: A Discipline for Software Engineering,
- W. S. Humphrey: Introduction to the Personal Software Process,
- S. Olofsson: Evaluation of PSP in the Undergraduate Education,
Master's thesis, Umeň University, UMNAD 272.99, 1999.
- A. Ístman: Anvandning av "the Personal Software Process" (PSP) i
Utbildningen pň C-nivň kurser, in Swedish, Master's thesis, Umeň
University, UMNAD 273.99, 1999.
SM PSP (Personal Software Process) is
a service mark of the SEI
(Software Engineering Institute).
Last modified: fri Mar 9 11 17:37:30 MET DST 2001
Copyright © 1999-2001 by jubo. All rights reserved.