Waterfall model in system development life cycle


Published on

Waterfall Model in SDLC system development life Cycle this model is used to developed software according to the requirement of the Users.... in any business this model is using commonly

Published in: Education, Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Waterfall model in system development life cycle

  1. 1. WATERFALL MODEL IN SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) The waterfall model of the software life cycle which 1st put forward by Royce in 1979. It become popular in the 1970s. However, when Boehm brought attention to it. there are many variants of the waterfall model depending on the organization the use the model and the specific projects. Presentation by Management Study Online (MSO)
  2. 2. SEQUENTIAL WATERFALL MODEL The Above figure depicts Linear-Sequential Waterfall model. Another variant of the waterfall model is the one in which each phase's results flow into the next and the process. Ideally process in an orderly fashion. this can be illustrated from the next figure.
  3. 3. FIG 2 : WATERFALL MODEL In the waterfall model "With feedback the process is structured as a cascade of phases where the output of one phase constitute the input to the next one.
  4. 4. 1. FEASIBILITY STUDY  Feasibility study is study about finding out the Problems. in this phase feasibility is an evaluation and analysis of the potential of proposed which is based on extensive investigation and research to support to process in decision making. Aims  Work out on overall understanding of the problems.  Generate Different Solution for solving the Problem.  Find out the Solution among alternative which is suitable and best.  Analysis each and every alternatives solution in terms of :  What are the Resources Required  What are the Cost of Development  How much time taken in development etc
  5. 5. 2. REQUIREMENT ANALYSIS AND SPECIFICATION  In this phase Developer understand the exact requirements of the customers. after the knowing requirement of the customers. developer need to gathering information and analysis it. Aims  Requirement gathering and analysis  Analysis the collected data.. is relevant or not  Requirement specification  Find out if any requirement is not completed. and solve it.
  6. 6. 3. DESIGN AND SPECIFICATION  In this design phase developer transform the Gathered requirement specification data into a particular format and bring it in a structure format.  Aims  Design phase transforms requirement specification data into a Programming language structure.  Bring all gathered customers requirement in a particular format for developing the software.
  7. 7. 4. CODING AND MODULE TESTING  In this Phase developer start developing this software. now in this phase developer start coding using programming language according to the requirement of the customers. Aims  Convert software design into source code.  Dividing in module if software have many function.  Testing each module after the coding. if developer test individual module is working correctly or not.
  8. 8. 5. INTEGRATION AND SYSTEM TESTING  In this phase after the developing every module and its testing developer integrate all module and made one software/system. "For example: developer divided one software into 4 module and after the developing of module 1, 2, 3, and 4 developer integrate all module each other and developed one software" after the integration he test whole software and test each and every functions of the software. Aims  Integrate all module in a system.  Ensure that the developed system functions working according to the requirement of the customers as specified in the document.
  9. 9. 6: DELIVERY  In this phase of waterfall model after the complete development of the software. developer distribute and provide software to users for fulfilling users needs and Desire.
  10. 10. 7. MAINTENANCE  Corrective Maintenance:  Corrective maintenance is kind of maintenance in which correct errors which are not discovered during the projects development phase.  Perfection Maintenance:  Perfection maintenance in also a kind of maintenance in which developer improve implementation of the system.  and developer try to enhance the Facilities and Functions of the system.  Adoptive Maintenance:  As per the Environment Software must be maintenance. (For example:- A software which is developed for Window xp in 2005 but Now peoples are using Window 7 or 8. in this case developer maintain his software and develop according to window 7 and 8 supporting).
  11. 11. All Content Are Written by MSO Team http://www.managementstudyonline.in/ You are free to use these Presentations for your personal and business presentations. Don’t do this.  Resell or distribute these Presentations.  Put these Presentations. on a website for download. This includes uploading them onto file sharing networks like Slideshare, Myspace, Facebook, bit torrent etc  Pass off any of our created content as your own work