SDLC - Waterfall Model

SDLC - Waterfall Model

Waterfall models of development are an example of a software development life cycle, or SDLC, model. It gets its name from the way it falls down. The visual aspect of this is what gives its perception to people and what it does, and eventually how it is implemented. There are multiple stages that map the four SDLC phases.

The Decide Phase pertains to deciding what it is that needs to be built, and there are three separate stages to this:

  • Business Case – This is what the user is trying to achieve with the software.
  • User Requirements – This is what the software needs to do in order to achieve the desired business aim.
  • System Specification – This is what the software needs in order for the computer to meet user requirements.

The Design Phase is useful for the various requirements that are mapped to software environments and implementation decisions. There are two separate stages to this phase. They are:

  • System Design – This is how the software will be structured into its separate components.
  • Component Design – This is how a computer will be structured.

The Develop Phase is a construction stage in a waterfall model and deals with the building of components that are required for software. There are many forms and ranges in which software components come in, all of which are configured to meet necessary requirements. There are two types of package software for this phase.

  • Commercial Of The Shelf – These are applications that come in packages that cover the needs of users and are bought and configured from commercial suppliers.
  • Open Source – These are also application packages, but the difference with these is that they are maintained buy a community of users.

The Demonstrate Phase is essentially the test stage which involves proving that software systems meet specifications and requirements of the decide and design phases.

All of these stages and phases make up SDLC waterfall models as they are traditionally used. Further arguments for waterfall models are that it places the emphasis of documentation and source code. The more that is understood about SDLC waterfall models will help businesses to better assess their needs and demands. Another argument is the design in general can be suited to software projects that are more stable when it comes to unchanging requirements.

It is possible and highly likely that designers would be able to predict any problem area of a system thereby being able to produce a proper design correction before it is actually implemented. The waterfall model would then also require that the implementation would accurately follow the design to completion, which would allow for the integration of a system to proceed without incident, all the while providing efficiency.



Available here and other leading retailers:


 

David Peterson

David G. Peterson is a business consultant and author of Handling the Remedy. He has extensive international experience managing projects and operations for large financial institutions. He has worked in North America, Europe, Middle East and Asia skillfully managing business and technical requirements, core systems enhancement and support, merger and acquisition integration's, business process reengineering, off-shoring and outsourcing.