Waterfall Methodology
- 1. WATERFALL METHODOLOGY 2 3 . 4 . 2 1
- 2. AGENDA T R A D I T I O N A L P R O C E S S M O D E L S H I S TO RY W H AT I S WAT E R FA L L ? S D L C O F WAT E R FA L L M O D E L W H E N I S WAT E R FA L L U S E D ? A D VA N TA G E S A N D D I S A D VA N TA G E S E X A M P L E S WAT E R FA L L V S A G I L E 2
- 3. 3 INTRODUCTION T R A D I T I O N A L P R O C E S S M O D E L S Waterfall model-The process is strictly sequential. Prototyping model- reduce risk by building a quick replica or mockup of the intended system Spiral model- Follows an evolutionary approach 3
- 4. THE WATERFALL METHODOLOGY L E T ’ S D I V E I N 4
- 5. What is Waterfall? The Waterfall Model was the first Process Model to be introduced. It is also referred to as a linear-sequential life cycle model. It is very simple to understand and use.
- 6. 6 6 This model was 1st introduced by Dr. Winston W. Royce in a paper published in 1970. It is a software development process. The waterfall method emphasizes on logical steps to be taken during using waterfall implementation. HISTORY OF WATERFALL
- 7. 7 F a c t s a b o u t S D L C W AT E R F A L L 7 • Used for embedded systems (by Sommerville) • Stable Requirements, not changed frequently and should be well understood(hardware used systems ) • Less Customer involvement • It is plan driven model used when risk is high like a risk of life e.g insulin pump delivery system.. WHEN IS THE WATERFALL METHODOLOGY USED?
- 8. SDLC OF WATERFALL MODEL 8 S O F T W A R E D E V E L O P M E N T L I F E C Y C L E Directly Reflects the Fundamenta l Developmen t Activities Communication Project initiation Requirements gathering Planning Estimating Scheduling Tracking Modeling Analysis Design Construction Code Test Deployment Delivery Support Feedback
- 9. 9 9 PHASE ACTIVITIES COMMUNICATION Inception , elicitation , negotiation ,specification , validation. (Consider all the requirements then Brainstorm them Do the requirement feasibility test to ensure that the requirements are testable or not). PLANING Identify task and their sequence , assign resources, calculate milestone, scheduling task ,cost estimation, time identification. System modelling • Analysis of requirements • Design the solution CONSTRUCTION a. Coding b. b. System testing • Now based on the design create the code. Fit in the codes for the next phase • Test the code to make sure it works exactly as its supposed to.
- 10. CONTINUATION… 10 PHASE ACTIVITIES SYSTEM DEPLOYMENT (deliver the solution and take feedback) SYSTEM MAINTENECE Make sure that the application is up and running in the respective environment
- 11. ADVANTAGES AND DISADVANTAGES O F T H E W A T E R F A L L M E T H O D O L O G Y 11
- 12. 12 W AT E R F A L L M E T H O D O L O G Y 12 • Simple and easy - Simple and easy to understand and use. • Beneficial for smaller projects- For smaller projects, the waterfall model works well and yield the appropriate results. • Sequential- Since the phases are rigid and precise, one phase is done one at a time, it is easy to maintain • Shows progress- Waterfall project management also shows progress simply. The clear milestones described in the first phase make it easy to determine if a project is moving forward on schedule. • Single order- The entry and exit criteria are well defined, so it easy and systematic to proceed with quality. • Documented without iterations- Results are well documented. • Easy managing- The linear nature of the system, make waterfall projects easy to manage. ADVANTAGES OF
- 13. 13 W AT E R F A L L M E T H O D O L O G Y 13 • Cannot adopt the changes in requirements • It becomes very difficult to move back to the phase. For example, if the application has now moved to the testing stage and there is a change in requirement, it becomes difficult to go back and change it, It is impossible. • Delivery of the final product is late as there is no prototype which is demonstrated. • For bigger and complex projects, this model is not good as a risk factor is higher. • Not suitable for the projects where requirements are changed frequently. • Does not work for long and ongoing projects. • Since the testing is done at a later stage, it does not allow identifying the challenges and risks in the earlier phase so the risk assessment is difficult. DISADVANTAGES OF
- 14. EFFECTIVE AND INEFFECTIVE PROJECT CHOICES O F T H E W A T E R F A L L M E T H O D O L O G Y 14
- 15. 15 W AT E R F A L L M E T H O D O L O G Y 15 • . EFFECTIVE PROJECT CHOICES Defense Department Military and Aircraft Forces Constructio n Nuclear materials Space Shuttles WELL- UNDERSTOOD PROBLEMS Embedded Systems 1. Frozen Requirements 2. Mission Critical Projects 3. Embedded Systems 4. External Projects Involved(hardware Related)
- 16. 16 W AT E R F A L L M E T H O D O L O G Y 16 IN-EFFECTIVE PROJECT CHOICES Games You can afford to handle 1. Changing requirements 2. Customer involvement Web based Stock Trading
- 17. 17 W AT E R F A L L M E T H O D O L O G Y 17 WATERFALL INCREMENTAL AGILE SPIRAL Plan Based less planning less plan keep it simple detail plan Traditional Traditional modern approach evolutionary Less Client involvement high client involvement high client involvement involvement minimal Very costly while Changing in requirement accept changes so does not change frequently easy adaptation Expensive to change WATERFALL VS OTHERS
- 18. . C O U R S E : S o f t w a r e D e v e l o p m e n t B 1 9 1 0 3 0 4 7 N E H A H A R O O N B 1 9 1 0 3 0 2 4 M A H E E N A B D U L WA H I D B 1 9 1 0 3 0 5 1 R U TA B A I M R A N SUPERVISOR : Prof. Farzeen Ashfaq TEAM MEMBERS B19103067 WAIZA WAQAR .
- 19. THANK YOU! .