Water Fall Model

Water Fall Model

Project Type: Presentation (pptx)

Downloads: 0 - 10 Monday 27th March 2017 Report

Water Fall Model - Overview

------------ PAGE 1 ------------ WATER FALL MODEL By MD. Monirujjaman Sarker SWE, DIU ------------ PAGE 2 ------------ CONTENT’S . History of water fall model . Features of water fall model . Phases of water fall model . Description of the phases . Advantages and Disadvantages ------------ PAGE 3 ------------ HISTORY OF WATER FALL MODEL . Winston w. Royce citied in an article in 1970 . Presented it as non- working model . Ever since widely used for software projects development . Royce didn’t use the term water fall model ------------ PAGE 4 ------------ FEATURES OF WATER FALL MODEL . Easy to flow during development . Can be implemented for any project . Every stage to be done separately . Documentation to be done at every stage . Testing to be done at every phase ------------ PAGE 5 ------------ WATER FALL MODEL VIEW ------------ PAGE 6 ------------ PHASES OF WATER FALL MODEL . Requirment analysis . Design . Coding . Testing . Maintenance Maintenance Step 5 Testing Step 4 Coding Step 3 Design Step 2 Requirment Gathering Step 1 ------------ PAGE 7 ------------ REQUIREMENT GATHERING . 1 st pahse of water fall model . Includes meeting of customer and getting requirements . Most crucial phase any misunderstanding leads to validation issues . Details must be accurated and detailed with no ambiguities . Understand customer requirements and specifications . End product should meet customer expectations . Documented and discussed further with the customer for reviewing ------------ PAGE 8 ------------ REQUIREMENT GATHERING PHASE ------------ PAGE 9 ------------ DESIGN . Customer requirements are broken to various modules for development . Hardware and software modules are identified and designed separately . Algorithm's and diagram's defining scope objective of each model are developed . Intermediate phase between requirement gathering and coding phase . Focuses on program attribute’s such as Data structure sotware architecture algorithm details etc Design needs to be documented for further use ------------ PAGE 10 ------------ DESIGNING PHASE ------------ PAGE 11 ------------ CODING . Design converted to machine readable form code . If design is done effectively then coding can be done effectively . Coding is done by dividing the project into small modules . Programs are created for the small modules than creating for whole project . According to the design the programmers do code for thesoftware . Then the created programme’s are documented ------------ PAGE 12 ------------ CODING PHASE ------------ PAGE 13 ------------ TESTING „X Individual and integrated components are methodlogically verified to ensure that they are error free and meet the requirments of customer „X In the whole testing part is divided into two parts namely 1) inside test 2) outside test . After testing the documentation for testing is to be done ------------ PAGE 14 ------------ TESTING PHASE ------------ PAGE 15 ------------ MAINTENANCE . Final phase of water fall model . Product handed over to customer after alpha and beta testing . After deployment on client side the maintenance team should undertake maintenance activities by visiting client site . Longest phase of software development life cycle which includes meet the changing customer needs adapted to accomdate changes in external environment correct errors and oversights previously undetected in testing phase ------------ PAGE 16 ------------ MAINTENANCE PHASE ------------ PAGE 17 ------------ ADVANTAGES AND DISADVANTAGES . Advantages . Easy to implement . Requires completing one phase before moving to next phase . Easy to develop various software's within small span of time . Disadvantage’s . Not possible to state all requirement's at once during requirement gathering . Working model can be seen only at the end . Backtrack is not possible in this model ------------ PAGE 18 ------------ THANK YOU B. akhil CSE 13E51A0511
Back to top of page