Welcome to AutoPSP!  This program was inspired by a summer course that I took in Software Engineering.   
It was a "guinea pig" course, consisting of only myself, my professor and one other student.  Our goal was  
to get through the book A Discipline for Software Engineering by Watts Humphrey before the end of the  
summer.  
  
I've never read a more mind opening book about software  engineering.  Watts Humphreys book illuminates  
a path from being a  hacker to being a professional engineer.  However, as with all  disciplines, there is a lot  
of effort to follow this path.  
  
The heart and soul of Mr. Humphreys book is the Personal Software  Process, or PSP.  This process  
provides you with a series of forms  with which you can track your productivity.  By productivity, I mean  
that you can track how long it takes you to write a program, how much time you spend in each phase of the  
development, how large your program is and so on.  Then comes the good bit.  Using the data you collect,  
you can predict future information.    
  
No more deadlines pulled out of thin air.  No more wondering how big  your program is, without being able  
to measure it.  No more trying to  convince a manager that you're working, even though your program  isn't.   
With PSP you can show documentation of the work that you do,  and make accurate predictions to use for  
planning your projects life!    
  
The only problem was the paper work.  I have about half a ream of  paper devoted to tracking my projects,  
and it was fast becoming an  unwieldy process.  So I took the next step and fed the whole thing  into this  
program.      
  
To really understand AutoPSP, you must understand the PSP.  The  best way to do this is go out and buy A  
Discipline for Software  Engineering by Watts Humphrey.  This tutorial presumes that you are  at least  
somewhat familiar with software engineering terminology.    
  
The program keeps all of your data organized for you.  It creates  graphical reports of your progress.  It even  
contains a Lines of Code counter and a Linear Regression program for making your  predictions as accurate  
as possible.    
  
So let's stop reading history and start playing with the program!