Scribd
Upload
42 views

What Is SDLC?: Requirement Gathering and Analysis

The document discusses Software Development Lifecycle (SDLC), which is a systematic process for building software that ensures quality. It consists of phases like requirements gathering, design, coding, testing, and deployment. The waterfall model is the traditional sequential SDLC model, while agile is an iterative incremental model that focuses on flexibility over requirements. Both approaches have advantages like structure and adaptability, as well as disadvantages like rigidity and lack of documentation.

Uploaded by

Sakshi Shriwas
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
42 views

What Is SDLC?: Requirement Gathering and Analysis

The document discusses Software Development Lifecycle (SDLC), which is a systematic process for building software that ensures quality. It consists of phases like requirements gathering, design, coding, testing, and deployment. The waterfall model is the traditional sequential SDLC model, while agile is an iterative incremental model that focuses on flexibility over requirements. Both approaches have advantages like structure and adaptability, as well as disadvantages like rigidity and lack of documentation.

Uploaded by

Sakshi Shriwas
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

What is SDLC?

SOFTWARE DEVELOPMENT LIFECYCLE (SDLC) is a


systematic process for building software that ensures the
quality and correctness of the software built. SDLC process
aims to produce high-quality software that meets customer
expectations. The system development should be complete in
the pre-defined time frame and cost. 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.
SDLC stands for Software Development Lifecycle.

 Phase 1: Requirement collection


 Phase 2: Analysis
 Phase 3: Design
 Phase 4: Coding
 Phase 5: Testing
 Phase 6: Installation/Deployment
 Phase 7: Maintenance

Requirement Gathering and Analysis


During this phase, all the relevant information is collected from
the customer to develop a product as per their expectation. Any
ambiguities must be resolved in this phase only.
Business analyst and Project Manager set up a meeting with
the customer to gather all the information like what the
customer wants to build, who will be the end-user, what is the
purpose of the product. Before building a product a core
understanding or knowledge of the product is very important.
Design
In this phase, the requirement gathered in the SRS document is
used as an input and software architecture that is used for
implementing system development is derived.

Implementation or Coding
Implementation/Coding starts once the developer gets the
Design document. The Software design is translated into
source code. All the components of the software are
implemented in this phase.

Testing
Testing starts once the coding is complete and the modules are
released for testing. In this phase, the developed software is
tested thoroughly and any defects found are assigned to
developers to get them fixed.

Deployment
Once the product is tested, it is deployed in the production
environment or first UAT (User Acceptance testing) is done
depending on the customer expectation.
In the case of UAT, a replica of the production environment is
created and the customer along with the developers does the
testing. If the customer finds the application as expected, then
sign off is provided by the customer to go live.

Maintenance
After the deployment of a product on the production environment,
maintenance of the product i.e. if any issue comes up and needs to
be fixed or any enhancement is to be done is taken care by the
developers.

Software Development Life Cycle Models

1. Waterfall Model
2. V-Shaped Model
3. Iterative Model
4. Spiral Model
5. Prototype Model
6. Big Bang Model
7. Agile Model

Waterfall Model
Waterfall model is the very first model that is used in SDLC. It is
also known as the linear sequential model.
In this model, the outcome of one phase is the input for the next
phase. Development of the next phase starts only when the
previous phase is complete.

 First, Requirement gathering and analysis is done. Once the


requirement is freeze then only the System Design can start.
Herein, the SRS document created is the output for the
Requirement phase and it acts as an input for the System
Design.
 In System Design Software architecture and Design,
documents which act as an input for the next phase are
created i.e. Implementation and coding.
 In the Implementation phase, coding is done and the software
developed is the input for the next phase i.e. testing.
 In the testing phase, the developed code is tested thoroughly
to detect the defects in the software. Defects are logged into
the defect tracking tool and are retested once fixed. Bug
logging, Retest, Regression testing goes on until the time the
software is in go-live state.
 In the Deployment phase, the developed code is moved into
production after the sign off is given by the customer.
 Any issues in the production environment are resolved by the
developers which come under maintenance.

Advantages of the Waterfall Model:


 Waterfall model is the simple model which can be easily
understood and is the one in which all the phases are done
step by step.
 Deliverables of each phase are well defined, and this leads to
no complexity and makes the project easily manageable.
Disadvantages of Waterfall model:
 Waterfall model is time-consuming & cannot be used in the
short duration projects as in this model a new phase cannot
be started until the ongoing phase is completed.
 Waterfall model cannot be used for the projects which have
uncertain requirement or wherein the requirement keeps on
changing as this model expects the requirement to be clear in
the requirement gathering and analysis phase itself and any
change in the later stages would lead to cost higher as the
changes would be required in all the phases.
Agile Model
Agile Model is a combination of the Iterative and incremental model.
This model focuses more on flexibility while developing a product
rather than on the requirement.

In Agile, a product is broken into small incremental builds. It is not


developed as a complete product in one go. Each build increments
in terms of features. The next build is built on previous functionality.

In agile iterations are termed as sprints. Each sprint lasts for2-4


weeks. At the end of each sprint, the product owner verifies the
product and after his approval, it is delivered to the customer.

Customer feedback is taken for improvement and his suggestions


and enhancement are worked on in the next sprint. Testing is done
in each sprint to minimize the risk of any failures.

Advantages of Agile Model:


 It allows more flexibility to adapt to the changes.
 The new feature can be added easily.
 Customer satisfaction as the feedback and suggestions are
taken at every stage.
Disadvantages:
 Lack of documentation.
 Agile needs experienced and highly skilled resources.
 If a customer is not clear about how exactly they want the
product to be, then the project would fail.

You might also like