water fall model
TRANSCRIPT
![Page 1: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/1.jpg)
![Page 2: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/2.jpg)
01
softw
are GROUP MEMBRERS
Maria Saleem(91)Anisa Zia(07)
![Page 3: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/3.jpg)
2
SO
FTW
AR
EWater fall Model
HISTORY• The first model description in 1970 by Winston • W.ROYCE. Presented as an example of non working model It has been widely used for software projects.
![Page 4: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/4.jpg)
2
SO
FTW
AR
EWATER FALL MODEL• features• First SDLC model• Oldest model• Linear sequential model• Simple to understand • easy to implement
![Page 5: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/5.jpg)
• Phases of water fall modelWaterfall model has 5 different phases, Which are following.
1)Requirement gathering and Analysis.2)Design.3)Coding.4)Testing.5)Maintenance.
![Page 6: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/6.jpg)
2
Wat
er fa
ll m
odel
pha
ses
Water fall modelRequireme
nt gathering
System design
• Design documentsimliimenntation
• Developed software
Testing Deployment phase
Quality assure
Requirement specification
maintenance
![Page 7: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/7.jpg)
03
RE
QU
IRE
ME
NT
PH
AS
E 1) Requirement gathering and analysis
• Meeting with customer• Software definition must be detailed• And no ambiguities.• Important to understand the • Customer requirements and • Expectations so that end product • So that end product meets his • Specification.
![Page 8: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/8.jpg)
04
Use
r com
mun
icat
ion
![Page 9: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/9.jpg)
Design• The customer requirements are
broken down into logical modules for the ease of implementation. Hardware and software requirements for every module are Identified and designed accordingly.
![Page 10: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/10.jpg)
![Page 11: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/11.jpg)
Coding is a step in which design is translated into machine-readable form.
coding
Develop design into code.Implementations of working application
according to the requirements of the user Developed software
![Page 12: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/12.jpg)
![Page 13: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/13.jpg)
Testing is the process of executing a program for finding an error
Verification and validation of software
testing
![Page 14: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/14.jpg)
![Page 15: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/15.jpg)
This is the final phase of the waterfall model, in which the completed software product is handed over to the client after alpha, beta testing.
After the software has been deployed on the client site, it is the duty of the software development team to undertake routine maintenance activities by visiting the client site.
If the customer suggests changes or enhancements the software process has to be followed all over again right from the first phase i.e requirement analysis.
MAINTENANCE
![Page 16: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/16.jpg)
![Page 17: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/17.jpg)
The water fall model is easy to implementation.
For implementation of small systems water fall model is use full.
The project requires the fulfillment of one phase, before proceeding to the next.
It is easier to develop various software through this method in short span of time.
ADVANTAGES OF WATER FALL MODEL
![Page 18: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/18.jpg)
The requirement analysis is done initially and sometimes it is not possible to state all the requirement explicitly in the beginning.
The 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.
It is difficult to follow the sequential flow in software development process.
DISADVANTAGES OF WATER FALL MODEL
![Page 19: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/19.jpg)
![Page 20: Water fall model](https://reader036.vdocuments.mx/reader036/viewer/2022070518/58eb7a141a28ab90578b45ed/html5/thumbnails/20.jpg)
THANK YOU