Kamalesh AR

Posted on Jun 30

Software Development Life Cycle

Today, I attended a training session on Software Development Life Cycle (SDLC). In this I learned about the SDLC, Phases of SDLC how it works in the projects and Companies with an example. Then experienced persons who are in the session they also shares their knowledge about this SDLC. That was a new thing for myself to gathering these type knowledge and information from them. In this session happens like interactive, differents opinions about the SDLC and informative things and discuss about the BRS(Business Requirements Specification),FRS(Functional Requirements Specification),SRS(Software Requirements Specification).This fully concentrate from requirements from client to develop final project based on their requirements complete the projects.

SDLC:

The software development lifecycle (SDLC) is the cost-effective and time-efficient process that development teams use to design and build high-quality software. The goal of SDLC is to minimize project risks through forward planning so that software meets customer expectations during production and beyond. This methodology outlines a series of steps that divide the software development process into tasks you can assign, complete, and measure.

Importance of SDLC:

Software development can be challenging to manage due to changing requirements, technology upgrades, and cross-functional collaboration. The software development lifecycle (SDLC) methodology provides a systematic management framework with specific deliverables at every stage of the software development process. As a result, all stakeholders agree on software development goals and requirements upfront and also have a plan to achieve those goals.

Here are some benefits of SDLC:

Increased visibility of the development process for all stakeholders involved
Efficient estimation, planning, and scheduling
Improved risk management and cost estimation
Systematic software delivery and better customer satisfaction

SDLC works:

The software development lifecycle (SDLC) outlines several tasks required to build a software application. The development process goes through several stages as developers add new features and fix bugs in the software.

The details of the SDLC process vary for different teams. However, we outline some common SDLC phases below.

Phases of SDLC

Planning
Design
Development
Testing
Deployment
Maintenance

Planning

The planning phase typically includes tasks like cost-benefit analysis, scheduling, resource estimation, and allocation. The development team collects requirements from several stakeholders such as customers, internal and external experts, and managers to create a software requirement specification document.

The document sets expectations and defines common goals that aid in project planning. The team estimates costs, creates a schedule, and has a detailed plan to achieve their goals.

Design

In the design phase, software engineers analyze requirements and identify the best solutions to create the software. For example, they may consider integrating pre-existing modules, make technology choices, and identify development tools. They will look at how to best integrate the new software into any existing IT infrastructure the organization may have.

Development

In the implementation phase, the development team codes the product. They analyze the requirements to identify smaller coding tasks they can do daily to achieve the final result.

Test

The development team combines automation and manual testing to check the software for bugs. Quality analysis includes testing the software for errors and checking if it meets customer requirements. Because many teams immediately test the code they write, the testing phase often runs parallel to the development phase.

Deploy

When teams develop software, they code and test on a different copy of the software than the one that the users have access to. The software that customers use is called production, while other copies are said to be in the build environment, or testing environment.

Having separate build and production environments ensures that customers can continue to use the software even while it is being changed or upgraded. The deployment phase includes several tasks to move the latest build copy to the production environment, such as packaging, environment configuration, and installation.

Maintain

In the maintenance phase, among other tasks, the team fixes bugs, resolves customer issues, and manages software changes. In addition, the team monitors overall system performance, security, and user experience to identify new ways to improve the existing software.

Real-time example:

"For example, if a client wants to build a food delivery application, the team first gathers all the requirements, such as user registration, restaurant search, cart, payment, and order tracking. Next, the project manager plans the budget, timeline, and team. Then, designers create the UI and database design. Developers write the frontend and backend code based on the design. After development, testers verify all features and report any bugs, which developers fix. Once the application passes testing, it is deployed by devops team to the production server so users can access it. Finally, during the maintenance phase, developers fix issues, improve performance, and add new features based on user feedback."

SDLC models: (TBD)

Waterfall

The waterfall model arranges all the phases sequentially so that each new phase depends on the outcome of the previous phase. Conceptually, the design flows from one phase down to the next, like that of a waterfall.

Pros and cons:

The waterfall model provides discipline to project management and gives a tangible output at the end of each phase. However, there is little room for change once a phase is considered complete, as changes can affect the software's delivery time, cost, and quality. Therefore, the model is most suitable for small software development projects, where tasks are easy to arrange and manage and requirements can be pre-defined accurately.

Iterative:

The iterative process suggests that teams begin software development with a small subset of requirements. Then, they iteratively enhance versions over time until the complete software is ready for production. The team produces a new software version at the end of each iteration.

Pros and cons

It’s easy to identify and manage risks, as requirements can change between iterations. However, repeated cycles could lead to scope change and underestimation of resources.

Spiral:

The spiral model combines the iterative model's small repeated cycles with the waterfall model's linear sequential flow to prioritize risk analysis. You can use the spiral model to ensure software's gradual release and improvement by building prototypes at each phase.

Pros and cons

The spiral model is suitable for large and complex projects that require frequent changes. However, it can be expensive for smaller projects with a limited scope.

Agile:

The agile model arranges the SDLC phases into several development cycles. The team iterates through the phases rapidly, delivering only small, incremental software changes in each cycle. They continuously evaluate requirements, plans, and results so that they can respond quickly to change. The agile model is both iterative and incremental, making it more efficient than other process models.

Pros and cons

Rapid development cycles help teams identify and address issues in complex projects early on and before they become significant problems. They can also engage customers and stakeholders to obtain feedback throughout the project lifecycle. However, overreliance on customer feedback could lead to excessive scope changes or end the project midway.

RAD Model:

The RAD (Rapid Application Development) Model is a software development methodology that focuses on fast development and frequent releases of working software. It emphasizes iterative development, quick user feedback, and flexibility, allowing changes to be easily incorporated during the development process. Unlike traditional models such as the Waterfall Model, RAD adapts quickly to changing requirements and user needs.

Pros and cons

The RAD model enables faster development, early customer feedback, better quality, easy progress tracking, and flexibility to accommodate changing requirements. It requires skilled developers, reusable components, continuous customer involvement, and strong team coordination. It is also not suitable for every project and can be expensive for small applications.

DevOps and the SDLC:

DevOps is a software development methodology that combines and automates the work of both software development and IT operations teams. The DevOps lifecycle has its own steps, which are similar to the steps of the SDLC. But DevOps reconfigures the steps of the SDLC to create a continuous cycle for software development and improvement.

The core principles of a DevOps approach are collaboration, automation and continuous integration and continuous delivery (CI/CD). Because DevOps addresses the full software development process, it might be considered a software development lifecycle in its own right.

But DevOps is also larger than this, encompassing a cultural and organizational shift toward shared responsibility and collaboration. Crucially, DevOps is not a single model, but a combination of practices, tools and cultural philosophies.

DevOps addresses the rigidity of the SDLC by making each phase of the software development process continuous throughout the project. Instead of being limited to discrete steps, planning, coding, testing, deploying, maintaining and monitoring all continue throughout a product’s lifecycle. The result is a continuous delivery pipeline in which software is improved through frequent updates.

DevSecOps and the SDLC:

DevSecOps, sometimes called “secure DevOps,” integrates automated security testing and security practices into the DevOps model. Where traditional software development treats security testing as its own phase, DevSecOps incorporates security considerations into every phase of the SDLC.

By threading security tests such as code reviews and penetration testing throughout the development lifecycle, teams can avoid some delays arising from factors such as vulnerabilities that are identified late in the process. They can address risk management issues earlier, create more secure programs, accelerate vulnerability remediation and deliver more cost-effective software.

Bug Bounty:

A bug bounty program is a security program where companies reward ethical hackers for finding and reporting security vulnerabilities before attackers can exploit them. This helps organizations improve application security and protect user data.

Bug bounty programs reward ethical hackers who identify and responsibly disclose vulnerabilities to the application’s developer, before attackers can exploit them. By engaging a diverse, global community of experts, organizations continuously monitor and test their attack surface, uncover hard-to-find vulnerabilities, reduce risk, and build customer trust. Bug bounty programs allow companies to leverage the hacker community to improve their systems’ security posture over time.

Conclusion:

The above defined topics are i learned from my session and now i study above the SDLC and how its works. This session is helped me understand that successful software development is not just about writing code—it requires proper planning, collaboration, documentation, testing, and continuous improvement.Overall these are my today learning about the SDLC to experience the learning is strengthened my knowledge of software development processes.

The images above are my handwritten notes taken during the live SDLC training session. I referred to these notes while writing this blog to summarize what I learned and to document my understanding of the concepts discussed during the session.