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 structured process utilized by software developers and project managers to design, develop, test, and deploy software systems. The SDLC consists of several distinct phases, each of which plays a critical role in ensuring the final product meets user expectations and satisfies various requirements. The objective of the SDLC is to produce high-quality software that is delivered on time and within budget.
+== 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 SDLC serves as a methodology that guides software development teams through a series of steps from conception to completion. By adhering to the principles of the SDLC, teams can manage risks, improve the overall quality of their output, and ensure effective communication among stakeholders. The SDLC encompasses diverse models, including Waterfall, Agile, Spiral, and V-Model, which cater to different project requirements and organizational cultures.
+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 and Background ==
+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 the SDLC has evolved over several decades in response to changing technological landscapes and increasing complexity in software projects. Although early programming initiatives required only basic planning, the advent of commercial software development necessitated more formal methodologies.
+== Stages of the Software Development Life Cycle ==
-=== Early Approaches ===
+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 1960s and 1970s, initial software development efforts were characterized by rudimentary planning and informal coding practices. As software systems grew in complexity, the need for structured approaches became apparent. The Waterfall model, introduced by Dr. Winston W. Royce in 1970, was one of the earliest formal methodologies. This linear model emphasized sequential phases that required completion before progressing to the next stage.
+=== Planning ===
-=== Emergence of Agile Models ===
+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 the late 1990s and early 2000s, the limitations of traditional methodologies, particularly the Waterfall model, prompted the emergence of more iterative and flexible approaches to software development. The Agile Manifesto, created in 2001 by a group of software developers, advocated for collaboration, adaptability, and incremental progress in the software development process. Agile methodologies such as Scrum and Extreme Programming (XP) gained traction across industries as they offered greater responsiveness to changing requirements.
+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.
-=== Current Trends ===
+=== Analysis ===
-Today, the SDLC is recognized as an essential component of successful software development projects. Many organizations adopt hybrid models that integrate elements of both traditional and Agile methodologies, leveraging the strengths of each approach to meet project-specific demands.
+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.
-== Phases of the Software Development Life Cycle ==
+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.
-The SDLC is typically divided into several key phases, each contributing to the overall success of software development. While the exact number and names of these phases may vary among different models, the fundamental principles remain consistent.
+=== Design ===
-=== 1. Requirement Analysis ===
+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.
-The first phase of the SDLC involves gathering and analyzing the requirements of the software system. Stakeholders, including end-users, management, and developers, collaborate to identify specific needs, challenges, and constraints. Techniques such as interviews, surveys, and workshops are often employed to gather comprehensive information.
+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.
-=== 2. Planning ===
+=== Implementation ===
-Following requirement analysis, a clear project plan is formulated to outline the scope, objectives, resources, timelines, and budget for the development effort. This phase involves identifying potential risks and developing mitigation strategies, ensuring a robust foundation for the project.
+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.
-=== 3. Design ===
+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.
-During the design phase, architects and developers create detailed software specifications based on the requirements outlined in the previous phase. This includes defining system architecture, user interfaces, and database structures. Various design models, such as Unified Modeling Language (UML) diagrams, may be utilized to visualize the architecture.
+=== Testing ===
-=== 4. Implementation ===
+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.
-The implementation phase involves the actual coding and development of the software based on the designs created earlier. Developers write code in accordance with best practices and coding standards while implementing necessary libraries and frameworks. This phase may also include version control systems to manage code changes and track progress.
+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.
-=== 5. Testing ===
+=== Deployment ===
-Testing is a crucial phase of the SDLC, where the software is rigorously evaluated to identify and rectify defects. Various testing methods, such as unit testing, integration testing, system testing, and acceptance testing, are conducted to ensure the software functions as expected. Automated testing tools may also be employed to enhance efficiency and accuracy.
+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.
-=== 6. Deployment ===
+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.
-Once testing is complete and any identified issues have been resolved, the software is deployed to a production environment. This phase includes the installation of the software on user systems, configuration, and training for end-users. Smooth deployment is crucial for minimizing disruptions and maximizing user adoption.
+=== Maintenance ===
-=== 7. 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.
-The final phase of the SDLC involves ongoing maintenance and support for the software after its deployment. This includes bug fixes, updates, and enhancements as users provide feedback and new requirements emerge. Regular maintenance ensures the software remains relevant and functional over time.
+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.
-== Usage and Implementation ==
+== Methodologies within the Software Development Life Cycle ==
-The SDLC is widely utilized across various industries, including finance, healthcare, telecommunications, and technology. Its importance is particularly pronounced in software development projects with strict deadlines, regulatory requirements, or complex stakeholder needs.
+Various methodologies exist within the scope of the Software Development Life Cycle, each with its unique approach and focus.
-=== Application in Different Methodologies ===
+=== Waterfall Model ===
-Various SDLC models cater to different types of projects and team dynamics. Commonly used methodologies include:
+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.
-* '''Waterfall Model:''' A linear, sequential approach is best suited for projects with well-defined requirements.
-* '''Agile Model:''' An iterative model emphasizing flexibility and continuous delivery, suitable for projects requiring rapid adaptation.
-* '''Spiral Model:''' Combines iterative development with a focus on risk assessment, ideal for large and complex projects.
-* '''V-Model:''' An extension of the Waterfall model that emphasizes verification and validation at each phase.
-Organizations may choose a specific model based on project size, complexity, and desired outcomes.
+=== Agile Methodology ===
-=== Best Practices for Implementation ===
+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.
-Implementing an effective SDLC involves adhering to best practices, including:
+=== DevOps ===
-* '''Effective Communication:''' Ensuring open channels among stakeholders facilitates better understanding and collaboration throughout the project.
-* '''Documentation:''' Comprehensive documentation at each phase serves as a reference for future development efforts and aids in knowledge transfer.
+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.
-* '''Risk Management:''' Identifying potential risks early in the SDLC enables teams to develop appropriate mitigation strategies.
-* '''Quality Assurance:''' Implementing quality assurance practices, including regular code reviews and testing at all stages, enhances software reliability.
 == Real-world Examples ==
-Understanding the practical application of the SDLC is essential for grasping its significance in the software development landscape. Several well-known software products and systems have successfully utilized structured SDLC practices.
+The principles of the Software Development Life Cycle are applied in various real-world software projects across different industries.
-=== Example 1: E-commerce Platform ===
-A leading e-commerce company may follow an Agile SDLC model to develop and enhance its platform. This approach allows the company to quickly adapt to changing consumer trends and integrate new features such as payment gateways, user recommendations, and personalized marketing tools. By conducting regular sprints and incorporating user feedback, the company successfully deepens user engagement.
-=== Example 2: Banking Software ===
-A financial institution developing a robust online banking system would typically adopt a Waterfall or V-Model approach. Given the high stakes involved in financial transactions, thorough planning and stringent testing are essential to fulfill compliance requirements. Detailed documentation and phase-wise verification ensure the security and functionality of the application before its deployment.
+=== Enterprise Resource Planning Systems ===
-=== Example 3: Mobile Application ===
+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.
-A startup launching a mobile application may utilize an Agile SDLC model to remain flexible and responsive to user feedback. As the team releases initial versions of the app, they gather user input and rapidly iterate on features, enhancing the application based on real-world usage. This continuous improvement cycle enables the startup to quickly align with market demands.
+=== Mobile Application Development ===
-== Criticism and Controversies ==
+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.
-While the SDLC has been widely adopted due to its ability to streamline software development, it has also faced criticism and controversy. Detractors argue that certain methodologies can be rigid and may not accommodate the dynamic nature of software projects.
+=== E-commerce Platforms ===
-=== Limitations of Traditional Models ===
+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.
-The Waterfall model, in particular, has been criticized for its linear approach, which may not effectively address changing user requirements during the later phases of development. Sticking to predefined phases can lead to project delays and increased costs, especially if critical changes are discovered late in the process.
+== Criticism or Limitations ==
-=== Agile Misconceptions ===
+Despite its widespread use and adaptation, the Software Development Life Cycle is not without criticism.
-Agile methodologies, while popular, have also been met with skepticism concerning their interpretation and implementation. Organizations that adopt Agile practices without fully understanding the principles may struggle with inconsistent results. Agile requires cultural changes, team collaboration, and a commitment to continuous improvement — challenges that some teams may find difficult to navigate.
+=== Rigidity in Traditional Models ===
-=== Process Overhead ===
+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.
-Some critics highlight the potential for excessive process overhead when implementing certain SDLC models. Teams may become bogged down by documentation requirements, meetings, and bureaucratic procedures, hampering creativity and slowing down delivery.
+=== Overhead in Documentation ===
-== 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 SDLC has significantly influenced the evolution of software engineering practices, promoting structured thinking and project management techniques. Its principles extend beyond software development and have impacted disciplines such as project management, systems engineering, and product management.
+=== Challenges in Agile Adoption ===
-=== Advancements in Tools and Methodologies ===
+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.
-The establishment of formal SDLC models has led to an abundance of tools and software aimed at enhancing productivity and effectiveness. Project management tools such as Jira, Trello, and Asana have evolved to facilitate various SDLC stages, from planning to testing. Additionally, Continuous Integration and Continuous Deployment (CI/CD) practices have emerged, emphasizing rapid development cycles while maintaining quality.
-=== Empowering Collaboration ===
-The SDLC has underscored the importance of collaboration across cross-functional teams in software development. By incorporating roles such as business analysts, developers, testers, and project managers, organizations can foster innovative thinking and diverse perspectives that contribute to project success.
-=== Education and Training ===
-The structured nature of the SDLC has prompted the establishment of curricula and training programs aimed at developing skilled software professionals. Educational institutions now offer specialized courses in software engineering, focusing on SDLC methodologies, tools, and practices that are pivotal for career success.
 == See also ==
-* [[Software engineering]]
+* [[Software development]]
 * [[Agile software development]]
-* [[Waterfall model]]
+* [[System development lifecycle]]
+* [[DevOps]]
 * [[Software testing]]
 * [[Project management]]
-* [[Continuous integration]]
-* [[DevOps]]
 == References ==
-* [https://www.agilealliance.org Agile Alliance]
+* [https://www.ibm.com/cloud/learn/software-development-lifecycle SDLC Overview - IBM]
-* [https://www.cio.com/article/319324/software-development-life-cycle-the-essentials.html CIO - Software Development Life Cycle: The Essentials]
+* [https://www.investopedia.com/terms/s/software-development-life-cycle.asp What is the Software Development Life Cycle? - Investopedia]
-* [https://www.nasa.gov NASA - Software Development Best Practices]
+* [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.scrum.org Scrum.org]
+* [https://www.tutorialspoint.com/sdlc/index.htm Software Development Life Cycle (SDLC) - TutorialsPoint]
-* [https://www.ibm.com/cloud/learn/software-development-life-cycle IBM - Software Development Life Cycle]
-* [https://agilemanifesto.org/ Agile Manifesto]
 [[Category:Software engineering]]
 [[Category:Software development]]
-[[Category:Software lifecycle]]
+[[Category:Computer science]]