Waterfall Software Life Cycle Model

he following diagram draws from the sphere of engineering, showing the traditional (also known as classic) and most straightforward approach to constructing software, the Waterfall Software Life Cycle Model. You can modify this plan to your needs, as the aim is to give you a starting point from which you can properly consider the work ahead. All modern software development models, including RAD and XP, have their roots in this approach. On the diagram, there is some scale implied in the length of the boxes left to right. Notice that the arrows can feed back up the process. This is important because if things start to go wrong somewhere down the line, you may need to back up one or more steps to get to the reason why. Idea This is literally just the idea, the first inspiration, the vision. This really is the realm of dreams, but realising the dream is where the Waterfall model comes in. Analysis This is the stage where the nitty gritty of the idea begins to be explored. What is involved? What will it need to make it happen? How long will it take? And the all important question: is if feasible? Often an idea will be reconsidered, or at least tempered at this stage, and that’s fine. In fact, it’s probably desirable, because it means that the concept is being fully explored, and thought is genuinely being given to what can be achieved with the resources available. It’s a lucky idea that has unlimited resources! Design Feeding from your analysis, you begin to design. This stage will often feed back and forth...

Pin It on Pinterest