Scribd
Upload
1 views3 pages

SDLC

Uploaded by

Jay Vachhani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1 views3 pages

SDLC

Uploaded by

Jay Vachhani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Software Development Life Cycle

The software development life cycle (SDLC) is a framework defining tasks performed at
each step in the software development process. SDLC is a structure followed by a
development team within the software organization. It consists of a detailed plan
describing how to develop, maintain and replace specific software. The life cycle defines
a methodology for improving the quality of software and the overall development
process. The software development life cycle is also known as the software development
process.
1. Identify the Current Problems
“What are the current problems n requirements?” Requirement gathering is the most
important and fundamental stage in SDLC. It is performed by the senior members of the
team with inputs from the customer, the sales department, market surveys and domain
experts in the industry. This information is then used to plan the basic project approach
and to conduct product feasibility study in the economical, operational and technical
areas.

Planning for the quality assurance requirements and identification of the risks associated
with the project is also done in the planning stage. The outcome of the technical feasibility
study is to define the various technical approaches that can be followed to implement the
project successfully with minimum risks.

2. Analysis
“What do we want?” In this stage of the SDLC, the team determines the cost and resources
required for implementing the analyzed requirements. It also details the risks involved
and provides sub-plans for softening those risks.

In other words, the team should determine the feasibility of the project and how they can
implement the project successfully with the lowest risk in mind.

3. Design
“How will we get what we want?” This phase of the SDLC starts by turning the software
specifications into a design plan called the Design Specification. All stakeholders then
review this plan and offer feedback and suggestions. It’s crucial to have a plan for
collecting and incorporating stakeholder input into this document. Failure at this stage
will almost certainly result in cost overruns at best and the total collapse of the project at
worst.

4. Coding
“Let’s create what we want.”

At this stage, the actual development starts. It’s important that every developer sticks to
the agreed blueprint. Also, make sure you have proper guidelines in place about the code
style and practices.
For example, define a nomenclature for files or define a variable naming style such
as camelCase. This will help your team to produce organized and consistent code that is
easier to understand but also to test during the next phase.

5. Code Test
“Did we get what we want?” In this stage, we test for defects and deficiencies. We fix those
issues until the product meets the original specifications.

In short, we want to verify if the code meets the defined requirements.

6. Software Deployment
“Let’s start using what we got.”

At this stage, the goal is to deploy the software to the production environment so users
can start using the product. However, many organizations choose to move the product
through different deployment environments such as a testing or staging environment.

This allows any stakeholders to safely play with the product before releasing it to the
market. Besides, this allows any final mistakes to be caught before releasing the product.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy