Using the software process model to analyze a software project

Attention is given to the software process model (SPM), which was introduced by A.L. Baker et al. (1987). The SPM models software development by modeling the evolution of the full set of documents produced in software development. The authors show the usefulness of the SPM as a management tool by applying it to a software project. Since the SPM shows patterns of the software product development in greater detail than the current tools available, it provides management with a more effective means of visualizing and controlling software projects. The SPM has the capability to alert management to problems during the development process. This was illustrated when the SPM indicated a problem during the design phase. The problem was made known by the pattern generated by the continuous changes to design specifications when initial code was completed. It was shown that the SPM can be used to ensure consistencies between documents. By plotting changes in documents, both developers and managers are alerted as to whether or not a change is incorporated in other documents.<
>