FB

Register

FN

LN

MB.NO

Email.id

UN

PW

FB Login Page

UN-Ram

PW-Ram@123

Login Button

Database-No Table

Table-No row/Column

Table-FB/Moibl

Application

Developer-done

Testing-Test

JIra-defect/issue/error/problem-assign developer—ticket id generate

+ve way-

Developer

Register page develop

FN-Mangesh-48bbbbbbb
LN-Reddy-64-55555555555555555555555555555555

Mo.no-9545466666666@@@@

Submit

UN-

PW-

Submit

Application Name= Velocity Cloths

Register / Login

Men Women

Men- Shirt Pant

Shirt- Brands, Size, Half, Full, Price

Pant- Brands, Size, Type, Price

Women- Tshirt Sadis

 Tshirt- Brands, Size, Price

Sadis- Brands, Price

Company- BA

Technical Team-PM, Solution Team, Dev Team, Test Team, CR

Dev Team- Unit Testing/WBT

One way scenario hit/ Positive scenario hit

Integration Testing

Test Team-

Positive Scenario hit- Sanity Testing

Smoke Testing

BBT/S&FT

Retesting –Assign-Dev-Jira-Dev fix-Testing-Resting

Regression Testing

Sign off-QA----Mail

UAT/Client Testing—Changes-Pant-GUI-Size-Suggestion-Notedown

Sign off

Production

Release/DM

End User

SQA

Costing

Resources

Time

Requirements

Scope

Service

Type of the project

Normal – Gaming
 Critical- Banking – 1 sum cal-

More Resources

Velocity cloth- 6month -10lacs

8month-9lacs

6month

Client-5month reminder mail

15 days

6 month & 15 days

7month

Deliver –DM-sagar-sevice-maintentabncd-4month-1month

Kite

Register

FN

LN

Mb.No

Email Id

Pan No

Submit

UN

PW

Login

UN

PW
SDLC- Software development life cycle

SDLC type-

LCD LCT

SDLC-

Used in any company / industry to design, develop & test the high quality application/
software/product

Different stages

Information Gathering-BA

Analysis-BA

Design-SA/DA/SA-HLD/LLD

Coding-Dev-F/B

Testing-WBT/BBT/GBT

Maintenance

Information Gathering-BA

BA

IG/RG

BA-Intract-Client

Collect req.

BA- document- BRS –Business req. specification

BRS-All req./Overall req.

 BRS- we don’t get

BA- Acts as bridge between client & technical team

Banking

Register

Login

2FA

Home Page

Account

Profile

Balance

Analysis

BA-Working

BA-Communicate-Client & Collect req. from client

Functionality of the application req.

BA- Prepare-SRS (Software requirement specification)

SRS-FRS(Functional req. specification)

SRS-CRS(Customer req. specification)

SRS- functional req. to be developed & system requirement that will be used

SRS- we get the SRS doc

SRC doc- Includes

1. Functional requirement(project-multiple req.)

2. Functional flow diagram(Step by step flow)
3. Use case (specific req.)
a. Description
b. Acceptance
4. Sanpshot/Screenshot/Prototype- Application without functionality

1. Functional flow diagram(Step by step flow)

Register
Login
2FA
Homepage
Request page- order, holding, fund
 Step by step stages of the application

Represent relation between the tasks

Dependencies between the tasks

2. Functional requirements

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

For example-
Register on banking app / kite

FN-Should accept character only, Length-48, Special character, digit, decimal,space..etc not allowed

LN- Should accept character only, Length-64, Special character, digit, decimal,space..etc not allowed

DB- DD-MM-YY format/ only digit

Email id- Should accept character, Special symbols, digit & deciamal, length

Mangesh123@gmail.com

Phone Number- allowed only digit, length 10, country code +91

Submit

Functional requirement

Snapshot/Screenshot/dummy model/prototype/wireframe

- BA-created
- Application without functionality
- Provide the idea to developer how SW supposed to look like
- Use- Irise software

Use Case/ User story

Requirement

Description-details about the requirement

 Acceptance-Does & don’t about the requirement

Use case/ User story- BA

Use case- Test scenario- Test cases

BRS SRS
Business Requirement specification Software requirement specification
BA prepare BRS BA prepare SRS
BA collect the requirement & BA prepare BRS SRS is derived from BRS doc
Gathering all the cut. requ. Gathering software & technical req.
Overall req. Detail req.
Use case not present Use cases are present
Ex. Ex
Kite Register
Register FN
Login LN
2FA Pan
Dashboard Mb.Mo
Watchlist DOB
Order Email id
Position Login
Funt UN
Profile PW
Login button
Forgot PW

3. Design

After completion of the SRS doc. BA sent this doc. To the developer

Analysis & Understand the req.

If developer not understand any req. so that time developer contact to the BA

Design architecture/System/Solution

HLD

LLD

HLD-

HLD is developed by- System architecture/Design

Designing structural functionality of main module known as external design

Include relation dependency of main module

It includes what & how any main module work

LLD
Coding-

Coding means programming

One line is code

Multiple line is programming

Coding- it is set of programming language designed, written by developer/ programmer know as coding

Developer-

Front end coding/developer

Back end coding/developer

Front end developer-

UI- user interface

Functionality

Flow’

Process

Back end developer

Data gathering

Data security

Data management

Algorithm

Full Stack Developer=Front end developer & back end developer

Testing

It is process to check completeness & correctness of Software w r to customer req.

Includes

1. WBT
2. BBT
3. GBT

WBT

Developer

WBT is also called as

Unit testing
 Clear box testing

Glass box testing

Transparent testing

Static testing

Code level testing

Tested their own code after development

Only positive scenario/ valid scenario

Ex- login page

+ve-

Valid UN

Valid PW

Click on the login button

Aware about the internal structure of the application

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

BBT

Tester are involve in the BBT

BBT- Tester verify/validate internal functionality of application depends on external functionality or

external interface (front end)

BBT- Build level testing/ technique

Build- Url

Test Url- https://kite.zerodha.com/dashboard

Dynamic testing

+ve & -ve Scenario hit

Tester validate end to end testing

Tester validate step by step testing

Main role of BBT- Only check internal functionality depends on the external functionality

Not aware about the internal structure of the application

GBT- manual / automation/ advance java /python

It’s a combination of = WBT & BBT

Knowledge about the programming

Tester involve

Testing

Defect

Don’t revert back to the developer instead of that we solve or correct the defect

In case any defect occurs- testers make some changes in code itself intends of assigning to the
developer

Ex

Dfect- 9404624368 with counry code

Developer develop- only 10 digit field

Missing the country code

+91 code

Defect- assign/lock/raise-developer-developer fix-testing- retesting-reassign- developer- developer fix-

testing – retesting

Ad. Of GBT

Time

Efforts

Deploye- server- Dev/Sit/UAT/Prod

What is difference between WBT & BBT??

WBT BBT
Is performed by Developer Is performed by Tester
Type-2 Type-2
Unit Testing Sanity /Smoke
Integration Testing Retesting/Regression
System & functional testing etc
Developer to check the Tester to check functionality of the application
Logic for the code Type-Functional testing
Control statement Functional testing-6type
Loop statement Non Functional testing-8types
Branches etc
Is also knows as Static testing Is also called dynamic testing
It’s a coding level testing It’s a build level testing
Its also called as Its also called System & functional testing
Clear box
 Glass box
Transpert

Developer check only -+ve scenario
Developer aware about the internal
coading/structure
Static testing is called as verification
Quality assurance
Tester check both +ve & -ve scenarion
Tester not aware about the internal
coding/structure
Dynamic testing is called validation
Quality control

Testing having 2 ways

1. TCD- Test case design

2. TCE- Test case execution

Customer – Req.

BA-Collect the req.

BA-Prepare BRS

BA – Prepare SRS

After the completion of the SRS document. BA sent this document to the developer & tester

Developer Tester

After getting the document After getting the document

Developer understand the req. Tester understand the req.

Design Test case design

HLD/LLD Test case review/Self/Peer/Internal/External

Coding

Testing/Unit

Integration testing

Test case execution

Review/ Pass/Fail

Defect review/

Maintenance

After the delivery of the project or product or software or application if there is a problem or any technical
difficulty, in such case company has fix it without any cost this is nothing but maintenance

Technical support –KPO- Knowledge process outsourcing

Non-Technical support –BPO- Business process outsourcing

Fish Model

Information Analysis Design Coding Testing Support

Gathering (BRS) (SRS) (HLD, LLD) (Developers) TCD, TCE

Review (BA) Review (BA) Review (Design) WBT (White BBT (Black
Box testing) box testing)

Static testing/ Verification / Dynamic testing / Validation /

Quality assurance Quality control

Fish is an advance version of SDLC

Fish model consist of verification & validation

Verification – Quality assurance / Static testing

Validation- Quality control/ dynamic testing

Tata & Tesla

Pre Launching- One charge- 100km

Actual- one change -100km

Review/Feedback

Verification

Verification process is knows as quality assurance/ Static testing

Verification process is a actually review process

Req. Ga-

In req. ga. BA collect customer req. & prepare the BRS after completion of the BRS.. BA review the BRS
document

Any- after the completion of the BRS doc. BA prepared SRS doc based on the BRS.

Review-

After the preparation the SRS doc. BA has to check SRS doc., whether it is correct or not because all
the further process depends on the SRS doc.

Design-

S/M architecture divides design in to two part

HLD

LLD

After the completion of the design phase, S/M architecture has to do the review process

Coding-

When coder complete coding/ code, coder has to check all the code- Unit testing process

Static testing it is process responsible authority/ people do only review process

Validation

Validation process is known as Quality control / dynamic testing

Dynamic testing focus on the quality of the product

Overall functionality/ entire functionality of the product/application/software is checked by step by step

from start to end

Validation includes BBT /GBT

Validation is end to end testing process

What is difference between Verification & validation?

Verification Validation
Qaulity Assurance Quality control
Static testing Dynamic testing
Review process End to end testing process
WBT/UT BBT/GBT
Preventive technique Corrective technique
QA-SDLC QC-STLF
What is difference between Static & dynamic Testing?

Static Testing Dynamic Testing

ST- BA,Designer, developer are checking their Dynamic Testing-tester will check functionality of
own- document, design, code the application
Progress Testing/preventive End to end testing/end progress tsting
Verification Validation
QA QC
ST-Present- BA, Designer, Developer Tester

Software

Testing

Software Testing

Software development process/ Happy flow of the development process

SQA

SDLC

Fish model

Different methodology/ process/implementation/model of SDLC

There are 3 SD methodology

1. Waterfall model
2. V model
3. Agile model

Which methodology you are using in your current project or current organization?

-Agile model

Agile model- 99% company instead of waterfall model & v model

Disadvantage of waterfall & V model- Agile model

Customer req.- Customer decide- model

Amount- Customer req.- Customer decide- model

Session- Customer-BA-High level people-then decide the which model there use?

Req- Fix or vary

How may req.?

Duration of project?
 Req. constant or changes continuously?

Waterfall model V Model Agile model/module

Requirement are fixes from
customer/ client
Used for- Small project
It is a step by step or continuous
process
If requirement are changed CR-
client / customer have to pay
extra amount
Used for- Big Project
Simultaneous process
Requirement CR are vary but no
extra amount is taken from
customer
Used for- big project & complex
project
Flexible process

Project- Velocity Cloth

Waterfall- req. Fix

Amount- 10cr

V Model-10 CR new/amount/ limitation

Initial Stage req. are fix

After that BA/PM/DA/dev/tester is proceed to work

But client told in that particular module I want one sub module there

CR- Change in request

Accept-Fulfill

CR- take a money for that change

Amount- 10cr+ Req. changes amount

Agile model- Req. vary

Amount- 12cr.

Customer-recommend- which model we are use in my project?

Session-Client/BA/High level people

- Revenue
- Resources
- Decide type of testing- man/automation
- Where to be suite this project in model
- Req.
- Amount
Waterfall module

Requirement
gathering

Analysis

Design

Coding

Testing

Maintains

- Water fall module is step by step implementation of the SDLC

 - Water fall module is linear sequential design
- It is step by step process
- In waterfall module- req. from client are fixed
- It is generally designed for low project/small project, where req. from the client are fixed
- In this module before moving to next stage, current stage should be completed
- If any problems occurs during testing phase we cannot go back to the coding phase, instead of
that only we can lock the defect in that stage only but that defect should be solved in the next
version or updated version
- If any defect is found by tester do not send it to developer
- Small scale company & product based company
- Duration 1 to 3 months
- Req. are fixed
- Disadvantages
- Backtrack is not possible
- Delivery to client more than 3 month/ not fixed

Information

Gathering (BRS) – V9.0 – New Requirement (V9.1) + Old defects (V9.0)

Analysis (SRS) - V9.0

Designer (HLD) - V9.0

Coding (LLD) - V9.0

Testing – TCD, TCE – defect (V9.0)

Support

V 1.0.0

V 1.1.5

V2.0.0

http.qa.paytm.com

http.uat.paytm.com

http.dev.paytm.com
http.paytm.com

V module

V module

Verification Validation
Development Testing Stage
stage

Information Gathering
Assessment of Dev. Plan
Analysis
Preparation of Test Plan
Requirement of phase Testing

Design & Design Phase Testing

Coding Program Phase Testing

Test Case Design

(Installation Build) Sanity Testing

Integration Testing System & functional Testing

UAT

Test Documentation

Maintains
DRE RFC
Post marten testing

Regression Testing
V module

- V module stands for verification & validation

- In v module V & V working parallel
- It is mapping between development stage & testing stage to validate client req.
- In v module suppose you have completed development of one stage, and second stage is
running, & if any changes in requirement CR comes for first stage- we can go back to first
stage and fulfill that CR with extra amount.

For ex-
Mobile number field- accept only 10 digit mobile number
New CR- BA-Accept-dev-New CR- add country code in front of mobile number- to take
extra amount

- V module generally preferred for big organization

- Duration – 3 month
- Deliver Model- 5 to 6
- Who decide the v module- client
- Extra money- for change in req.