ABSTRACT

Why do we have software process? For perhaps half of the time that has elapsed since software was first produced, practitioners seemed to get along without anything that could be reasonably called “process.” A whole new generation of software developers has moved into the workforce since serious and concerted efforts have been made to codify the process for creating software. Yet still there is little consensus as to the degree of process we should use. There is a similar lack of agreement on the type of process, its sequencing, the work products and deliverables it produces, the languages, patterns, thought processes, and even organizational structures required to successfully create software.