Software Development Life Cycle

1470 Words6 Pages
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) Software Development Lifecycle is a structure used to show us all the phases performed during the software development process. It shows us the methodologies used to improve the quality and overall software development process. The SDLC is a structure followed by developers, mainly the teams in software organizations to describe how they can develop, maintain and replace specific software. Phases of Software Development Life Cycle (SDLC) Requirement gathering and analysis In the Software Development Life Cycle, this is the most vital phase of them all, where the client or customer meets with the manager and project team (software developers, system analyst, technical architects etc.)…show more content…
Implementation & coding. Implementation: With implementation, this is where the project team makes the actual product. The overview and the idea of the project become clearer. The project team begins to build and code the software. Coding: The Designing of the software must be done properly and also the required information must be gathered accurately, the coding process will have different phases as which when linked together they will form the end product of what’s needed. The project team must meet the deadlines for the software coding if the customer has given correct information to conduct the project. Testing This is the phase where the experienced testers focus on investigation and discovery to test the system against the requirements of the customer. The tester tests for defects within the system to verify if the system behaves as expected and according to the requirements, if there are any defects, it is not possible sometimes to solve all the failures but it will help in reducing the errors of the…show more content…
In this modeling, the process is not allowed to go back to the previous phase to do some changes. Advantages - Friendly to the user - System verification in each phase helps detect errors - Construction approach - The user I able to plan the system Disadvantages - More time required - Almost no small room for iteration - Change not easily responded to V-Shaped Model In addition to the waterfall model, it bent upwards like a V shape after the implementation phase. Validation on the other side of v where validation is on the 1st side of v and the sides are joined by the coding phases Advantages - Straightforward and easy to implement - Functions effectively where the demands are easily met - Enables the user to verify and validate the developed system at an early
Open Document