1. Waterfall Model :- The Waterfall model is a popular and traditional version of the SDLC model for developing software. It specifies a sequential flow which the software must undergo.
Imagine a waterfall on the cliff of a steep mountains, once the water has flowed and begun its journey down the side, it can not turn back. The same case with the Waterfall mode, once a development phase is completed the development proceeds to the next phase and there is no back tracking possible. It is also called Linear Sequential Model.
The phases of Waterfall model are :-
1. Requirement Gathering/Analysis
2. Design
3. Coding
4. Testing
5. Implementation
1. Requirement Gathering/Analysis :- In this phase business analyst gather information about what the customer needs, and analysis all aspect related to requirement and other details. All the information collected from the customer is captured in a formal document called System Requirement Specification(SRS). Which serves as an input to the next phase.
2. Design :- In this phase we define the hardware and software architecture, components, modules, interfaces and data to satisfy the requirement specified in the SRS documents.
3. Coding :- Based on the system design document the developers starts coding. The system is developed in units. Complete integration of small units is performed to create the final software package.
4. Testing :- In this phase, both units and integrated once are verified to ensure that they are error free and meet the customer requirements which is given in the SRS document.
5. Implementation :- In this phase we deploy the developed product in its target location/environment. This task is performed by developers with the help of some tools like compilers, debuggers, interpreters etc.
Waterfall Model is suitable for the project where :-
1. Requirement are clearly defined
2. Usefull for small and medium time duration projects
3. Use where technology is stable
4. Familier with the domain and development environment.
Advantages of Waterfall model :-
1. Simple and easy to use and understand.
2. It works for small projects where requirements are clearly defined.
3. Project under control.
4. Predefined outputs at every cycle.
5. Early identifucation of slippage if any.
Disadvantages of Waterfall model :-
1. Poor for long and large projects
2. Risk chances is higher
3. Backtracking is not possible
4. Not feasible for complex projects
5. Customer requirement may change
Imagine a waterfall on the cliff of a steep mountains, once the water has flowed and begun its journey down the side, it can not turn back. The same case with the Waterfall mode, once a development phase is completed the development proceeds to the next phase and there is no back tracking possible. It is also called Linear Sequential Model.
The phases of Waterfall model are :-
1. Requirement Gathering/Analysis
2. Design
3. Coding
4. Testing
5. Implementation
1. Requirement Gathering/Analysis :- In this phase business analyst gather information about what the customer needs, and analysis all aspect related to requirement and other details. All the information collected from the customer is captured in a formal document called System Requirement Specification(SRS). Which serves as an input to the next phase.
2. Design :- In this phase we define the hardware and software architecture, components, modules, interfaces and data to satisfy the requirement specified in the SRS documents.
3. Coding :- Based on the system design document the developers starts coding. The system is developed in units. Complete integration of small units is performed to create the final software package.
4. Testing :- In this phase, both units and integrated once are verified to ensure that they are error free and meet the customer requirements which is given in the SRS document.
5. Implementation :- In this phase we deploy the developed product in its target location/environment. This task is performed by developers with the help of some tools like compilers, debuggers, interpreters etc.
Waterfall Model is suitable for the project where :-
1. Requirement are clearly defined
2. Usefull for small and medium time duration projects
3. Use where technology is stable
4. Familier with the domain and development environment.
Advantages of Waterfall model :-
1. Simple and easy to use and understand.
2. It works for small projects where requirements are clearly defined.
3. Project under control.
4. Predefined outputs at every cycle.
5. Early identifucation of slippage if any.
Disadvantages of Waterfall model :-
1. Poor for long and large projects
2. Risk chances is higher
3. Backtracking is not possible
4. Not feasible for complex projects
5. Customer requirement may change
great article on waterfall model. can you plz post more testing models? thanks you are doing great job. Keep posting
ReplyDeleteHi Kelvin thanx for reading my article. Sure i will post all software development models and other software testing articles very soon. Keep visiting my blog
Delete