The classic waterfall model of software engineering is used throughout the production software development community. The escalating costs associated with software development and the unsatisfactory reliability, performance, and functionality of the resulting software have motivated software engineers to develop new alternate models of software development including prototyping, software synthesis, and reusable software. It is difficult to compare and contrast these new models of software development because their disciples often use different terminology, and the models often have little in common except their beginnings (marked by a recognition that a problem exists) and ends (marked by the existence of a software solution). This paper provides a framework which can serve 1) as a hasis for analyzing the similarities and differences among alternate life cycle models; 2) as a tool for software engineering researchers to help describe the probable impacts of a new life cycle model; and 3) as a means to help software practitioners decide on an appropriate life cycle model to utilize on a particular project or in a particular application area.' Index Terms-Reusable software, software development life cycles, software prototyping, software synthesis, waterfall model.

No abstract

This paper is about discipline. It is about discipline that managers should apply to software development. Why is such discipline needed? Quite simply because the software industry has traditionally behaved in an undisciplined manner—doing its own thing. The products that the industry has turned out have typically Contained other than what was expected (usually less, rather than more); Been delivered much later than scheduled; Cost more than anticipated; Been poorly documented; and If you have been involved in any of the situations quoted above, then this paper may be of some help. In short, if you are now, or intend to be, a software seller or buyer, then you should benefit from an understanding of Software Configuration Management. Lest you think that you are not now, or ever will be, a software seller or buyer—keep in mind that the recent technology explosion in electronic component miniaturization has placed the era of personalized computing at hand. In that context, nearly everyone may be considered a potential seller or buyer of software. This paper is about the discipline called Software Configuration Management (SCM). The objective of SCM is to assist the software seller in achieving product integrity and to assist the software buyer in obtaining a product that has integrity.

No abstract

No abstract