SDLC (Software development life cycle)-

• SDLC 6 stages
1. Information gathering
2. Analysis
3. Design
4. Coding
5. Testing
6. Maintenance/ support
Information Gathering

Analysis

Design

Coding

Testing

Maintenance
Information gathering-
• In Information gathering stage BA will work
• BA will interaction/ communicate with Client
• BA will take business related requirement form client
• In Information gathering stage, BA will prepare a documents
BRS (business requirement Specification)
• Ex. XYZ Client → Business module → Client business module
• BRS documents will not get share to developer & Tester
• BA is taking Requirement from clients/Customers & Preparing BRS document
Simply it acts as bridge between

BA

Client Technical Team

(Project Team)

Analysis-
• In analysis stage BA will work
• BA will interact/ communicates with Client
• BA will take software/application related requirement form
client
• In analysis stage, BA will prepare a documents SRS (software
requirement Specification)
• SRS documents also called FRS(functional requirement
Specification)/ CRS (customer requirement Specification)
• Ex. Zoom Car→ Login page, Login email/ mobile no., Car
selection, Location ,payment method, etc,
• SRS documents will contains
 1. Functional requirements (1 module = 15 requirement)
2. Functional flow diagram
3. Use Cases (1 requirement)
A. Description- Details about the requirement
B. Acceptance criteria- Does & don’t about requirement
4. Screenshot/ snapshot/ Prototypes – Image about application/
software
• When BA will complete these documents, BA will sent these
documents to developer & tester throw mail
• Developer & tester will understand these SRS
• If requirements is not clear or understand then developer &
tester will take meeting with BA
1. Functional flow Diagram

• Represents step by step stages of Application/product

• Represents relation between the task

• Dependencies between the tasks

2. Functional requirement

Meeting the attributes which are required to complete specific function/Task

For Example – Register on Banking App

First name - Should accept Character only, Length | Special Char not allowed

Last name - Should accept Character only, Length | Special Char not
 allowed DOB – DD-MM-YYYY format |Only Digits

Email Id - ?

Phone number – Allowed only

digits Submit button - ?

This how functional requirement

3. Use Case –(specify requirement/ 1 requirement)

Description – Details about requirement
Acceptance criteria-Does & Don’t about requirement
Use cases– Test scenarios – Test cases – Testing – entre system – start to end
Use case testing is a technique that helps to identify test cases that cover the
entire system, from start to finish.

• Use case is combination of - Input + Process + Output

• Checking the functionality for available input , process & output

E.g. Use case for online shopping

Uses Case name : Cash withdrawal
Actors : Customer
Description : this use case describes how the customer uses the ATM system to withdraw
cash from bank account

Work Flow :

Actor The customer will insert their debit card

System The system will prompt for the pin
Actor The customer will enter the pin
System The system will display the option to “withdraw cash “
Actor The customer will select the option to withdraw cash
System The system will prompt for an amount
Actor The customer will enter the amount
System The system will submit the amount to the bank for approval
Actor The bank will confirm the transaction
System The system will dispense the cash amount
Actor The system will return the card
System The use case ends with a success
 4. Snapshot - Application without
functionality Snapshot is
format/Review/Prototype
Snapshot provides idea to Developer how SW supposed to
be look like Snapshot created by BA
Uses Irise Software for snapshot creation
Visualization of functionality before development
of product IRise with 8.11 Version

• When BA will completed the SRS documents, then BA will sent these
documents to developer & tester
• BA will sent these documents throw Mail to Developer & Tester team
• Developer & Tester team will do the analysis/ understand the documents
• If we have doubt about SRS documents, then developer & Tester team will
communicate to BA (For communicate we will conduct meeting)
Difference between BRS & SRS?

BRS SRS
Business requirement specification Software requirement specification
This document generally consists of In SRS document all functional
complete scope of the project,
performance, requirement, and usability. and non- functional requirements
are covered.
BA people prepares BRS BA people prepares SRS
From client BA collects the requirements SRS is derived from BRS
and
prepares BRS document
Gathering Customer requirements Gathering Software & Technical Req.
Use cases are not present in BRS Use cases are present in SRS.
Overall req. Detail req.
E.g., Banking Domain
Sign Up Sign Up page-Logo,
page Home
Page UN,PW Number,
Account Information
Contact List Special Character

Design-
• When BA will sent SRS documents to designer
• Designer will do or prepared the HDL (High level design), LLD (Low level
design)
• Ex. Paytm – Mobile No. frame box & Browser planes frame

System architecture develops the

design It have two stages
1. HLD – High level design
2. LLD – Low level design

HLD – High level design

High level design is developed by System architecture or design

architecture Designing Structural functionality of Main module

Known as External Design Include relation dependency of main

module
 It includes what & how any main modules work

Understand architecture of entire application from main module to sub module

E.g. booking ticket

Low Level Design

Defines static logic of every sub modelling

Designing Structural functionality of Sub module know as

internal design Low level design is created by front end

developer

E.g. booking ticket

Coding:

Coding means

programing One line is

code

Multiple line of code is known as program

It is set of programing language designed, written by programmer

known as coding
 Developer- There are two types

Front End developer/Coding – UI, Functional checking, flow, process developed

by Front End developer
Back End developer/coding – data management, data gathering,
data security, algorithm section is done at the back end section
developed by Back End Developer

Developer who is work on front end development as well as back end

development called as full stack developer

Testing
It is a process to check
Completeness & correctness of software/ Application w.r.to customers ‘requirement

Testing having three types of testing –

I. White box Testing

II. Black Box Testing
III. Grey Box Testing

White box Testing [Clear Box testing, Glass Box testing, TransparentTesting]

It is a coding level testing approach to check Completeness & correctness of program

• It is also called as - Clear Box testing, Glass Box testing,

Transparent Testing

• Because its open end or transparent testing

• Also known as static Testing

• IN WBT – only Developers are involved

 • Performing code level testing, Unit Testing – Tested their own
code after development

• Only Positive scenarios / valid scenarios

• Aware about internal structure of application

• Before deploying the code tested own code to make sure there is no
bugs

WBT
Testing +Ve Scenarios

Developers
Black Box Testing

In the black box testing tester verify/ validates internal functionality of

application depends on external interface (front end)

It’s a build level testing Technique

It is also known as functional & system testing or

Also Known as dynamic testing

Tester validated end to end testing step by step

Tester executes positive & negative scenarios – valid and invalid data

Tester are involved

Check the internal functionality depends upon

external data Not aware about internal structure of

application

Testing BBT
+Ve & - Ve Scenarios

Tester

Positive scenario – E.g. Mobile number 10 digit

Negative scenario - ?
Gray box Testing –

What is & Why?

Advantages? GBT = WBT

+BBT

Gray box testing - It’s a combination of white box testing & Black

box testing Testers are involved in this type of testing

In the gray box testing Testers needs some knowledge of programing language
In case any defect occurs – testers makes some changes in code itself instead
of assigning to the developers

Advantage – Time & Efforts savage

WBT (White Box testing) BBT (Black Box testing)

WBT is performed by developer BBT is performed by Tester
WBT is 2 types BBT is 2 types

- Unit Testing - Sanity Testing/ Smoke testing

- Integration Testing
In WBT check, Logic for Code,
Condition statement, Loop statement,
branches, etc
WBT also called as code level testing
It is known as static Testing
It’s a coding level testing technique
It is known as clear box |Glass
Box| Transparent
Testing
Developers are involved
In WBT developers tested their own code In BBT Tester test end to end
Check for + scenario
Aware about internal structure
Static testing is called as Verification Dynamic testing is called as Validation
Quality Assurance
- System & functional testing
- Re-testing, etc
Tester will do the check some coverage
– Input domain coverage, error
handling coverage,
Backend coverage, etc
BBT also called as System &
functional
testing
It is known as dynamic testing
It’s a build level testing technique
It is called as system & function testing
Tester are involved
functionality
Check for +Ve & –Ve scenarios
Not Aware about internal structure
Quality Control
 Customers’ Requirements

BA

BRS

SRS

Developer Test Case design

Design

Coding

Testing

Integration Testing

Test case execution

Review

Its static testing technique used to check - Completeness & correctness

of the documents

Review can be taken to monitor

quality Assurance Types of review

1. Test Case Review

2. Execution Case Review

Defect Case Review

Root cause review – finding exact root of bug

Maintains

• After delivery of product/ Application Service

comes in picture – part of service provided by

company.

• In case of ant technical difficulty service is to be provided

without any additional cost

• Companies like Tech Mahindra, provided

support to customers like different customers

 Maintains be

Technical support –

called as KPO

Non-Technical

support – called as

BPO

Interview Question

1. What is software testing

2. Manual Testing
3. SQA? Features?
4. What is SDLC? Stages in SDLC?
5. How Many tester & Developers in your Team?
6. What do you mean by SRS & BRS documents? Or Difference?
7. Black Box testing?
8. What is Gray box testing?
9. Are you be the part of WBT?
10. Did you worked as Gray box tester?
11. Testing start before development or after development?
12. Static vs. dynamic Testing
13. What is software project?
14. What is difference WBT & BBT
15. What is difference Verification & Validation
15. What is snapshot
16. Team size? Roles?
17. Who is good tester?
18. Why you joined as a tester?