Evolutionary Delivery versus the "waterfall model"
暂无分享,去创建一个
The conventional wisdom of planning software engineering projects, using the widely cited "waterfall model" is not the only useful software development process model. In fact, the "waterfall model" may be unrealistic, and dangerous to the primary objectives of any software project.The alternative model, which I choose to call "evolutionary delivery" is not widely taught or practiced yet. But there is already more than a decade of practical experience in using it. In various forms. It is quite clear from these experiences that evolutionary delivery is a powerful general tool for both software development and associated systems development.Almost all experienced software developers do make use of some of the ideas in evolutionary development at one time or another. But, this is often unplanned, informal and it is an incomplete exploitation of this powerful method. This paper will try to expose the theoretical and practical aspects of the method in a fuller perspective. We need to learn the theory fully, so that we can apply and learn it completely.
[1] Philip Gilbert. Software design and development , 1986 .
[2] Tom Gilb. Software engineering: using "design by objectives" tools (DBO) , 1984, SOEN.
[3] Carolyn Wong. A Successful Software Development , 1984, IEEE Transactions on Software Engineering.