Embed Size (px)
DESCRIPTION
SDLC models - Software testing
Citation preview
SDLC PhasesPlanning
Business value
Project Cost
Return on Investment
Project Plan
Project Kick Off
SDLC PhasesAnalysis
Requirement Gathering and Analysis
Requirement Documentation
System inputs
System Functions
Output of Analysis Phase
SDLC PhasesDesign
Design Specification
Technology to be used
Requirements are broken down to modules
Functional Planning
SDLC PhasesDevelopment
Design specification to Working Model
Develop Components
Components are integrated to Complete System
Unit Testing
SDLC PhasesTesting
Testing Activities based on Test Plan
Bug Tracking and Fixes
Testing Sign off
SDLC PhasesMaintenance
Troubleshooting
Help Desk and Training
Latest updates of the Software
The Waterfall Model
Requirement Analysis Phase
System Design Phase
Maintenance Phase
Testing Phase
Implementation Phase
The Waterfall Model
Requirement Analysis Phase
Requirement Gathering and Consolidation Requirement Analysis Requirement specification document
Entry Criteria: Requirements from End UserExit Criteria: Requirement specification document
The Waterfall Model
System Design Phase
System Design is created Hardware and software requirements Requirement specification document System Architecture System Design specification document
Entry Criteria: Requirement specification document Exit Criteria: System Design specification document
The Waterfall Model
Implementation Phase
Modules are identified Modules are developed Unit Testing
Entry Criteria: System Design specification document Exit Criteria: Unit Test Sign-off
The Waterfall Model
Testing Phase
Integration Testing System Integration Testing Defect tracking and fixes Bug Re-Testing Regression Testing
Entry Criteria: Unit Test Sign-offExit Criteria: System Test Sign-off
The Waterfall Model
Maintenance Phase
Production defects are resolved Customer Support
Entry Criteria: System Test Sign-offExit Criteria: Application shutdown or no updates
The V-Model
Prepare for Acceptance Test
Prepare for Integration Test
Prepare for System Test
Preparation for Unit Test
Requirement Analysis
High-level Design System Testing
Acceptance Testing
Integration TestingDetailed Design
Coding Unit Testing
The V-Model – Verification and Validation
Prepare for Acceptance Test
Prepare for Integration Test
Prepare for System Test
Preparation for Unit Test
Requirement Analysis
High-level Design System Testing
Acceptance Testing
Integration TestingDetailed Design
Coding Unit Testing
Verification Phase Validation Phase
The V-Model – Verification Phases
Requirement
Analysis
• User Requirements are documented• Document will contain functional and non functional requirements of the system - SRS
High Level Desig
n
• Requirements are analyzed to implement• Software Specification Document is created which serves as the basis for software development.
Low Level Desig
n
• Modules are listed and functionality of each module is described.• Dependency of each module is defined• Database design and Integration testing design etc… are carried out
Coding
• Coding of the system is performed
The V-Model – Validation Phases
Unit Testing
• Modules or Components are tested separately• Testing done by developers
Integratio
n Testing
• Testing performed after integrating the Components or Modules to find defects due to integration between the modules.
• Testing performed by developers.
System
Testing
• Testing to check if it meets the functional and non functional requirements• Dependency of each module is Performed by Test Team in an environment similar to production environment.• Database design and Integration testing design etc… are carried out
UAT
• To test the system according to user and business requirements. To check if system is ready for public use.• Performed just before implementing the system in the production environment.• Performed by Business.
Agile Model
Agile Model
Iteration
Phase 1 Phase 2 Phase 3
Project
Iteration 1 Iteration 2 Iteration 3
Software SoftwareSoftware
Agile Principles
Short Term planning
Team should be given more importance than process and Tools
Creation of software should be given importance than documentation
Effort should be focused on effective collaboration with customers than bargaining maximum pricing
Ability to change during course of a project should be given priority than strict adherence to the plan
Incremental Model
Incremental Model
Module 1
Module 2
Module 3
Module 4
Stage 1
Stage 2
Stage 3
Stage 4
Module Feedback
Iterative Model
Iterative Model
New Requirements
ModuleEnhancement 1 Enhancement 2
Quality Standards
Iterative ModelRequirements
Phase
DesignPhase
Implementation and Test Phases
Review Phase
![Unit II [Software Process and SDLC Models]](https://img.pdfslide.net/doc/110x75/61e4392a004b487850207565/unit-ii-software-process-and-sdlc-models.jpg)
