Connie FarrisSystems Analysis, Design and Integration(IT425-1801A-03) Crispin Jose SDLC Methods A methodology is used to structure, plan and control the software development process. In simple terms, we can describe SDLC as the methodology that a developer might use to standardize the process of software development. Many SDLC models are available, choosing the right method is not an easy decision, so we are going to highlight the main advantages and disadvantages of some commonly used SDLCs.Waterfall ModelThis, in my opinion. the simplest life-cycle methods. When one phase is complete, it is then checked and verified before moving to the next phase. There are six steps: 1. Requirement analysis, 2. Design, 3. Implementation, 4. Testing, 5. Installation and 6. Maintenance. Advantages:Easy to understand and use.Each phase is completed separately from the other phases.Good for little projects where the requirements have been defined.Disadvantages:Working software is not produced until late in the project. Risk and Uncertainty are very high. If it is a large project this method is not a good choice. Spiral MethodInvolving various users to point out the numerous aspects of the system, the requirements of the system are established. The most critical step in the spiral model is to create a basic design for the new system to generate cost-effective strategies. The procedure uses a fourfold process, this process includes strengths, weakness and risk evaluated, requirements determined, planning and design, development and testing.Advantages:Works well for large projectsWorking software is developed early in the lifecycle.Risk analysis is very highDisadvantages: Higher CostNot good for small projectsRequires high expertise in risk analysis to be a success Prototype ModelThis model is used to best the shortcomings of the waterfall module. Instead of halting the requirements before design, a prototype is built based on the current requirements. giving the clients a better understanding of the final product.Advantages:User inputs proves benefits With a working model provided, the users get a better comprehension of the system being built.Since the system is using prototypes, errors and risks can be discovered early stages.Disadvantages:The complexity of the system is increasedInvolves higher risk because of exploratory methodologyErrors are an ingrained part of the development process since the system is implemented, then repaired as it is built.