![]() In 1983 the paper was republished with a foreword by Benington explaining that the phases were on purpose organised according to the specialisation of tasks, and pointing out that the process was not in fact performed in a strict top-down fashion, but depended on a prototype. This presentation was about the development of software for SAGE. Benington at the Symposium on Advanced Programming Methods for Digital Computers on 29 June 1956. The first known presentation describing use of such phases in software engineering was held by Felix Torres and Herbert D. When first adopted for software development, there were no recognised alternatives for knowledge-based creative work. The waterfall development model originated in the manufacturing and construction industries, where the highly structured physical environments meant that design changes became prohibitively expensive much sooner in the development process. In software development, it tends to be among the less iterative and flexible approaches, as progress flows in largely one direction ("downwards" like a waterfall) through the phases of conception, initiation, analysis, design, construction, testing, deployment and maintenance. The approach is typical for certain areas of engineering design. The waterfall model is a breakdown of project activities into linear sequential phases, meaning they are passed down onto each other, where each phase depends on the deliverables of the previous one and corresponds to a specialization of tasks. Please help update this article to reflect recent events or newly available information.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |