SDLC

SOFTWARE DEVELOPMENT LIFE CYCLE

Content

Introduction
SDLC Overview
SDLC Phases
SDLC Flow
SDLC Model
Waterfall Model
Agile Model
Conclusion
Introduction

Software development is defined as the process of designing, creating, testing, and

maintaining computer programs and applications.

SDLC is the acronym of Software Development Life Cycle.

It is also called as Software Development Process.

SDLC is a framework defining tasks performed at each step in the software development
process.

ISO/IEC 12207 is an international standard for software life-cycle processes. It aims to be

the standard that defines all the tasks required for developing and maintaining software.
What is the SDLC?

The software development life cycle (SDLC) is the process of planning, writing, modifying, and maintaining software.

Software development life cycle (SDLC) is the term used in the software industry to describe the process for creating a
new software product.

The goal of the SDLC life cycle model is to deliver high quality, maintainable software that meets
the user’s requirements.

Software developers use this as a guide to ensure software is produced with the lowest cost and highest possible quality
in the shortest amount of time.

Developers use the methodology as they design and write modern software for computers, cloud deployment, mobile
phones, video games, and more. Adhering to the SDLC methodology helps to optimize the final outcome.
Why is the SDLC important?

The SDLC is important because it helps ensure that the right people are involved in the right activities at the right
times.

Using a structured approach to developing software helps ensure that your project will be successful.

Some of the SDLC's benefits are:

•Understanding your requirements and the goal of the software

•Identify risks at an early stage
•Plan how you will deliver your solution in stages, such as building prototypes or writing
functional specifications
•Measure your progress relative to your goals and ensure everything is on track
SDLC Phases
7 stages of the software development life cycle

Each stage in the SDLC has its own set of activities that need to be performed by the team members involved
in the development project.

While the process timeline will vary from project to project, the SDLC generally follows the seven stages
outlined below.

Stage 1: Plan and brainstorm.

Stage 2: Analyze requirements.
Stage 3: Design the mockups.
Stage 4: Develop the code.
Stage 5: Test the product.
Stage 6: Implement and launch the product.
Stage 7: Set up maintenance and operations.
Stage 1: Plan and brainstorm.

The first step in the software development life cycle is planning.

It's when you gather the team to brainstorm, set goals, and identify risks.

At this stage, the team will work together to devise a set of business goals, requirements,
specifications, and any high-level risks that might hinder the project's success.

1.Set Goals: Decide what we want to achieve.

2.Collect Requirements: Find out what users need.
3.Brainstorm Ideas: Think of different ways to meet those needs.
4.Check Feasibility: See if our ideas are doable and affordable.
5.Make a Plan: Outline steps, timeline, and resources.
6.Identify Risks: Spot any problems that might come up and plan for them.

Documents Required:
•Project Charter: Overview of the project's goals and objectives.
•Stakeholder List: Who is involved and their roles.
•Requirements Document: Initial list of what the software needs to do.
•Feasibility Study: Analysis of the project's viability.
•Project Plan: Detailed plan of actions, timeline, and resources.
•Risk Assessment: Potential risks and mitigation strategies
Stage 2: Analyze requirements.

Once you've come up with some ideas, it's time to organize them into a cohesive plan and design.

This requires a lot of research and planning to ensure that your final product meets your expectations (and
those of your customers).

The big step is creating a detailed project plan document and work breakdown structure that outlines the
requirements.

1.Gather Detailed Requirements: Collect specific details about what the software must do.
2.Understand User Needs: Ensure that the requirements align with what users need.
3.Document Requirements: Write down all the requirements clearly and precisely.
4.Create Use Cases: Develop scenarios that show how users will interact with the software.
5.Review Requirements: Check the requirements with stakeholders to make sure nothing is missed.
6.Approve Requirements: Get formal agreement from stakeholders on the final list of requirements.

Documents Required:
•Requirements Specification Document: Details all user and system requirements.
•Use Case Document: Describes how users will interact with the system.
Stage 3: Design the mockups.

Once have got design plans in front of you, it's time for wireframing and mockups.

This step builds upon the planning stage, building out the tasks you need to do in the work breakdown
schedule.

There are plenty of tools available, such as Adobe XD or InVision or Figma, that make this process much
easier than ever before.

1.Create Visual Designs: Develop visual representations of the software.

2.Sketch Interfaces: Draw simple sketches of the user interface.
3.Build Wireframes: Create basic layouts for each screen.
4.Design Prototypes: Make interactive models to show how the software will work.
5.Review with Stakeholders: Get feedback from users and stakeholders.
6.Revise Designs: Update designs based on feedback.

Documents Required:
•Mockup Designs: Visual representations of the software.
•Wireframes: Basic screen layouts.
•Prototypes: Interactive models of the software.
Stage 4: Develop the code.

The development phase is where coding begins to take place.

It is one of the most time-consuming phases in the SDLC.

This phase often requires extensive programming skills and knowledge of databases.

The team will build functionality for the product or service, which includes creating a user interface and building the
database so users can store information in the system.

1.Write Code: Develop the software based on the design.

2.Follow Standards: Ensure coding standards and best practices are followed.
3.Perform Unit Testing: Test individual components for functionality.
4.Integrate Code: Combine different parts of the code into a whole.
5.Debug: Identify and fix any issues in the code.

Documents Required:
•Source Code: The written code for the software.
•Code Documentation: Explanation of how the code works and how to use it.
•Unit Test Cases: Tests to verify each part of the code works correctly.
•Integration Plan: Plan for combining different code components.
•Bug Report: List of identified issues and their status.
Stage 5: Test the product.

Before releasing the mockups into final production, need to test it to ensure it is free of bugs and errors.

Any issues need to be fixed before moving forward with deployment.

Need to manage how the system will integrate into existing systems, software, and processes.

1.Prepare Test Cases: Create scenarios to test the software.

2.Conduct Testing: Execute the test cases to check functionality.
3.Identify Bugs: Find and document any issues or errors.
4.Fix Issues: Developers resolve the identified bugs.
5.Re-test: Test again to ensure issues are fixed.
6.User Acceptance Testing (UAT): Get final approval from users.

Documents Required:
•Test Plan: Strategy for testing the software.
•Test Cases: Specific scenarios and conditions for testing.
•Bug Reports: Detailed descriptions of identified issues.
•Test Report: Summary of testing outcomes and results.
•UAT Document: Confirmation from users that the software meets their needs.
Stage 6: Implement and launch the product.

Once have completed all testing phases, it's time to deploy your new application for customers to use.

After deployment, the launch may involve marketing your new product or service so people know about its existence.

If the software is in-house, it may mean implementing the change management process to ensure user training and
acceptance.

1.Deploy Software: Install the software on the users' systems.

2.Train Users: Provide training on how to use the software.
3.Monitor Launch: Ensure the software performs as expected.
4.Handle Issues: Address any problems that arise during launch.
5.Evaluate Performance: Assess how well the software meets goals.
6.Feedback Collection: Gather user feedback for improvements.

Documents Required:
•Deployment Plan: Strategy for installing and configuring the software.
•Training Materials: Guides or manuals for users.
•Launch Checklist: List of tasks to ensure a smooth launch.
•Issue Log: Record of any problems encountered and their resolutions.
•Performance Evaluation: Assessment of software performance post-launch.
•User Feedback Forms: Surveys or forms to collect user opinions.
Stage 7: Set up maintenance and operations.

The final stage of the software development life cycle is maintenance and operations.
This is one of the most critical stages because it's when your hard work gets put to the test.
Maintenance involves updating an existing software product to fix bugs and ensure reliability.
It can also include adding new features or functionality to a current product.
Operations refer to the day-to-day running of a software product or service, such as performing backups and other
administrative tasks.

1.Establish Maintenance Procedures: Define how to keep the software running smoothly.
2.Monitor Performance: Keep track of how well the software performs.
3.Handle Updates and Upgrades: Implement new features and fix issues.
4.Provide Support: Assist users with any questions or problems.
5.Ensure Security: Protect the software from threats and vulnerabilities.
6.Review and Improve: Continuously assess and enhance software capabilities.

Documents Required:
•Maintenance Plan: Outline procedures for ongoing maintenance.
•Monitoring Reports: Regular updates on software performance.
•Change Management Plan: Strategy for handling updates and upgrades.
•Support Documentation: Guides or resources for assisting users.
•Security Protocols: Policies and procedures to safeguard the software.
•Improvement Recommendations: Suggestions for enhancing software features.
Disadvantages of Using SDLC Models

1.Rigidity: Some models, like Waterfall, can be inflexible once a phase is complete.
2.Long Development Time: Sequential models may lead to lengthy development cycles.
3.Limited User Involvement: Structured processes may reduce continuous user input.
4.Costly Changes: Modifying requirements late can be expensive and time-consuming.
5.Testing Challenges: Testing may discover critical issues late in development.
6.Complexity: Models may require extensive documentation and planning.
7.Skill Requirements: Implementing models may demand specific expertise.
8.Progress Measurement: Tracking progress accurately can be challenging.
9.Adaptability: Some models may not adapt well to changing requirements.
10.Agility Concerns: Traditional models may not align with Agile principles.
Advantages of using SDLC Models

1.Structured Approach: Provides a clear and organized process for development.

2.Risk Management: Identifies and addresses risks early in the project.
3.Quality Assurance: Ensures software meets high standards and user needs.
4.Efficient Resource Management: Helps allocate resources effectively.
5.Clear Communication: Facilitates understanding among team members and stakeholders.
6.Predictable Delivery: Improves project planning and timelines.
7.Flexibility: Adapts to different project requirements and changes.
8.Documentation: Ensures decisions and requirements are well-documented.
SDLC Models

Software Development life cycle (SDLC) is a spiritual model used in project management that
defines the stages include in an information system development project, from an initial
feasibility study to the maintenance of the completed application.

There are different software development life cycle models specify and design, which are
followed during the software development phase.

These models are also called "Software Development Process Models."

Each process model follows a series of phase unique to its type to ensure success in the step
of software development.
SDLC Models
Waterfall Model

The Waterfall Model was the first Process Model to be introduced.

It is also referred to as a linear-sequential life cycle model.

It is very simple to understand and use.

In a waterfall model, each phase must be completed before the next phase can begin and there
is no overlapping in the phases.

The Waterfall model is the earliest SDLC approach that was used for software development.

The waterfall Model illustrates the software development process in a linear sequential flow.

This means that any phase in the development process begins only if the previous phase is
complete. In this waterfall model, the phases do not overlap.
The sequential phases in Waterfall model are,

•Requirement Gathering and analysis − All possible requirements of the system to be

developed are captured in this phase and documented in a requirement specification
document.

•System Design − The requirement specifications from first phase are studied in this phase
and the system design is prepared. This system design helps in specifying hardware and
system requirements and helps in defining the overall system architecture.

•Implementation − With inputs from the system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is developed and
tested for its functionality, which is referred to as Unit Testing.

•Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is tested
for any faults and failures.

•Deployment of system − Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.

•Maintenance − There are some issues which come up in the client environment. To fix those
issues, patches are released. Also to enhance the product some better versions are released.
Maintenance is done to deliver these changes in the customer environment.
Waterfall Model - Application

Every software developed is different and requires a suitable SDLC approach to be followed based
on the internal and external factors.

Some situations where the use of Waterfall model is most appropriate are

•Requirements are very well documented, clear and fixed.

•Product definition is stable.
•Technology is understood and is not dynamic.
•There are no ambiguous requirements.
•Ample resources with required expertise are available to support the product.
•The project is short.
Waterfall Model - Advantages

•Simple and easy to understand and use

•Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a review
process.
•Phases are processed and completed one at a time.
•Works well for smaller projects where requirements are very well understood.
•Clearly defined stages.
•Well understood milestones.
•Easy to arrange tasks.
•Process and results are well documented.
Waterfall Model - Disadvantages

•No working software is produced until late during the life cycle.
•High amounts of risk and uncertainty.
•Not a good model for complex and object-oriented projects.
•Poor model for long and ongoing projects.
•Not suitable for the projects where requirements are at a moderate to high risk of changing. So,
risk and uncertainty is high with this process model.
•It is difficult to measure progress within stages.
•Cannot accommodate changing requirements.
•Adjusting scope during the life cycle can end a project.
•Integration is done as a "big-bang. at the very end, which doesn't allow identifying any
technological or business bottleneck or challenges early.
Agile Model