What is the Waterfall Methodology? скачать в хорошем качестве

What is the Waterfall Methodology?

What is the Waterfall Methodology Model? The waterfall model emphasizes that projects should follow a logical progression of steps throughout the software development life cycle (SDLC). As the name implies, each phase of the project cascades into the next, progressively following down like a waterfall. The sequence followed by the Waterfall approach usually follow: 1. Gather the Requirements During this first phase, the potential requirements of the product are methodically collected and written down in a specification document. With this requirements document, project managers plan out every other phase without further customer correspondence until the product is complete. It is assumed that all the requirement gathering happens at this phase. 2. Analyze Requirements With a compiled of ideas that define what the application should do, the next step is to transform them into an actionable plan. During this second stage, you should properly generate the models and business logic that will be used in the application. 3. Translate Business Needs Into Tech Requirements In this phase, design specifications need to be created to outline how exactly the business needs covered in the requirements document will be implemented -- technically speaking. This design process covers technical design requirements, such as programming language, data layers, services, etc. 4. Development This is the implementation phase, when the actual source code is finally written, implementing all models, business requirements, and integrations that were specified in the prior stages. 5. Test the Application In this testing phase, QA and beta testers systematically locate and report problems within the application. From this stage, the project often goes back to the previous stage (sometimes even goes back to the design phase), where the code is re-written, in order to ensure the bugs are fixed. In this case, the project needs to go through testing again, until it is cleared by testers. 6. Launch the Product At this stage, the application is ready for deployment to a live environment, where users can access it and get back to you with more feedback. It is key that customers review the product to make sure that it meets the requirements laid out at the beginning of the project. After the product release, it's important to maintain subsequent support on the product to keep it functional and up-to-date. If you're interested in learning more, then read here: https://producthq.org/agile/product-m... If you're looking to take your product management career to the next level with a PM certification, then go here: https://producthq.org/ Subscribe to our YouTube channel here to keep up with everything product management: https://bit.ly/2WpAxY7 Connect with me here: LinkedIn:   / joshua-fechter   Twitter:   / joshfechter5   Instagram:   / joshua.fechter   #WaterfallModel #WaterfallMethodology #ProductHQ #JoshFechter