ENGIMY.IO - CHEATSHEET
SDLC × QUICK REFERENCE
SDLC
SOFTWARE ENGINEERING REFERENCE

SOFTWARE
DEVELOPMENT LIFECYCLE.

A comprehensive reference for SDLC – phases, methodologies, models, and best practices. All in one place.

REFERENCE v1.0

SDLC Quick Reference

Everything you need day‑to‑day – process, methodologies, and best practices.

What is SDLC?

  • SDLC – Software Development Life Cycle
  • Framework for planning, creating, testing, and deploying software
  • Provides structure and standardisation
  • Helps manage time, cost, and quality
  • Ensures stakeholder alignment

SDLC Phases

1. Planning
  • Define project scope and objectives
  • Feasibility study (technical, financial, operational)
  • Resource estimation and allocation
  • Risk assessment
  • Deliverable: Project plan, feasibility report
2. Requirements Analysis
  • Gather and document user needs
  • Functional vs non‑functional requirements
  • Create Software Requirements Specification (SRS)
  • Stakeholder interviews and workshops
  • Deliverable: SRS document
3. Design
  • Create system architecture
  • Database design (ER diagrams)
  • UI/UX design (wireframes, prototypes)
  • High‑level and low‑level design
  • Deliverable: Design documents, prototypes
4. Implementation (Coding)
  • Write code according to design specifications
  • Follow coding standards and guidelines
  • Unit testing by developers
  • Code reviews and version control
  • Deliverable: Source code, executables
5. Testing
  • Verify software meets requirements
  • Identify and fix defects
  • Functional, integration, system, UAT testing
  • Performance and security testing
  • Deliverable: Test reports, QA sign‑off
6. Deployment
  • Release software to production
  • Deployment planning and rollout strategy
  • User training and documentation
  • Data migration (if applicable)
  • Deliverable: Deployed software, user manuals
7. Maintenance
  • Bug fixes and patches
  • Performance improvements
  • Feature enhancements
  • Support and incident management
  • Deliverable: Updated versions, support logs
8. Retirement (Optional)
  • End of life planning
  • Data archiving and migration
  • System decommissioning
  • Deliverable: Retirement plan, archive

SDLC Methodologies

Waterfall

  • Linear, sequential approach
  • Each phase completed before next
  • Pros: Simple, structured, easy to manage
  • Cons: Inflexible, late testing, no feedback loop
  • Use when: Requirements are clear and stable

Agile

  • Iterative, incremental approach
  • Sprints (1‑4 weeks) with continuous feedback
  • Pros: Flexible, fast, customer involved
  • Cons: Less documentation, scope creep
  • Use when: Requirements are evolving

Scrum

  • Agile framework with roles (PO, SM, Team)
  • Ceremonies: Sprint Planning, Daily Standup, Review, Retrospective
  • Artifacts: Product Backlog, Sprint Backlog, Burndown Chart
  • Pros: Transparent, adaptive
  • Cons: Requires experienced Scrum Master

Kanban

  • Visual workflow management (Kanban board)
  • Continuous delivery, no fixed iterations
  • WIP (Work In Progress) limits
  • Pros: Flexible, efficient
  • Cons: Can become chaotic without WIP limits

V‑Model

  • Verification and Validation model
  • Testing planned in parallel with development
  • Pros: Early testing, quality focus
  • Cons: Rigid, not good for complex projects

Spiral

  • Risk‑driven iterative model
  • Combines Waterfall and prototyping
  • Pros: Excellent risk management
  • Cons: Complex, expensive
  • Use when: Large, high‑risk projects

Lean

  • Focus on value, eliminate waste
  • Continuous improvement, fast delivery
  • Pros: Efficient, customer‑centric
  • Cons: Requires cultural shift

DevOps

  • Combines development + operations
  • CI/CD, automation, monitoring
  • Pros: Faster releases, better collaboration
  • Cons: Requires cultural and tooling changes

SDLC Methodologies Comparison

Methodology Approach Flexibility Customer Involvement Best For
Waterfall Linear Low Low Clear requirements, stable
Agile Iterative High High Evolving requirements
Scrum Iterative High High Complex products
Kanban Continuous High Medium Support, maintenance
V‑Model Linear Low Low Safety‑critical systems
Spiral Iterative Medium Medium Large, high‑risk projects
Lean Continuous High High Efficiency improvement
DevOps Continuous High Medium Cloud‑native, SaaS

SDLC Roles & Responsibilities

Business Analyst (BA)
  • Gather requirements
  • Bridge business and technical teams
Project Manager (PM)
  • Plan and track progress
  • Manage resources and budget
Software Architect
  • Design system architecture
  • Technology selection
Developer / Engineer
  • Write and test code
  • Implement features
QA Engineer
  • Design and execute tests
  • Ensure quality standards
DevOps Engineer
  • Manage CI/CD pipelines
  • Infrastructure and monitoring
Product Owner
  • Prioritise features (Agile)
  • Define product vision
Scrum Master
  • Facilitate Scrum ceremonies
  • Remove impediments

Best Practices

  • Choose the right methodology – based on project size, requirements, and team structure.
  • Involve stakeholders early – continuous feedback reduces rework.
  • Document key decisions – architecture, design, and requirements.
  • Automate testing and deployment – improves quality and speed.
  • Use version control – Git for all code and configuration.
  • Perform code reviews – pair programming or PR reviews.
  • Continuous integration – build and test automatically on every commit.
  • Continuous delivery / deployment – automate deployment to staging/production.
  • Monitor and log – track performance, errors, and user behaviour.
  • Regular retrospectives – improve processes continuously.
  • Prioritise security – DevSecOps approach.
  • Write clean, maintainable code – follow SOLID principles.
  • Maintain a healthy backlog – prioritise based on business value.
  • Keep the team aligned – daily standups and open communication.
📌 Quick Reference
Phases: Planning → Requirements → Design → Implementation → Testing → Deployment → Maintenance
Waterfall: Linear, sequential, clear requirements
Agile: Iterative, flexible, customer feedback
Scrum: Sprints, roles (PO, SM, Team), ceremonies
DevOps: CI/CD, automation, collaboration
Best practices: automation, code reviews, monitoring, retrospectives, security
← Back to All Cheatsheets