Requirement Gathering and Analysis

During this phase, all pertinent information from the consumer is gathered in
order to build a product that meets their needs. Any discrepancies must be clarified
solely during this step. A meeting with the customer is set up by the business analyst
and project manager to obtain all of the necessary information, such as what the
customer wants to construct, who will be the end-user, and what the product's purpose
is Prior to constructing a product, it is critical to have a solid grasp or expertise of the
product. A customer, for example, wants a financial transaction-related application. In
this scenario, the requirements must be specific, such as what kind of transactions will
be conducted, how they will be conducted, and in what currency they will be conducted.
After gathering requirements, an analysis is conducted to determine the viability of
developing a product. In the event of any ambiguity, a conference call is scheduled for
additional discussion. The SRS (Software Requirement Specification) document is
prepared once the requirement has been well understood. The developers should
properly understand this document, which should also be evaluated by the custom.
Design

The requirements acquired in the SRS document are used as input in this phase,
and the software architecture required to implement system development is derived.

Implementation or Coding

When the developer receives the Design document, the implementation/coding

process begins. Source code is created from the software design. During this phase, all
of the software's components are implemented.

Testing

When the coding is finished and the modules are available for testing, testing
begins. The generated software is thoroughly tested in this phase, and any flaws
discovered are assigned to developers to be corrected. Retesting, also known as
regression testing, is carried out until the program meets the customer's expectations.
To ensure that the software is compliant with the cues, testers consult the SRS paper.

Deployment

Depending on the customer's expectations, the product is either put in the

production environment or initially subjected to UAT (User Acceptance Testing).

Maintenance

After a product is deployed in a production environment, the developers are

responsible for product maintenance, which includes fixing any issues that arise and
any enhancements that need to be made.