Software Testing Vocabulary and Acronyms

Commonly Used Abbreviations and Technical Terms in Software Testing and Quality Assurance

Acronym	Full-Form	Description
ISTQB	International Software Testing Qualifications Board	The International Software Testing Qualifications Board (ISTQB®) is responsible for the international continued education program "ISTQB® Certified Tester" For More Info:istqb
SDLC	Software Development Life Cycle	Software life cycle models describe phases of the software cycle and the order in which those phases are executed. Each phase produces deliverables required by the next phase in the life cycle.
UAT	User Acceptance Testing	This validation is carried out by end users who are familiar with the business requirements.
CFD	Cost of Fixing Defect	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
QA or SQA	Quality Assurance or Software Quality Assurance	SQA is a set of activities for ensuring quality in software engineering processes (that ultimately result in quality in software products). The activities establish and evaluate the processes that produce products.
SRS	Software Requirement Specification	Software requirement specification (SRS) is a document that completely describes what the proposed software should do without describing how software will do it. The basic goal of the requirement phase is to produce the SRS, Which describes the complete behavior of the proposed software. SRS is also helping the clients to understand their own needs.
HLD	High Level Design	High – level Design (HLD) gives the overall System Design in terms of Functional Architecture and Database design. This is very useful for the developers to understand the flow of the system. In this phase design team, review team (testers) and customers plays a major role. For this the entry criteria are the requirement document that is SRS. And the exit criteria will be HLD, projects standards, the functional design documents, and the database design document.
LLD	Low Level Design	During the detailed phase, the view of the application developed during the high level design is broken down into modules and programs. Logic design is done for every program and then documented as program specifications. For every program, a unit test plan is created. The entry criteria for this will be the HLD document. And the exit criteria will the program specification and unit test plan (LLD).
FRS	Functional Requirement Specification	The Functional Requirements Specification (FRS) documents the operations and activities that a system must be able to perform. Functional Requirements should include: Descriptions of data to be entered into the system Descriptions of operations performed by each screen Descriptions of work-flows performed by the system Descriptions of system reports or other outputs Who can enter the data into the system How the system meets applicable regulatory requirements
BRS	Business Requirement Specification	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
TTD	Test Driven Development	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
-	System Analyst	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
KT	Knowledge Transfer	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
RCN	Requirement Clarification Note	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
RTM	Requirement Tracibility Matrix	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
SUT	System Under Test	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
ECP	Equavilance Class Partitioning	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
BVA	Boundary Value Analysis	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
SDS	Software Design Specification	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
DD	Deployment Document	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
SRN	Software Release Note	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
--	Severity	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
--	Priority	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
--	Defect/Bug Tracking	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
Patch	Patch	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
Buid	Build	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
Path	Path	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
UIS	User Interphase Specifications	The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect.
All Different Requirements Are: FS - Functional Specification SRS - System Requirement Specifications SRD - System Requirement Document BRD - Business Requirement Document DRD - Design Requirement Document FRS - Functional Requirement Specifications BRS - Business Requirement Specifications UIS - User Interphase Specifications