1. (VIII) Maintenance or Support: After successful software release and training our project
management defines a Change Control Board(CCB) to receive queries or requests in the future from
the customer on that software from that customer.
This CCB consists of a few developers, a few test engineers and the project manager. This team
receives two types of requests from the customer during the utilization of the software.
(Enhancement Correction) Change Request
Enhancement Missed Defect / Latent Defect
Impact Analysis Impact Analysis
(Analysis where to make changes in the S/W)
Developers
CCB
Perform that change Perform that change
Test the S/W Change Tester Test the s/w change
Review old test process capability to Improve
Change Control Board: It is the team which will handles customer requests for enhancement changes.
OBSERVATIONS
Testing Stage Verification/Validation Testing Techniques Responsible People
Reviews in Analysis Verification Walk through, inspection, Business Analyst
Peer Review
(BRS & SRS)
Reviews in Analysis Verification Walk through, inspection, Designers
Peer Review
(HLD & LLD)
Unit Testing in Coding Validation White Box Testing Techniques Developers
(on Individual Program)
Integration Testing (Two or Validation White Box Testing Techniques Developers
more Modules integrated)
System Testing on s/w build Validation Black Box Testing Test Engineers
UAT(S/W Build) Validation Alpha Testing/Beta Testing Users/Customers
Release Testing Validation Black Box Testing Release Team
Testing in Maintenance Validation Black Box Testing CCB

2. Testing Techniques:
There are 3 types of testing techniques in STLC(System Testing Life Cycle).
 Documents Testing Techniques
 White Box Testing Techniques
 Black Box Testing Techniques
(A) Documents Testing Techniques:
These techniques are also known as verification testing techniques. The responsible persons use these
techniques to review
BRSSRSHLDLLDs
There are 3 types of documentation testing techniques.
 Walk Through: verifying a document from the
 Inspection: verification of a document for some particular aspect or functionality in the
software and concentrating an specific.
 Peer Review: Requesting peers or colleagues to verify the document.
(B) White Box Testing Techniques:
These techniques are also known as Glass Box or Open Box or Clear Box testing techniques. These
techniques are applicable for programs in Unit Testing and for interface programs in integration
testing.
There are 4 types of white box testing techniques.
1) Basic Path Coverage
2) Control Structure Coverage
3) Program Technique Coverage
4) Mutation Coverage
(C)Black Box Testing Techniques:
These are also known as close box testing techniques. These techniques are applicable on the
Software builds. There are 4 types of black box testing techniques.
1) Boundary Value Analysis(BVA)
Whenever one need to develop the test cases for a range kind of input then it is suggested to
use a technique called BVA.
BVA says that instead of testing on whole range, just concentrate on the boundaries if at all
the boundaries are working fine then one can come to a conclusion then the whole range is
working fine.

3. 2) Equivalence Class Partitioning:(ECP)
Whenever one need to develop the test cases for huge range of data or a mixture of so many
requirements then it is suggested to use a technique ECP.
Equivalence Class Partition says that divides the inputs into different classes and then write
the test cases for each class separately.
3) Decision Tables
4) State transmission diagrams
5) Error guessing