What are the steps for software development in waterfall model?

Asked By 220 points N/A Posted on -
qa-featured

Hi All,

What are the steps for software development in waterfall model? Regards. Thanks for the help.
SHARE
Best Answer by mwendamartin
Best Answer
Best Answer
Answered By 0 points N/A #89572

What are the steps for software development in waterfall model?

qa-featured
The steps followed by software developers in Waterfall methodology in software development include:
  • Requirement analysis and Elicitation.
  • Designing the software.
  • Development of the software.
  • Testing and implementation.
  • User training and software maintenance.
Answered By 0 points N/A #89575

What are the steps for software development in waterfall model?

qa-featured
Waterfall model is also called the classic life cycle or linear sequential model it goes through the following stages:
  1. Analysis phase, this phase tries to answer the question of, what is required to make the system work? Here a system analyst gathers the system requirements and user requirements.
  2. Design phase, this focuses on translating the requirements into representation of the system, tries to answer the question of, how do we realize the system as specified by gathered requirements? This is usually documented.
  3. Coding, this involves writing of collective pieces of lines instruction which are machine readable. The system now becomes a n entity that can be utilized.
  4. Testing, carried out by a test Engineer to ensure that input fed to a computer produces desired results. The system internal is also checked for errors and correction done. Can be of two types Alpha testing – testing done at the Developers site and Beta testing – testing done at the users site.
  5. Support, this is where all the above phases are reapplied to software due to changes encountered e. g. customer demand enhancements, changes in environment it was deployed or due to errors encountered.
Since its is the oldest software development process model it has encountered several disadvantages namely:
  • Software products nowadays rarely follow the development phases as required by this model.
  • It has difficulty in accommodating user’s uncertainty.  Therefore, not all users requirements are captured as required.
  • Patience is needed since a working product will only be available at end of the process.
  • It's still widely used due to its systematic and disciplined approach.

Login/Register to Answer

Related Questions