Download Software Development Life Cycle: The Waterfall Method and more Thesis Financial Accounting in PDF only on Docsity! ITEC-6150 Unit 2 Assignment Masters of Science in Information Technology ITEC-6150: Principles of Software Engineering Unit 2 Assignment When it comes to developing a software there are various tools and procedures to consider since each business and practice require different criteria and function differently. With developing software there are at least five different development procedures to consider and those procedures are Waterfall, V-Model, Rapid Application, Extreme Programming, and Spiral, and each method has their strengths and weaknesses for the development life cycle. For this assignment we are "part of a four person development team that needs to make a software that will work with a software for a large company". For this method we shall use the Waterfall method and we shall cover what this method is, why we chose this method, the key aspects of this method, and why the other methods didn't work. The Waterfall Method The Waterfall (WF) Method is one of the oldest methodologies for the software development life cycle (SDLC) and it works by "having each phase planned and developed to completion before starting the next phase of development" (Bruegge, 2010). These different phases include "requirements analysis, system design, implementation, testing, deployment, and maintenance" (Bruegge, 2010). Because of this plan of development the method does make it harder to add or change pieces of development, but the method is meant to work by continuously starting the cycle again. Below is an example of a waterfall design (Image by tutorialspoint.com) As the image shows the design is meant to cascade into the next phase until completion, however if changes are made during development then the method starts again in order to accommodate the new changes until completion again. Why This Method The reason for choosing this method is because it's one of the oldest and easiest methods to utilize for a project and even though it doesn't accommodate sudden changes well for a project it does make it "easily manageable and works within deadlines with clear intentions and milestones" (tutorialspoint.com, 2021). This method is a good choice for keeping the project organized and on tasks since the method can't proceed forward until the current phase is completed. Along with this, if the other development group chose to follow the WF method as well it will help create a productive schedule with each group in order for each of them to proceed among the different phases of the project. How This Method Applies to the Project Since this project is meant to work alongside another application it means that the planning would need to take place right away and the goals of the project would have to be well established since the WF method doesn't actually release a working model until the very end of
