Cursor

AI Assistant

Agenda Overview

What is SDLC?

Software Development Life Cycle (SDLC)

Definition :- A structured process used by software organizations to design, develop, and test high-quality software. It covers the entire life span of the software from inception to retirement.

Key Stakeholders :- Business Analysts, Developers, Architects, Project Managers.

Primary goal :- To deliver a high-quality product that meets customer expectations within time and budget estimates.

Phases of SDLC

 What is STLC?

Software Testing Life Cycle

Definition: A sequence of specific activities conducted during the testing process to ensure software quality goals are met. It is a subset of the SDLC

Key Stakeholders: QA Leads, Testers, Test Automation Engineers.

Primary Goal: To identify defects, validate functionality, and ensure the system is bug-free

 Phases of STLC

Comparison - SDLC vs. STLC

SDLC MODELS

WATERFALL MODELS

• Requirements: Gather and document all business needs and system specifications upfront before moving to the next phase.

• Design: Create the technical blueprint, including system architecture and data structures, based on the approved requirements.

• Development: Write the actual software code to build the product according to the design specifications.

• Testing: Execute test cases to verify functionality and identify any defects or bugs in the code.

• Pass Testing?: A decision checkpoint to determine if the software is bug-free (proceed to Deployment) or needs fixes (return to Development).

• Deployment: Release the final, tested software product to the live production environment for user use.

• Maintenance: Provide ongoing support, bug fixes, and updates to ensure the software continues to operate correctly over time.

AGILE MODELS

• Requirement: Define a small, manageable set of features (user stories) for the current sprint rather than the entire project at once.

• Design: Create a quick, lightweight technical plan or prototype specifically for the features selected in the current sprint.

• Develop: Write and implement the code for the selected features, focusing on producing working software quickly.

• Test: Continuously verify the new code against requirements and run regression tests to ensure existing features still work.

• Deploy: Release the working increment of the software to a staging or production environment for immediate user availability.

• Review: Gather feedback from stakeholders and the team on the product and process to improve the next sprint cycle.

SPIRAL MODELS

• Planning: Determine the objectives, alternatives, and constraints for this specific iteration (spiral) of the project.

• Risk Analysis: Identify potential technical or management risks (like budget overruns or unclear tech) and find ways to resolve them before coding.

• Engineering: Design, develop, and test the actual software prototype or working version for this cycle.

• Evaluation: The customer reviews the work produced in the Engineering phase and provides feedback to guide the next spiral.

V MODELS

V MODELS

• Right Side (Validation - Bottom-Up)

Unit Testing: Testing individual code modules.
 

Integration Testing: Testing combined modules.
 

System Testing: Testing the complete system.
 

User Acceptance Testing (UAT): Validating the system meets user requirements.

• Left Side (Verification - Top-Down)

Requirements Analysis: Defines user needs; maps to User Acceptance Testing (UAT).

System Design: High-level design; maps to System Testing.

Architectural Design: Detailed system structure; maps to Integration Testing.

Module Design (Low-Level Design): Component design; maps to Unit Testing.
Bottom (Implementation)

• Coding: The actual software development.

ITERATIVE MODELS

• Start Small: Begin with a basic set of requirements for a simple, initial version (prototype) of the software.
• Cyclical Process (Iteration): Repeat the core Software Development Life Cycle (SDLC) phases for each enhancement.
• SDLC Phases in Each Cycle:
  • Planning & Requirements: Define goals for the current iteration.
  • Design & Prototyping: Create a testable design/prototype.
  • Implementation & Testing: Build and test the added features.
  • Evaluation & Feedback : Get input from stakeholders/users.
• Incremental Growth: Each iteration adds new features or refines existing ones, making the system more complete.
• Feedback Loop: Crucial for identifying issues and guiding the next iteration's focus.
• Repeat Until Done: The process continues until the final, complete system is ready. 

PROTOTYPING MODELS

• Requirements Gathering: Initial vague requirements are collected from the customer.
• Quick Design: A basic, rough design is created for the prototype, focusing on core functionality, not full details.
• Prototype Development: A working model (wireframe, mockup, or simple code) is built.
• User Feedback & Testing: The prototype is shown to users/customers for evaluation and feedback.
• Refinement/Correction: Based on feedback, the prototype is modified; this cycle repeats.
• Final Product Development: Once the prototype is accepted, the complete, robust system is built, coded, and deployed.

RAD (Rapid Application Development)MODELS

• Requirements Planning: Defines the project scope and business needs through collaborative workshops rather than detailed upfront planning.

• User Design: Users actively test and refine working prototypes to shape the system functionality based on real-time feedback.

• Construction: Developers rapidly build and integrate the actual system using automated tools and parallel development cycles.

• Cutover: The final phase where the system goes live, covering final testing, data migration, and user training.

STLC MODELS

WATERFALL MODELS

• Requirements Gathering: Define all software needs (Development).

• System Design: Create system architecture (Development).

• Implementation / Coding: Write the code (Development).

• Testing (Verification): Perform unit, integration, system, and user acceptance testing (Testing).

• Deployment: Release the software.

• Maintenance: Provide ongoing support and updates.

Flowchart

    A[Requirement Analysis]

    B[Test Planning]

    C[Test Design]

    D[Test Execution]

    E[Test Closure]

    A --> B --> C --> D --> E
    E --> A

AGILE MODELS

• Requirement Analysis: Identify and understand the testable requirements and acceptance criteria for the features selected in the current sprint.
• Test Planning: Create a lightweight test strategy outlining scope, approach, resources, tools, and timelines specific to the sprint.
• Test Design: Prepare and review test cases, test data, and scenarios for the selected features, ensuring coverage of functional and regression requirements.
• Test Execution: Execute test cases, log and track defects, retest fixes, and perform regression testing to ensure existing functionality remains unaffected.
• Test Closure: Validate test completion, assess test outcomes, document test metrics, and provide sign-off feedback to improve the next sprint cycle.

Requirement Analysis

 ↓

Test Planning
 ↓
 Test Design
 ↓
 Test Execution
 ↓
 Test Closure
 ↺
 Next Sprint

SPIRAL MODELS

• Test Planning: Define testing objectives, scope, approach, resources, and constraints for the current testing cycle.
• Risk Analysis: Identify testing risks such as insufficient test coverage, environment issues, or unclear requirements, and plan mitigation strategies before test execution.
• Test Design & Preparation: Design test scenarios, test cases, and test data based on requirements, and set up the required test environment for this cycle.
• Test Execution: Execute test cases, report and track defects, retest fixes, and perform regression testing to ensure stability.
• Test Evaluation & Closure: Review test results with stakeholders, assess product quality and testing effectiveness, and use feedback to improve the next testing cycle.

Test Planning
 ↓
 Risk Analysis
  ↓
Test Design &
 Preparation
  ↓
 Test Execution
  ↓
Test Evaluation
   & Closure
      ↺
 Next Cycle

V MODELS

V MODELS

• Right Side (Validation - Bottom-Up)

Unit Testing: Testing individual code modules.
 

Integration Testing: Testing combined modules.
 

System Testing: Testing the complete system.
 

User Acceptance Testing (UAT): Validating the system meets user requirements.

• Left Side (Verification - Top-Down)

Requirements Analysis: Defines user needs; maps to User Acceptance Testing (UAT).

System Design: High-level design; maps to System Testing.

Architectural Design: Detailed system structure; maps to Integration Testing.

Module Design (Low-Level Design): Component design; maps to Unit Testing.
Bottom (Implementation)

• Coding: The actual software development.

Conclusion

 What is the fundamental relationship between SDLC and STLC?

 What is the fundamental relationship between SDLC and STLC?

Which SDLC model follows a strict linear approach where a new phase cannot begin until the previous one is 100% complete?

Which SDLC model follows a strict linear approach where a new phase cannot begin until the previous one is 100% complete?

B) Spiral Model 

C) Waterfall Model