Software Development Life Cycle (SDLC)

Software development lifecycle shortly is SDLC. SDLC aims to produce high-quality system that meets or exceeds customer expectations works effectively and efficiently in the current and planned information technology infrastructure and is inexpensive to maintain and cost effective. To enhance the process followed in your software project is SDLC. Each phase of SDLC produces deliverables acquired by the next phase in the lifecycle. Requirements are translated into design, code is produced according to the design. 

Testing should be done on develop the product based on requirement. Deployment should be done after the completion of testing. A typical software development life cycle consists of the following phases:

• Requirement phase 
• analysis phase
• design phase
• development phase
• testing phase
• deployment Phase
• maintenance phase 

 

Requirement Phase

Let's see each and every phase in detail. First one requirement phase requirement gathering and analysis is the most important phase in software development life cycle. Business enlist collects the requirement from the customer or client as per the clients business needs and documents the requirements in the business requirement specification document name bearish depends upon the organization.Some examples are customer requirement specification CRS, business specification BS, business requirement document etc and provides the same to the development team.

Analysis Phase

Analysis phase once the requirement gathering and analysis is the the next step is to define and document the product requirements and get them approved from the customer. This is done to software requirement specification document SRS consists of all the product requirements to be designed and developed during the project lifecycle keep it will involved in this phase. Our project managers business analyst and senior members in the team the outcome of this phase is software requirement specification design phase.

Design Phase

 This phase has two steps hitch LD high level design. It gives the architecture of the software product to be developed and is done by architects or senior developers.LLD low level design it is done by senior developers it describes how each and every feature in the product should work and how every component should work. Here only the design will be dead and not the code the outcome from this phase is high level document and low level document which works as an input to the next phase. 

Development Phase

Development phase developers of all levels seniors juniors freshers involved in this phase. This is the phase where we start building the software and start writing the code for the product. The outcome from the space is source code document and developed the product testing phase. 

Testing Phase

When the software is ready it is sent to the testing department where tester test it thoroughly. They either test the software manually or by using automated testing tools depends on process defined in STLC and ensure that each and every component of the software works fine. Once the QA make sure that the software is error-free it goes to the next stage which is implementation. The outcome of this phase is the quality product and the testing artifacts. List out the test deliverables is one of the most popular interview questions.

Deployment Phase

Deployment and maintenance phase. After successful testing the product is delivered or deployed to the customer for their use. Deployment is done by the deployment or implementation engineers. Once when the customer start using the develop the system then the actual problems will come up and needs to be solved from time to time the process. Where the care is taken for the develop the product is known as maintenance. 

Maintenance Phase

100% testing is not possible because the way testers test the product is different from the way customers uses the product. Maintenance should be done as per service level agreement. let's see types of software development life cycle models Waterfall spiral V model prototype and agile the other related models are rapid application development rational unified model hybrid model etc.