Software Development

Life Cycle (SDLC)

The Software Development Life Cycle (SDLC) is a systematic approach to
software development that ensures quality, efficiency, and a structured
process for building and deploying software systems.

by • Aryan Kumar Singh

• Mohit Jindal
• Mansi Pathak
• Pankaj Madhwal
• Akshat Gupta
Introduction to SDLC

1 Structured 2 Key Goals

Approach The primary goals are to
SDLC provides a well-
ensure high-quality
defined framework for
software, meet user
managing software
requirements, and achieve
development processes.
efficient development and
deployment.

3 Broad Applicability
The principles of SDLC are applicable across various software

projects, regardless of their size or complexity.

Phases of SDLC

Planning 1
Defining the project scope, goals, resources, and timelines.

2 Requirements
Analysis
Gathering and documenting detailed user requirements and specifications.
Design 3
Creating the architectural design, system design, and user interface design.

4 Implementation
Developing the actual software code according to the design specifications.

Testing 5
Rigorously testing the software for functionality, performance, and reliability.

6 Deployment
Releasing the software to production environments for users to access.

Maintenance 7
Ongoing support, bug fixes, enhancements, and updates to the software.
 Overview of SDLC Models
Understanding Software Development Life Cycle Models

1. Definition of SDLC
models 2. Purpose of SDLC models 3. Types of SDLC models

SDLC models are structured There are several types of

frameworks that define the They guide software SDLC models, including
stages and processes development by providing a Waterfall, V-Shaped,
involved in software clear roadmap for planning, Prototyping, Incremental,
development. designing, building, testing, Spiral, and Agile.
and deploying software
 2. Key Project
3. Project Plan
1. Life Cycle Parameters
Definition
Models Important
Life Cycle Models and A project plan
Project Parameters Life cycle models project-specific
is defined by
provide a fixed parameters
Understanding combining the
generic framework include size
Frameworks and Key lifecycle model
that can be adapted (measured in
Project Elements with the project
to specific projects. person-years),
parameters.
budget, and
duration.
 Improving Software Development through Life Cycle
Changes

1 2 3
Increased project visibility
Improved development speed Enhanced product quality
A new lifecycle approach can improve the
Changing the lifecycle model can lead to Lifecycle changes can contribute to a
visibility of project progress and status.
faster development times. higher quality of the final product.

4 5 6
Lowered risk exposure Better customer relations
Reduced administrative overhead
Implementing changes in the lifecycle Lifecycle changes can foster improved
Adjusting the lifecycle model can minimize
can help reduce the risks associated relationships with customers through better
administrative tasks and streamline
with software development. communication and satisfaction.
processes.
 The Waterfall Model: An Overview

Description of the Waterfall Model as a Classic Software Lifecycle Model

The Waterfall
Introduced by
model is
Royce in 1970, It is widely
characterized by understood and
the Waterfall
Historical Sequential its sequential Widely
model has a commonly used
Context Approach approach, where Understood
significant in the software
each phase must
historical impact development
be completed
on software industry.
before the next
development.
begins.
Waterfall Model

Requirements

Clearly define the project scope, features, and functionalities.

Design

Develop a detailed system architecture and design specifications.

Implementation

Write the actual software code based on the approved design.

Testing

Thoroughly test the software for bugs, errors, and performance issues.

Deployment

Release the software to production environments for user use.

 Strengths Weakness

Waterfall model has drawbacks, including its

Among the advantages of the waterfall model are inflexibility and lack of revision opportunities.
the following: Some specific concerns include the following:
• Provides a way for large or changing teams to • Design flaws, when discovered, often mean
work together toward a common goal defined in starting over from scratch
the requirements phase • It doesn’t incorporate mid-process feedback from
• Ensures a disciplined and structured organization users or clients and makes changes based on
• Provides a simple method to understand, follow, results
and arrange tasks • There’s no consideration for error correction
• Facilitates management control and • The model doesn’t accommodate changes, scope
departmentalization based on deadlines adjustments, and updates well
• Establishes good coding habits by defining first, • Work on different phases doesn’t overlap, which
then implementing design reduces the efficiency
• Provides easy access to early system design and • Projects don’t produce a working product until
specification changes later stages
• Defines milestones and deadlines clearly • Not an ideal model to use for complex and high-
risk projects
 Steps in Structured Evolutionary Prototyping
A Guide to Prototyping Model Development

1. Develop 2. Create a high- 3. Build a prototype 4. Demonstrate and

preliminary project level paper model with basic evaluate prototype
plan attributes continuously

• Initiate the • Design a • Construct an • Regularly

prototyping conceptual initial version of showcase the
process by framework that the product that prototype to
outlining the serves as a visual includes essential stakeholders and
project's representation of features for gather feedback
objectives and the project. testing. for ongoing
scope. improvements.
 Strengths Weakness
1. Early visualization of system requirements

Structured Evolutionary Prototyping allows for the early visualization of

1. Risk of abandoning structured development
system requirements, leading to better understanding and clarity.
There is a danger that developers may opt for quick fixes instead
2. Enhanced developer-user collaboration
of following a structured development process.
This model promotes enhanced collaboration between developers and
2. Reputation for poor quality methods
users, facilitating better communication and feedback.
Structured evolutionary prototyping can develop a reputation for
3. Accurate end products
utilizing methods that do not ensure high quality.
The use of this prototyping model results in more accurate end products
3. Potential overlook of maintainability
that meet user specifications.
There is a risk that maintainability aspects of the software may be
4. Flexibility in design and development
neglected during development.
Structured Evolutionary Prototyping offers flexibility, allowing for
4. Risk of endless process (scope creep)
adjustments and changes during the design and development phases.
The prototyping approach may lead to scope creep, resulting in an
5. Visible progress tracking
unending development process.
It provides visible progress tracking, which helps stakeholders
understand the development status and timelines.