Software Development Life Cycle: Difference between revisions

Latest revision as of 09:28, 6 July 2025

Software Development Life Cycle is a structured process that outlines the stages involved in the development of software applications. It encompasses a set of practices and methodologies, aiming to produce high-quality software systems that meet or exceed customer expectations. The stages typically include planning, analysis, design, implementation, testing, deployment, and maintenance. Each phase plays a crucial role in ensuring that the software development process is efficient, systematic, and aligned with business objectives.

Background or History

The origins of the Software Development Life Cycle (SDLC) can be traced back to the early days of computing. Initially, software development was primarily an ad-hoc activity, with developers often creating applications without any formal methodologies. As the complexity of software systems grew, the need for a more structured approach became apparent.

In the 1970s, various development methodologies began to emerge, such as the Waterfall model and the iterative and incremental models. The Waterfall model, introduced by Dr. Winston W. Royce in 1970, describes a linear and sequential approach to software development, where each phase must be completed before the next phase begins. This model emphasized the importance of documentation and formal reviews at each stage of development.

Over the years, alternative methodologies such as Agile and DevOps have gained popularity, addressing the limitations of traditional models like Waterfall. The Agile methodology, in particular, emphasizes flexibility and iterative progress, allowing teams to respond quickly to changes in requirements. Despite the evolution of various methodologies, the fundamental phases of the SDLC remain relevant and crucial for successful software development.

Stages of the Software Development Life Cycle

The Software Development Life Cycle is divided into several key stages, each with distinct objectives and deliverables. These stages are interrelated and contribute to the overall success of software projects.

Planning

The planning phase is the starting point of any software development project. During this stage, project stakeholders define the scope of the project, outline goals and objectives, and assess the resources required for completion. Activities in this phase may include feasibility studies, risk assessments, and stakeholder interviews.

In addition, a project management plan is created, detailing timelines, budgets, and roles and responsibilities. This phase sets the stage for the subsequent phases, ensuring that all stakeholders have a shared understanding of the project’s purpose and objectives.

Analysis

The analysis phase involves gathering detailed requirements from stakeholders. Analysts engage in discussions with users to identify their needs, expectations, and constraints. This may include documenting functional requirements, non-functional requirements, and use cases, which serve as a foundation for the design phase.

During this stage, techniques such as interviews, surveys, and prototyping may be employed to elicit requirements effectively. The output of the analysis phase is typically a requirements specification document, which articulates what the software must accomplish.

Design

Once the requirements are well understood, the design phase focuses on developing the architecture of the software system. This phase is pivotal in translating requirements into a workable system architecture.

System architects and designers create technical specifications and design documents that outline the software’s structure, components, interfaces, and data flows. During this phase, design methodologies such as Object-Oriented Design (OOD) and Model-Driven Architecture (MDA) may be utilized. The output includes detailed design diagrams and data models, which serve as blueprints for the development team.

Implementation

The implementation phase, also known as the coding phase, involves the actual building of the software. Developers write the source code according to the design specifications. Programming languages and development tools are selected based on the project requirements.

Version control systems are often utilized during this phase to track code changes and facilitate collaboration among team members. It is crucial that coding standards and best practices are adhered to in this phase, ensuring the codebase remains clean, maintainable, and scalable.

Testing

Testing is a critical phase in the SDLC, aimed at ensuring the software meets the defined requirements and is free of defects. Various testing strategies, including unit testing, integration testing, system testing, and user acceptance testing (UAT), are employed to validate different aspects of the software.

Test cases are derived from the requirements specification to ensure comprehensive coverage. Automated testing tools may also be utilized to enhance efficiency and accuracy. The testing phase may reveal bugs or issues that require rework, necessitating close collaboration between developers and testers.

Deployment

Upon successful testing, the software moves into the deployment phase. This stage involves the installation and configuration of the software in a production environment. Deployment strategies may vary, from traditional installations to cloud-based releases, depending on the architecture of the application.

User training and support plans are often implemented during this phase to ensure that end-users can effectively utilize the new software. The deployment phase also includes post-deployment reviews and monitoring to ensure that the software performs as expected in a real-world setting.

Maintenance

The maintenance phase is the final stage of the Software Development Life Cycle and involves ongoing support and enhancement of the software after deployment. This phase is crucial for addressing issues that arise during operation, rolling out updates, and implementing new features based on user feedback.

Software maintenance can be categorized into corrective maintenance, adaptive maintenance, and perfective maintenance. Corrective maintenance focuses on fixing errors, adaptive maintenance addresses changes in the operational environment, and perfective maintenance involves enhancing system performance or adding new functionalities.

Methodologies within the Software Development Life Cycle

Various methodologies exist within the scope of the Software Development Life Cycle, each with its unique approach and focus.

Waterfall Model

The Waterfall model is one of the earliest formalized approaches to software development. It is characterized by a linear and sequential progression of stages, where the completion of one phase leads directly to the initiation of the next. One of the main advantages of the Waterfall model is the clarity it provides in project planning and documentation. However, its rigidity can be a limitation, as changes in requirements during later stages can cause significant disruption.

Agile Methodology

Agile methodology prioritizes flexibility and customer collaboration over strict adherence to process. Agile teams work in iterative cycles, known as sprints, which allow for frequent reassessment of project priorities. This methodology encourages continuous feedback from users, making it suitable for projects where requirements evolve rapidly. The Agile Manifesto emphasizes four key values: individuals and interactions, working software, customer collaboration, and responding to change.

DevOps

DevOps is a modern framework that seeks to integrate software development (Dev) and IT operations (Ops) to enhance the speed and quality of software delivery. By fostering a culture of collaboration, automation, and continuous improvement, DevOps aims to shorten the software development lifecycle. It incorporates practices such as Continuous Integration (CI) and Continuous Deployment (CD) to automate manual tasks, facilitating faster releases and better code quality.

Real-world Examples

The principles of the Software Development Life Cycle are applied in various real-world software projects across different industries.

Enterprise Resource Planning Systems

Organizations often implement Enterprise Resource Planning (ERP) systems to streamline their operations. The SDLC plays a crucial role in these projects, guiding the development of customized software that integrates various business processes. The planning stage involves understanding the specific needs of each department, while the analysis and design phases ensure alignment with organizational goals.

Mobile Application Development

Mobile app development projects consistently utilize the SDLC to navigate the complexities of building applications for diverse platforms. In the Agile context, mobile development teams iterate on user feedback, enhancing functionalities in subsequent releases. The testing phase becomes particularly important in this domain, as user experience and performance are vital for app success.

E-commerce Platforms

The development of e-commerce platforms requires a thorough understanding of user requirements and compliance with regulations. The SDLC helps ensure that these platforms are built with scalability and security in mind. Stakeholders utilize the analysis phase to identify essential features, while the testing phase verifies the platform's functionality and reliability before launch.

Criticism or Limitations

Despite its widespread use and adaptation, the Software Development Life Cycle is not without criticism.

Rigidity in Traditional Models

Traditional models, such as Waterfall, have been criticized for their rigid structure, which can lead to inefficiencies and delays if requirements change late in the process. This inflexibility can result in projects that fail to meet user needs or are delivered late, causing dissatisfaction among stakeholders.

Overhead in Documentation

The emphasis on documentation in traditional SDLC models can potentially lead to overhead, consuming valuable time and resources. Some argue that excessive documentation may detract from hands-on development and collaboration, which can stifle creativity and innovation.

Challenges in Agile Adoption

While Agile methodologies offer flexibility, their implementation can be challenging. Teams transitioning from traditional models to Agile may face cultural resistance and difficulties in adapting to new processes. Furthermore, Agile's reliance on customer collaboration can present challenges in managing stakeholders' expectations.

References

@@ Line 1: / Line 1: @@
-= Software Development Life Cycle =
+'''Software Development Life Cycle''' is a structured process that outlines the stages involved in the development of software applications. It encompasses a set of practices and methodologies, aiming to produce high-quality software systems that meet or exceed customer expectations. The stages typically include planning, analysis, design, implementation, testing, deployment, and maintenance. Each phase plays a crucial role in ensuring that the software development process is efficient, systematic, and aligned with business objectives.
-The '''Software Development Life Cycle''' (SDLC) is a systematic process for planning, creating, testing, and deploying software applications. SDLC provides a structured framework that guides developers through various stages of software development, ensuring that the final product meets the desired quality standards and fulfills user requirements. This article will explore the key phases of SDLC, its methodologies, advantages, limitations, real-world applications, and its evolutionary history.
+== Background or History ==
-== Introduction ==
+The origins of the Software Development Life Cycle (SDLC) can be traced back to the early days of computing. Initially, software development was primarily an ad-hoc activity, with developers often creating applications without any formal methodologies. As the complexity of software systems grew, the need for a more structured approach became apparent.
-The Software Development Life Cycle comprises several phases that facilitate the structured development of software products. It acts as a roadmap for both developers and stakeholders, detailing each step involved—from initial conception to maintenance after deployment. Understanding the SDLC is crucial for developers, project managers, and all stakeholders involved in software development. Effective application of SDLC can lead to increased productivity, improved quality, and reduced project risks.
+In the 1970s, various development methodologies began to emerge, such as the Waterfall model and the iterative and incremental models. The Waterfall model, introduced by Dr. Winston W. Royce in 1970, describes a linear and sequential approach to software development, where each phase must be completed before the next phase begins. This model emphasized the importance of documentation and formal reviews at each stage of development.
-== History ==
+Over the years, alternative methodologies such as Agile and DevOps have gained popularity, addressing the limitations of traditional models like Waterfall. The Agile methodology, in particular, emphasizes flexibility and iterative progress, allowing teams to respond quickly to changes in requirements. Despite the evolution of various methodologies, the fundamental phases of the SDLC remain relevant and crucial for successful software development.
-The concept of software development as a structured process dates back to the early 1960s as computer science emerged as a discipline. Early software development efforts were largely ad-hoc, with developers relying on their intuition and experience. As software systems grew in complexity, it became evident that a more systematic approach to software development was necessary.
+== Stages of the Software Development Life Cycle ==
-The 1970s saw the emergence of various models for software development, most notably the Waterfall model proposed by Dr. Winston W. Royce in 1970. The Waterfall model introduced sequential phases including requirements analysis, design, implementation, testing, deployment, and maintenance. However, the rigid nature of this model led to the development of more flexible paradigms in subsequent decades, such as Agile and Iterative models, reflecting the evolving needs of developers and businesses.
+The Software Development Life Cycle is divided into several key stages, each with distinct objectives and deliverables. These stages are interrelated and contribute to the overall success of software projects.
-In the 1990s, the introduction of software engineering principles and paradigms further solidified the importance of SDLC as a framework for successful software projects. Standards such as ISO/IEC/IEEE 12207 established a global consensus on software lifecycle processes, providing formal guidance on activities, roles, and responsibilities.
+=== Planning ===
-== Phases of the Software Development Life Cycle ==
+The planning phase is the starting point of any software development project. During this stage, project stakeholders define the scope of the project, outline goals and objectives, and assess the resources required for completion. Activities in this phase may include feasibility studies, risk assessments, and stakeholder interviews.
-The SDLC typically consists of the following key phases, each serving a specific purpose in the development process:
+In addition, a project management plan is created, detailing timelines, budgets, and roles and responsibilities. This phase sets the stage for the subsequent phases, ensuring that all stakeholders have a shared understanding of the project’s purpose and objectives.
-=== 1. Planning ===
+=== Analysis ===
-The planning phase is the foundation of the entire SDLC process. During this phase, stakeholders define the project scope, objectives, timelines, and budget. A feasibility study is often conducted to evaluate the project's viability, considering factors such as technical feasibility, economic feasibility, and legal constraints. Effective planning establishes a clear framework for the subsequent phases and aligns the project goals with the organization’s strategic objectives.
+The analysis phase involves gathering detailed requirements from stakeholders. Analysts engage in discussions with users to identify their needs, expectations, and constraints. This may include documenting functional requirements, non-functional requirements, and use cases, which serve as a foundation for the design phase.
-=== 2. Requirements Gathering and Analysis ===
+During this stage, techniques such as interviews, surveys, and prototyping may be employed to elicit requirements effectively. The output of the analysis phase is typically a requirements specification document, which articulates what the software must accomplish.
-In this critical phase, developers gather detailed requirements from stakeholders, including end-users, customers, and management. This involves conducting interviews, surveys, and workshops to understand user needs and expectations. The requirements are then documented in a clear and concise manner, often in the form of a Software Requirements Specification (SRS) document. This phase ensures that all functional and non-functional requirements are identified, helping to minimize misunderstandings later in the process.
+=== Design ===
-=== 3. Design ===
+Once the requirements are well understood, the design phase focuses on developing the architecture of the software system. This phase is pivotal in translating requirements into a workable system architecture.
-Once requirements are finalized, the design phase commences, where developers create a comprehensive blueprint of the software system. This phase typically involves two levels of design: system design and detailed design. The system design outlines the overall architecture, including module division, data flow, and interactions with external systems. The detailed design delves into specific components, defining algorithms, data structures, and interfaces. The design phase may produce several artifacts such as data models, user interfaces, and system architecture diagrams.
+System architects and designers create technical specifications and design documents that outline the software’s structure, components, interfaces, and data flows. During this phase, design methodologies such as Object-Oriented Design (OOD) and Model-Driven Architecture (MDA) may be utilized. The output includes detailed design diagrams and data models, which serve as blueprints for the development team.
-=== 4. Implementation (or Coding) ===
+=== Implementation ===
-The implementation phase involves the actual coding of the software application based on the design specifications. Developers write code in the chosen programming languages, following coding standards and best practices to ensure code quality. This phase may include various tasks such as unit testing, code reviews, and version control management to track changes in the codebase. The effectiveness of this phase significantly influences the overall quality and maintainability of the final product.
+The implementation phase, also known as the coding phase, involves the actual building of the software. Developers write the source code according to the design specifications. Programming languages and development tools are selected based on the project requirements.
-=== 5. Testing ===
+Version control systems are often utilized during this phase to track code changes and facilitate collaboration among team members. It is crucial that coding standards and best practices are adhered to in this phase, ensuring the codebase remains clean, maintainable, and scalable.
-Testing is a critical phase in the SDLC where the developed software is rigorously evaluated to identify defects or discrepancies against the specified requirements. Various levels of testing are conducted, including unit testing, integration testing, system testing, and user acceptance testing (UAT). Each testing type serves a unique purpose and helps ensure that the software functions as expected and meets quality standards. Inadequate testing can lead to significant issues post-deployment, underscoring the importance of this phase in the SDLC.
+=== Testing ===
-=== 6. Deployment ===
+Testing is a critical phase in the SDLC, aimed at ensuring the software meets the defined requirements and is free of defects. Various testing strategies, including unit testing, integration testing, system testing, and user acceptance testing (UAT), are employed to validate different aspects of the software.
-After successful testing, the software application is deployed in a production environment for end-users. This phase may involve various strategies such as direct installation, phased deployment, or pilot testing. Additionally, training and user documentation are often provided to ensure that users can effectively utilize the new system. The deployment phase marks the transition from development to operational use, and its success largely depends on thorough preparation and effective communication with stakeholders.
+Test cases are derived from the requirements specification to ensure comprehensive coverage. Automated testing tools may also be utilized to enhance efficiency and accuracy. The testing phase may reveal bugs or issues that require rework, necessitating close collaboration between developers and testers.
-=== 7. Maintenance ===
+=== Deployment ===
-Post-deployment, the software enters the maintenance phase, where it is regularly updated and improved to meet evolving user needs and fix any detected issues. This phase may include bug fixes, performance enhancements, and the addition of new features. Maintenance is crucial for the long-term success and sustainability of the software application, and it often consumes a significant amount of the overall project budget and resources.
+Upon successful testing, the software moves into the deployment phase. This stage involves the installation and configuration of the software in a production environment. Deployment strategies may vary, from traditional installations to cloud-based releases, depending on the architecture of the application.
-== Software Development Methodologies ==
+User training and support plans are often implemented during this phase to ensure that end-users can effectively utilize the new software. The deployment phase also includes post-deployment reviews and monitoring to ensure that the software performs as expected in a real-world setting.
-Various methodologies have been developed to facilitate the SDLC, each with its own philosophy and approach towards managing the software development process. Below are some of the most commonly used methodologies:
+=== Maintenance ===
+The maintenance phase is the final stage of the Software Development Life Cycle and involves ongoing support and enhancement of the software after deployment. This phase is crucial for addressing issues that arise during operation, rolling out updates, and implementing new features based on user feedback.
+Software maintenance can be categorized into corrective maintenance, adaptive maintenance, and perfective maintenance. Corrective maintenance focuses on fixing errors, adaptive maintenance addresses changes in the operational environment, and perfective maintenance involves enhancing system performance or adding new functionalities.
+== Methodologies within the Software Development Life Cycle ==
+Various methodologies exist within the scope of the Software Development Life Cycle, each with its unique approach and focus.
 === Waterfall Model ===
-The Waterfall model is one of the most traditional approaches to SDLC, characterized by a linear progression through each phase. Each phase must be completed before the next one begins, making it straightforward but inflexible. The Waterfall model is best suited for projects with well-defined requirements that are unlikely to change.
+The Waterfall model is one of the earliest formalized approaches to software development. It is characterized by a linear and sequential progression of stages, where the completion of one phase leads directly to the initiation of the next. One of the main advantages of the Waterfall model is the clarity it provides in project planning and documentation. However, its rigidity can be a limitation, as changes in requirements during later stages can cause significant disruption.
 === Agile Methodology ===
-Agile is an iterative and incremental approach to SDLC that emphasizes flexibility and collaboration between cross-functional teams. Agile methodologies, such as Scrum and Kanban, encourage frequent reassessment of requirements and deliverables, allowing for adaptability to changing priorities. Agile development promotes regular feedback from stakeholders, which fosters continuous improvement throughout the project's lifecycle.
+Agile methodology prioritizes flexibility and customer collaboration over strict adherence to process. Agile teams work in iterative cycles, known as sprints, which allow for frequent reassessment of project priorities. This methodology encourages continuous feedback from users, making it suitable for projects where requirements evolve rapidly. The Agile Manifesto emphasizes four key values: individuals and interactions, working software, customer collaboration, and responding to change.
-=== Spiral Model ===
+=== DevOps ===
-The Spiral model combines elements of both iterative development and the Waterfall model, allowing developers to build a system in incremental releases known as iterations. Each iteration includes phases of planning, risk analysis, engineering, testing, and evaluation, making it suitable for high-risk projects. The Spiral model focuses on risk management and incorporates user feedback at each iteration.
+DevOps is a modern framework that seeks to integrate software development (Dev) and IT operations (Ops) to enhance the speed and quality of software delivery. By fostering a culture of collaboration, automation, and continuous improvement, DevOps aims to shorten the software development lifecycle. It incorporates practices such as Continuous Integration (CI) and Continuous Deployment (CD) to automate manual tasks, facilitating faster releases and better code quality.
-=== V-Model ===
+== Real-world Examples ==
-The V-Model, or Validation and Verification model, extends the Waterfall approach by emphasizing the relationship between development stages and corresponding testing activities. In the V-Model, each development phase has a directly associated testing phase, ensuring that validation and verification are integrated throughout the SDLC. This model is well-suited for projects with strict regulatory and compliance requirements.
+The principles of the Software Development Life Cycle are applied in various real-world software projects across different industries.
-=== DevOps ===
-DevOps is a cultural movement that fosters collaboration between development and IT operations teams, aiming to reduce the time between writing code and deploying it in production. By integrating continuous integration, continuous delivery, and continuous deployment practices, DevOps promotes the rapid delivery of high-quality software while maintaining system stability.
+=== Enterprise Resource Planning Systems ===
-== Real-world Applications and Comparisons ==
+Organizations often implement Enterprise Resource Planning (ERP) systems to streamline their operations. The SDLC plays a crucial role in these projects, guiding the development of customized software that integrates various business processes. The planning stage involves understanding the specific needs of each department, while the analysis and design phases ensure alignment with organizational goals.
-The choice of SDLC methodologies varies across organizations and projects, depending on factors such as project size, complexity, and stakeholder requirements. Real-world applications of SDLC can be observed in various sectors, including finance, healthcare, education, and e-commerce.
+=== Mobile Application Development ===
-=== Case Study: E-commerce Platform Development ===
+Mobile app development projects consistently utilize the SDLC to navigate the complexities of building applications for diverse platforms. In the Agile context, mobile development teams iterate on user feedback, enhancing functionalities in subsequent releases. The testing phase becomes particularly important in this domain, as user experience and performance are vital for app success.
-In the development of an e-commerce platform, an Agile methodology may be selected to accommodate the dynamic nature of market demands and quickly evolving consumer preferences. Through regular sprints, the development team can release new features, gather user feedback, and iterate on the design to enhance user experience.
+=== E-commerce Platforms ===
-=== Case Study: Healthcare System Implementation ===
+The development of e-commerce platforms requires a thorough understanding of user requirements and compliance with regulations. The SDLC helps ensure that these platforms are built with scalability and security in mind. Stakeholders utilize the analysis phase to identify essential features, while the testing phase verifies the platform's functionality and reliability before launch.
-Conversely, the development of a healthcare management system may prioritize regulatory compliance and data security, necessitating the use of the V-Model. By aligning each development phase with rigorous testing protocols, stakeholders can ensure that the system adheres to industry standards and provides reliable patient care functionalities.
+== Criticism or Limitations ==
-== Advantages of Software Development Life Cycle ==
+Despite its widespread use and adaptation, the Software Development Life Cycle is not without criticism.
-Utilizing the SDLC framework offers numerous advantages for software development projects:
+=== Rigidity in Traditional Models ===
-* '''Improved Quality''': A structured approach ensures comprehensive requirements identification and reduces the likelihood of defects in the final product.
-* '''Enhanced Project Management''': SDLC provides a clear roadmap, assisting project managers in tracking progress, budgeting, and resource allocation.
-* '''Predictable Costs and Timelines''': With clearly defined phases, stakeholders can estimate project duration and costs more accurately.
-* '''Better Risk Management''': Early identification of risks allows teams to mitigate potential issues and adapt more effectively to changes in requirements.
-* '''Increased Stakeholder Involvement''': Well-defined phases promote continuous stakeholder input, resulting in a product that better meets user expectations.
-== Limitations and Challenges of SDLC ==
+Traditional models, such as Waterfall, have been criticized for their rigid structure, which can lead to inefficiencies and delays if requirements change late in the process. This inflexibility can result in projects that fail to meet user needs or are delivered late, causing dissatisfaction among stakeholders.
-Despite its advantages, the Software Development Life Cycle also presents several limitations and challenges:
+=== Overhead in Documentation ===
-* '''Inflexibility of Traditional Models''': Rigid methodologies, such as Waterfall, may struggle to accommodate changing requirements, leading to increased costs and project delays.
-* '''High Resource Requirement''': Comprehensive documentation required at each phase can result in significant time and resource investment.
-* '''Overemphasis on Documentation''': An excessive focus on documentation may detract from the collaborative and innovative aspects of software development.
-* '''Not Suitable for All Projects''': Certain fast-paced or small-scale projects may benefit more from less structured approaches, leading to the exploration of alternative methodologies.
-* '''Resistance to Change''': Organizations accustomed to traditional methods may find it challenging to adapt to new SDLC approaches, such as Agile or DevOps.
-== Influence and Impact ==
+The emphasis on documentation in traditional SDLC models can potentially lead to overhead, consuming valuable time and resources. Some argue that excessive documentation may detract from hands-on development and collaboration, which can stifle creativity and innovation.
-The Software Development Life Cycle has had a profound impact on the field of software engineering. Its structured approach has influenced the development of best practices, coding standards, and project management methodologies. Furthermore, the evolution of SDLC has paved the way for more dynamic and specialized development techniques, addressing the increasing complexity and diversity of software systems today.
+=== Challenges in Agile Adoption ===
-As technology continues to evolve, the concepts of SDLC are likely to adapt and transform, incorporating emerging trends such as artificial intelligence, machine learning, and cloud computing. By embracing innovative methodologies and integrating advanced tools, organizations can optimize their software development processes and enhance their ability to deliver high-quality software solutions in a rapidly changing digital landscape.
+While Agile methodologies offer flexibility, their implementation can be challenging. Teams transitioning from traditional models to Agile may face cultural resistance and difficulties in adapting to new processes. Furthermore, Agile's reliance on customer collaboration can present challenges in managing stakeholders' expectations.
 == See also ==
-* [[Software engineering]]
+* [[Software development]]
 * [[Agile software development]]
-* [[Waterfall model]]
+* [[System development lifecycle]]
-* [[Software requirements specification]]
+* [[DevOps]]
-* [[Software architecture]]
+* [[Software testing]]
+* [[Project management]]
 == References ==
-* [https://www.ibm.com/software-engineering/ IBM - Software Engineering]
+* [https://www.ibm.com/cloud/learn/software-development-lifecycle SDLC Overview - IBM]
-* [https://www.sei.cmu.edu/ The Software Engineering Institute]
+* [https://www.investopedia.com/terms/s/software-development-life-cycle.asp What is the Software Development Life Cycle? - Investopedia]
-* [https://www.iso.org/iso-12207-software-lifecycle.html ISO/IEC/IEEE 12207 - Software Lifecycle Processes]
+* [https://www.cio.com/article/245346/what-is-the-software-development-life-cycle-its-methodologies-and-how-to-manage-it.html The Software Development Life Cycle: Its Methodologies and How to Manage It - CIO]
-* [https://www.agilealliance.org/ Agile Alliance]
+* [https://www.tutorialspoint.com/sdlc/index.htm Software Development Life Cycle (SDLC) - TutorialsPoint]
-* [https://www.devops.com/ DevOps Institute]
-* [https://www.scrum.org/ Scrum Alliance]
-* [https://towardsdatascience.com/ The Evolution of Software Development Methodologies]
-[[Category:Software]]
 [[Category:Software engineering]]
-[[Category:System development]]
+[[Category:Software development]]
+[[Category:Computer science]]