IMPORTANT
There are different SDLC models, in some cases the 1 is better than the other. Also important to know, the one Avans uses is not findable on google search. The Avans one can be looked at as synonyms for the one I explain here.
Software development life cycle (SDLC) is a process that is used to design, develop, and test good-quality software. SDLC, or software development life cycle defines the entire procedure of software development step-by-step. The goal of it is to deliver high-quality, maintainable software that meets the userās requirements.
SDLC specifies the task(s) to be performed at various stages by a software engineer or developer. It ensures that the end product is able to meet the customerās expectations and fits within the overall budget. This makes it important for the developer to know about the SDLC beforehand, because otherwise you will most likely already break the cycle.
Stages of the Software Development Life Cycle
Stage-1: Planning and Requirement Analysis
Planning is a crucial step in life, but also in software development. In this step you will also do Requirements Analysis. The information from this analysis forms the building blocks of a basic project. The quality of the project is a result of planning. Thus, in this stage, the basic project is designed with all the available information.
Stage-2: Defining Requirements
At this point, the collected requirements are consolidated into a structured document known as the Software Requirements Specification (SRS). This document outlines in detail everything the software should be able to do, and sets measurable criteria for success. It provides a clear contract between stakeholders and developers and helps to prevent misunderstandings during the later stages of development.
The SRS must be reviewed and approved by customers, market analysts, project sponsors, and other stakeholders. Their validation confirms that the documented expectations truly reflect business goals and user needs. If necessary, revisions are made until all parties reach an agreement. This approval marks the end of the analysis phase and clears the path for the design phase to begin.
Stage-3: Designing Architecture
At this level you design your architecture. This is things like diagrams, wireframes etc. SRS is a reference for software designers to come up with the best architecture for the software. Hence, with the requirements defined in SRS, multiple designs for the product architecture are present in the Design Document Specification (DDS).Ā
This DDS is assessed by market analysts and stakeholders. After evaluating all the possible factors, the most practical and logical design is chosen for development.
Stage-4: Developing Product
At this stage we start developing, developers use a specific programming code as per the design in the DDS. Hence, it is important for the coders to follow the protocols set by the association. Conventional programming tools like compilers, interpreters, debuggers, etc. are also put into use at this stage.
Stage-5: Product Testing and Integration
After the development of the product, testing of the software is necessary to ensure its smooth execution. Although, minimal testing is conducted at every stage of SDLC.Ā Therefore, at this stage, all the probable flaws are tracked, fixed, and retested. This ensures that the product confronts the quality requirements of SRS. Software documentation is an essential part of the software development life cycle. A well-written document acts as a tool and means to information repository necessary to know about software processes, functions, and maintenance. Documentation also provides information about how to use the product. Training in an attempt to improve the current or future employee performance by increasing an employeeās ability to work through learning, usually by changing his attitude and developing his skills and understanding.
Stage-6: Deployment and Maintenance of Products
After detailed testing, the conclusive product is released in phases as per the organizationās strategy. Then it is tested in a real industrial environment. It is important to ensure its smooth performance. If it performs well, the organization sends out the product as a whole. After retrieving beneficial feedback, the company releases it as it is or with auxiliary improvements to make it further helpful for the customers. However, this alone is not enough. Therefore, along with the deployment, the products supervision.
Sources