To see the differences between this two methodologies lets see their features.
Waterfall Methodology
-The documentation is very important , all the document referents to architecture must be done before the coding start
-Waterfall suppose that there will not be change along the development of the final product
- Start up whit the requirements gathering
- Are based on the contract, for that reason the requirements of the client and the documentation is so important
-Its development is document driven
-The integration of different modules occur and the end
-The communication with the bussines people only occur at the beginning of the project
-It’s focused on analysis and design for that reason relies on the architects and designers
- The final product is not only composed by the software itself but can include the documentation , the user manual and others.
-Each developer is in charge of one different area of the development
Keep reading
