Notes. Water Fall Model:. Introduction:. In 1985, The United

1196 WordsMar 4, 20175 Pages
NOTES Water Fall Model: INTRODUCTION: In 1985, the United States Department of Defense captured this approach in DOD-STD-2167A, their parameter for working with software development agents, which stated that "the agent shall apply a software development cycle that includes the 6 phases: Requirement Engineering, Analysis& Design, Implementation, Integration and Testing, Deployment, Maintenance". Steps of Water Fall Model: REQUIREMENT ENGINEERING: DEFINITION: Requirement engineering is the process of determining user’s need for a new & modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often…show more content…
Development moves from requirements, through design, implementation, testing, installation, troubleshooting, and ends up at maintenance. Each phase of development proceeds in proper order. Disadvantage: The disadvantage of waterfall development is that it does not allow for much revision. Once an application is in the testing stage, it is very difficult to go back and change something that was not well-documented. PROS Corns Simple and easy to use. Easy to manage Phases are processed and completed one at a time. Works very well for smaller projects Clearly defined stages. Well understood milestones. Easy to arrange tasks. Results are well documented. No software is produced until late during the life cycle. High amounts of risk Not a good model for complex and object-oriented projects. Poor model for long and ongoing projects .Not suitable for the projects where requirements are at a moderate to high risk of changing. So risk and uncertainty is high with this process model. It is difficult to measure progress within stages. Cannot accommodate changing requirements. Adjusting scope during the life cycle can end a project. Integration is done as a "big-bang. at the very end, which doesn 't allow identifying any technological or business bottleneck or challenges early. Diagram: Incremental: Introduction: This model is a process of software development where the
Open Document