Making Software Visible, Operational, and Maintainable in a Small Project Environment

Practical suggestions are presented for effectively managing software development in small-project environments (i.e., no more than several million dollars per year). The suggestions are based on an approach to product development using a product assurance group that is independent from the development group. Within this check-and-balance management/development/product assurance structure, a design review process is described that effects an orderly transition from customer needs statement to software code. The testing activity that follows this process is then explained. Finally, the activities of a change control body (called a configuration control board) and supporting functions geared to maintaining delivered software are described. The suggested software management practices result from the experience of a small (approximately 100 employees) software engineering company that develops and maintains computer systems supporting real-time interactive commercial, industrial, and military applications.

[1]  Barry W. Boehm An Experiment in Small-Scale Application Software Engineering , 1981, IEEE Transactions on Software Engineering.

[2]  Stanley G. Siegel,et al.  An approach to software configuration control , 1981, SIGMETRICS Perform. Evaluation Rev..

[3]  Edward H. Bersoff,et al.  Software Configuration Management , 1978, SIGMETRICS Perform. Evaluation Rev..

[4]  Jr. Frederick P. Brooks,et al.  The Mythical Man-Month: Essays on Softw , 1978 .

[5]  Stanley G. Siegel,et al.  Auditing Throughout the Software Life Cycle: A Primer , 1982, Computer.