SDLC Life Cycle

 SDLC Life cycle: 

             Software Development Life Cycle (SDLC), A life cycle model represents all the methods required to make a software product transit through its life cycle stages. Different life cycle models may plan the necessary development activities into phases in different ways, Proper planning and execution are the key components of a successful software development process.

Why Need of SDLC Life Cycle:

• development of a software product in a systematic and disciplined manner
• clear understanding among team representatives about when and what to do
• describes entry and exit criteria for each phase
• It provides a foundation for project planning, scheduling, and estimating.
• It establishes a framework for a consistent set of activities and deliverables.
• It serves as a tool for project tracking and control.
• It improves the visibility of project planning to all stakeholders involved in the development process.
• It accelerates and enhances the speed of development

SDLC Life cycle:

The stages of SDLC:

1. Planning and requirement analysis:

                                          Is the most important and necessary stage in SDLC, Planning is the crucial step in everything and so as in software development, requirement analysis is also performed by the developers of the organization. the requirement comes from the customers, sales department/market surveys.

The business analyst and Project organizer set up a meeting with the client to gather all the data like what the customer wants to build, who will be the end user, and what is the objective of the product. Before creating a product, a core understanding or knowledge of the product is very necessary.

                                         

Once the requirement is understood, the SRS (Software Requirement Specification) document is created. Also, refers the BRD Documents

2. Defining: 

                   

                    Once the requirement analysis is done, the next stage is to certainly represent and document the software requirements and get them accepted by the project stakeholders.

This is accomplished through the "SRS"- Software Requirement Specification document which contains all the product requirements to be constructed and developed during the project life cycle.

3. Designing:

The next phase is about bringing down all the knowledge of requirements, analysis, and design of the software project. This phase is the product of the last two, like inputs from the customer and requirement gathering.

4.Developing:

In this phase of SDLC, the actual development begins, and the programming is built. The implementation of design begins concerning writing code. Developers have to follow the coding guidelines described by their management and programming tools like compilers, interpreters, debuggers, etc. are used to develop and implement the code

5. Testing:

After the code is generated, it is tested against the requirements to make sure that the products are solving the needs addressed and gathered during the requirements stage.

Type of testing

• unit testing
• integration testing 
• system testing
• acceptance testing 
• Regression Testing
• Sanity Testing
• Smoke Testing
• Performance Testing

6. Deployment:

                 Once the software is certified, and no bugs or errors are stated, then it is deployed.

Then based on the assessment, the software may be released as it is or with suggested enhancement in the object segment.

After the software is deployed, then its maintenance begins.

7. Maintenance:

                         Once when the client starts using the developed systems, then the real issues come up and requirements are to be solved from time to time.

This procedure where care is taken for the developed product is known as maintenance.

Advantages:

• Efficient with regard to costs
• Efficacious in terms of time
• Enhances teamwork and coordination, defines suitable roles for employees and increases workplace transparency.
• Minimal danger when the project is implemented