Waterfall Model By Zubair YaSeeN

  • View
    104

  • Download
    1

Embed Size (px)

Transcript

  1. 1. Waterfall Model Presented To: Resp. Inam_ul_haq Presented By: Zubair Yaseen 3005 BSIT(E) 4th Semester University of Education Okara (Renala Campus) 4/30/2015 1
  2. 2. Index History of water fall model. What is water fall model. Features of water fall model. Phases of water fall model. Brief description of phases. Advantages. Disadvantages. Conclusion. References 4/30/2015 2University of Education Okara
  3. 3. History of Waterfall Model 1. The first formal description of waterfall model is often cited as a 1970 article by Winston W.Royce. 2. Royce did not use the term waterfall in this article. 3. Royce presented this model as an example of flawed,Non-Working model 4/30/2015 3University of Education Okara
  4. 4. What is Waterfall model The Waterfall is Sequential design process used in software Development process,In which progress is seen as flowing steadily downwards(like waterfall) through the phases of analysis, Design, Implementation, Testing and maintenance. It is also called linear sequential model. 4/30/2015 4University of Education Okara
  5. 5. Features of waterfall model 1. Waterfall model is easy to flow. 2. It can be implemented any size of project. 3. Every stage has to be done separately at the right time so you cant jump stages. 4. Documentation is produced at every stage of a waterfall model allowing people to understand what has been done. 5. Testing is done at every stage. 4/30/2015 5University of Education Okara
  6. 6. Phases of Waterfall model Waterfall model has 5 different phases which are following: 1. Requirement gathering and Analysis. 2. Design. 3. Coding. 4. Testing. 5. Maintenance. 4/30/2015 6University of Education Okara
  7. 7. Phases of Waterfall model 4/30/2015 7University of Education Okara
  8. 8. Brief Description of Phases 1. Requirement gathering and Analysis This is the first phase of waterfall model in which includes a meeting with the customer to understand his requirements. Business analyst will collect the requirements with an interaction of client. System analyst will study the client requirements and prepare the system requirement specification(SRS). 4/30/2015 8University of Education Okara
  9. 9. Brief Description of Phases 1. Requirement gathering and Analysis Requirement gathering and Analysis Phase the basic requirements of the system must be understood by software engineer, who is also called Analyst. All the requirements are then well documented and discussed further with the customer for reviewing. 4/30/2015 9University of Education Okara
  10. 10. Brief Description of Phases 4/30/2015 10University of Education Okara
  11. 11. Brief Description of Phases 2-System Design: Once the user requirements have been established and analyzed. It become necessary to define how the system will be constructed to perform the necessary tasks. Outline overall system architecture. It is an intermediate step b/w requirements analysis and coding. Design architecture is responsible to decide architecture of an application in order to fulfill client requirements 4/30/2015 11University of Education Okara
  12. 12. Brief Description of Phases 4/30/2015 12University of Education Okara
  13. 13. Brief Description of Phases 3- Development &Coding: Actual creation of software User Requirements and System specifications are translated into by coding. Developers will write the software using programming languages and script languages in order to develop the application 4/30/2015 13University of Education Okara
  14. 14. Brief Description of Phases 4/30/2015 14University of Education Okara
  15. 15. Brief Description of Phases 4-Testing: Testing is perform to ensure that the development system work correctly and efficiently. Testing mainly focuses on i. Internal efficiency: It ensures that software is functioning according to the system design and perform its all the required task. 4/30/2015 15University of Education Okara
  16. 16. Brief Description of Phases ii-External Effectiveness: It makes sure that the computer code is efficient standardized and well documented. 4/30/2015 16University of Education Okara
  17. 17. Brief Description of Phases 4/30/2015 17University of Education Okara
  18. 18. Brief Description of Phases 5-Maintenance: This is the final phase of the Waterfall model in which completed software product is handed over to the customer after alpha , beta testing. Maintenance involves monitoring and improving system performance and upgrating to newer version. If the customer suggests changes or enhancement software process has to be followed all over again right from the first phase requirement analysis 4/30/2015 18University of Education Okara
  19. 19. Advantages A waterfall model helps find problems earlier on which can cost a business less than if it was found later on. Requirements will be set and these wouldn't be changed. As everything is documented a new team member can easily understand what's to be done. Implementers have to follow the design accurately 4/30/2015 19University of Education Okara
  20. 20. Disadvantages If requirements may change the Waterfall model may not work. Many believe it is impossible to make one stage of the projects life cycle perfect. Difficult to estimate time and cost for each stage of the development process. Customer can see working model of the project only at the end. If we want to go backtrack then it is not possible in this model 4/30/2015 20University of Education Okara
  21. 21. Conclusion The model is recommended for use only in projects which are relatively stable and where customer needs can be clearly identified at an early stage. 4/30/2015 21University of Education Okara
  22. 22. References wikipedia.com. Computer Science cs504. www.Google.com. 4/30/2015 22University of Education Okara