Skip to content

sdlc-flow.md

Latest commit

 

History

History
197 lines (148 loc) · 6.21 KB

sdlc-flow.md

File metadata and controls

197 lines (148 loc) · 6.21 KB

Software Development Life Cycle (SDLC)

Overview

The Software Development Life Cycle (SDLC) is a systematic process for planning, creating, testing, and deploying software applications. It provides a structured approach to software development that ensures quality and efficiency.

SDLC Phases

┌─────────────────────────────────────────────────────────────────┐
│                        SDLC FLOW                                │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│   ┌──────────────┐    ┌──────────────┐    ┌──────────────┐     │
│   │   Planning   │───►│ Requirements │───►│   Design     │     │
│   │    Phase     │    │   Analysis   │    │    Phase     │     │
│   └──────────────┘    └──────────────┘    └──────────────┘     │
│                                                   │             │
│                                                   ▼             │
│   ┌──────────────┐    ┌──────────────┐    ┌──────────────┐     │
│   │ Maintenance  │◄───│  Deployment  │◄───│ Development  │     │
│   │    Phase     │    │    Phase     │    │    Phase     │     │
│   └──────────────┘    └──────────────┘    └──────────────┘     │
│                              ▲                    │             │
│                              │             ┌──────────────┐     │
│                              └─────────────│   Testing    │     │
│                                            │    Phase     │     │
│                                            └──────────────┘     │
└─────────────────────────────────────────────────────────────────┘

1. Planning Phase

Objective: Define the project scope, objectives, and feasibility.

Key Activities:

  • Identify project goals and objectives
  • Conduct feasibility study (technical, operational, economic)
  • Define project scope and timeline
  • Allocate resources and budget
  • Risk assessment

Deliverables:

  • Project Charter
  • Feasibility Report
  • Project Schedule

2. Requirements Analysis Phase

Objective: Gather and document detailed requirements from stakeholders.

Key Activities:

  • Stakeholder interviews
  • Requirements gathering sessions
  • Document functional requirements
  • Document non-functional requirements
  • Requirements review and approval

Deliverables:

  • Software Requirements Specification (SRS)
  • Use Case Diagrams
  • User Stories

3. Design Phase

Objective: Create the architecture and design of the system.

Key Activities:

  • System architecture design
  • Database design
  • UI/UX design
  • API design
  • Security design

Deliverables:

  • High-Level Design (HLD)
  • Low-Level Design (LLD)
  • Database Schema
  • Wireframes/Mockups

4. Development Phase

Objective: Build the actual software based on design specifications.

Key Activities:

  • Code development
  • Unit testing
  • Code reviews
  • Version control management
  • Documentation

Deliverables:

  • Source Code
  • Unit Test Cases
  • Technical Documentation

5. Testing Phase

Objective: Verify the software meets requirements and is bug-free.

Key Activities:

  • Test planning
  • Test case development
  • Test execution
  • Defect tracking
  • Regression testing

Deliverables:

  • Test Plan
  • Test Cases
  • Bug Reports
  • Test Summary Report

6. Deployment Phase

Objective: Release the software to the production environment.

Key Activities:

  • Environment setup
  • Deployment planning
  • Release management
  • User training
  • Go-live support

Deliverables:

  • Deployment Guide
  • Release Notes
  • User Manuals

7. Maintenance Phase

Objective: Provide ongoing support and enhancements.

Key Activities:

  • Bug fixes
  • Performance optimization
  • Feature enhancements
  • Security patches
  • User support

Deliverables:

  • Maintenance Reports
  • Updated Documentation
  • Patch Releases

SDLC Models

Model Description Best For
Waterfall Sequential, linear approach Small, well-defined projects
Agile Iterative, incremental approach Dynamic requirements
Scrum Agile framework with sprints Team-based development
V-Model Verification and Validation Safety-critical systems
Spiral Risk-driven iterative approach Large, high-risk projects
DevOps Continuous integration/delivery Rapid deployment needs

QA Role in SDLC

Quality Assurance is involved throughout the SDLC:

Phase QA Activities
Planning Review project plans, identify quality risks
Requirements Validate requirements, create test strategy
Design Review design documents, plan test approach
Development Review code, create test cases
Testing Execute tests, report defects
Deployment Verify deployment, smoke testing
Maintenance Regression testing, monitor quality

Best Practices

  1. Early QA Involvement - Include QA from the planning phase
  2. Clear Documentation - Maintain comprehensive documentation
  3. Regular Reviews - Conduct reviews at each phase transition
  4. Risk Management - Identify and mitigate risks early
  5. Continuous Improvement - Learn from each project cycle