Software development life cycle [SDLC]

System Development Life Cycle - Svitla

  • The Software Development life cycle is also known as the Application Development life cycle.

  • It's a process of planning, analysis, designing, creating, testing and deploying software systems.

  • The system development life cycle framework provides a sequence of activities for system designs and developers to follow.

  • It consists of a set of steps or phases in which each phase of SDLC uses the results of the previous one.

  • There are various SDLC models, such as the Waterfall model, Agile, Scrum, and Spiral models, and also DevOps each with its unique approach to the development process.

  • The choice of the SDLC model depends on the project's nature, requirements, and the organization's development choices.

  • Waterfall method :

  • Diagram of Waterfall methodology

  • The oldest and most straightforward approach with this methodology, we finish one phase and start the next each phase has its own -mini-plan in waterfalls into

    • 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 the 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 into 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 each unit. Post integration the entire system is tested for any faults and failures.

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

    • Maintenance: Some issues 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 Advantages :

  • 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 :

  • Not suitable for projects where requirements are at a moderate to high risk of changing. So, risk and uncertainty are 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.

Agile Method :

Agile for Dummies: Introduction. Agile is becoming so popular in IT… | by  Jeremia Delviero | Medium

Agile methodology is a project management framework that breaks projects down into several dynamic phases, commonly known as sprints.

After every sprint, teams reflect and look back to see if there was anything that could be improved so they can adjust their strategy for the next sprint.

  • Customer Collaboration over Contract Negotiation: Agile places a strong emphasis on involving customers and stakeholders throughout the development process. Regular feedback and collaboration help ensure that the software meets the actual needs of the users.

  • Responding to Change over Following a Plan:

    Agile acknowledges that requirements can change during the development process, and it encourages teams to be adaptable and respond to changes in priorities, technology, and business needs.

  • Working Software over Comprehensive Documentation: While documentation is still important, Agile prioritizes delivering functional software over extensive documentation. The focus is on creating valuable, working software that can be continuously improved.

  • Individuals and Interactions over Processes and Tools: Agile values the importance of effective communication, teamwork, and collaboration among team members. The emphasis is on empowering individuals to make decisions and solve problems.

Agile Method Advantages :

  • Since then agile projects are client-focused, agile makes sure that the client is involved in every stage continuously.

  • The team members demonstrate better performance. Because coordination and collaboration among team members are key to the success of agile projects.

Agile Method Disadvantages :

  • Less predictable.

  • More time and commitment.

  • Greater demands on developers and clients.

  • Lack of necessary documentation.

  • Projects easily fall off track.

To implement Agile successfully, various frameworks and methodologies have been developed, including Scrum, Scrum, in particular, is one of the most popular Agile frameworks and is widely used.

Scrum Method :

Scrum is an agile development methodology used in the development of Software based on an iterative and incremental process.

  • Scrum is an adaptable, fast, flexible and effective agile framework that is designed to deliver value to the customer throughout the development of the project.

  • The primary objective of Scrum is to satisfy the customer’s need through an environment of transparency in communication, collective responsibility and continuous progress.

  • The development starts from a general idea of ​​what needs to be built, elaborating a list of characteristics ordered by priority (product backlog) that the owner of the product wants to obtain.

Thanks for reading.

@ankitashinde99

https://www.linkedin.com/in/ankitashinde99/