1. What is SDLC?

SDLC is a systematic process for building software that ensures the quality and correctness of the
software built. SDLC consists of a detailed plan which explains how to plan, build, and maintain
specific software. Every phase of the SDLC life Cycle has its own process and deliverables that feed
into the next phase.
Requirements Collection & Analysis
The requirement is the first stage in the SDLC process. It is
Roles and responsibilities: 
conducted by a team of members with inputs from all the
stakeholders and domain experts in the industry. This stage gives • Client / Product Owner Drives the
a clearer picture of the scope of the entire project and the Requirements Detailing
anticipated issues, opportunities, and directives which triggered • Dev Team: Gathering the requirements
the project. Requirements Gathering stage needs teams to get
detailed and precise requirements. This helps companies to • Output / Outcome: Requirement
finalize the necessary timeline to finish the work of that system. Specification document
Feasibility Study
Once the requirement analysis phase is completed the next sdlc step is to Roles and responsibilities: 
define and document software needs. This process is conducted with the
• Client / Product Owner Approves the SRS
help of the ‘Software Requirement Specification OR SOW’  document also
document
known as the ‘SRS’ document.
• Dev Team: Build SRS document
There are mainly five types of feasibilities checks:
• Output / Outcome: Agreement between
• Economic: Can we complete the project within the budget or not?
Product Owner and Dev Team on SRS document
• Legal: Can we handle this project as per policies / other regulatory
compliances?
• Operation feasibility: Can we create operations which are expected by
the client?
• Technical: Check whether the current computer system / infra can
support the software?
• Schedule: Decide that the project can be completed within the given
schedule or not?
Design
In this third phase, the system and software design documents are
Roles and responsibilities: 
prepared as per the requirement specification document. This helps
• Client / Product Owner Reviews the
define overall system architecture. There are two kinds of design Architecture, Tech Stack & Design documents
documents developed in this phase:
• Dev Team: Build Architecture, Tech Stack &
High-Level Design (HLD)
Design documents
• Brief description and name of each module
• An outline about the functionality of every module • Output / Outcome: Build consensus and agree
• Interface relationship and dependencies between modules on Architecture, Tech Stack & Design
• Database tables identified along with their key elements documents
• Low-Level Design(LLD)
• Functional logic of the modules
• Database tables, which include type and size
• Complete detail of the interface
• Addresses all types of dependency issues
• Listing of error messages
• Complete input and outputs for every module
Coding
In this phase, developers start to build the entire system
Roles and responsibilities: 
by writing code using the chosen programming
• Client / Product Owner will act as an
language. In the coding phase, tasks are divided into Observer
units or modules and assigned to the various
• Dev Team: Implements 
developers.
• Output / Outcome: Feature
Development
Testing
• Once the software is complete, it is deployed in the testing
environment. The testing team starts testing the functionality Roles and responsibilities: 
of the entire system. This is done to verify that the entire • Client / Product Owner will act as an
application works according to the customer requirement. Observer
• During this phase, the QA / testing team may find some • Dev Team: Verify Implementation
bugs/defects which they communicate to developers. The • Output / Outcome: Dev Team Certify
development team fixes the bug and sends it back to QA for a
Build for Deployment
re-test & closure.
Deployment
Once the software testing phase is over and no bugs or
Roles and responsibilities: 
errors left in the system then the final deployment
• Client / Product Owner will act as an
process starts. Based on the feedback given by the project
Observer
manager, the final software is released and checked for
deployment issues if any. • Dev Team: Administer Deployment
Activities
• Output / Outcome: Complete
Deployment
Maintenance
Once the system is deployed, and customers start using the
developed system, following 3 activities occur Roles and responsibilities: 
• Bug fixing – bugs are reported because of some scenarios • Client / Product Owner will act as an
which are not tested at all approver for bugs / upgrade / Change
Request
• Upgrade – Upgrading the application to the newer versions
of the Software • Dev Team: Implementation
• Enhancement – Adding some new features into the existing
• Output / Outcome: Bugs / Upgrade /
software
Enhancements deployment
The main focus of this SDLC phase is to ensure that needs continue
to be met and that the system continues to perform as per the
specification mentioned in the first phase.