1 BRS
BUSSINESS REQUIREMENTS
2 SRS/FRS
FUNCTINAL/SYSTEM REQUIREMENTS
3 DESIGN(HLDS)
HEIGHLEVEL DESIGN
OVER ALL ARCHETECTURE(ROOT TO LEAF MODULE)
4 DESIGN(LLDS)
LOW LEVEL DESIGN
MICRO LEVEL/UNIT LEVEL/MODULE LEVEL
5 CODING
UNIT TESTING(WHITE BOX TESTING)
PATHS ,LOOPS,STRUCTURE STUDIED BY DEVELOPERS.
6 INTEGRATION TESTING(GREY BOX TESTINGDONE BY TESTERS AND 
DEVELOPERS)
MORE THAN ONE(2R MORE)MODULES R INTEGRATED 
TO CHECK THE DATA FLOWAND APPEARING SCREEN WITH CONNECTIVITY
7 SYSTEM/FUNCTIONAL TESTING(BLACK BOX TESTING TECHNICSDONE 
BY TESTERS ONLY)
HEREUNDER SYS ALL S/W &H/W COPONENTSAS PER BRS(DOC) AND 
DIFFRENT NET WORKS,TOPOLOGIS AND OPERATING 
SYSTEMS,PERFORMANCE,RELAIBILITY,COMPATABILITY R CHECKED
(VALIDATED)
UNDER FUNCTIONAL
6 COVERAGES
1 BEHAVIRAL COVERAGER GUI COVERAGE:
WHICH VALIDATES THE BEHAVIOR OF OBJ IN SCREEN WITH RESPECT 
TO OPERATIONS.
2I/P DOMINE COVERAGE:
BASED ON B.V.A AND E.C.P VALUSES WE VALIDATE THETEXT BOXES 
AND CHECK LIST BOXES ETC..
3ERROR HANDLING:
MEANING FUL MSGS W.R.T WRONG OPERATIONS
TO GUIDE THE USER
4 BACK END COVERAGE:
VALIDATING THE BACK ENDDATA VALIDATION AND DATA INTEGRITY 
WRT TO FRONT END OPERATIONS.
5 MANUPULATIONS:
VALIDATING OUT PUT AND OUT COME
OUT PUT= MATHAMATICAL  CALUCULATIONS.
OUT COME =GETTING RELAVENT WINDOWS /SCREENS IN THE NXT 
WINDOW
6 SANITATION:
REMOVING EXTRA FUNCTIONALITIES WHICH MAY CAUSE CONFUSION TO 
CUSTEMOR.
8 UAT(USER ACCEPTANCY TEST)
THERE R TWO TYPES
1 ALPHA--TESTING:FOR APPLICATION/PROJECT
2BETA-- TESTING :FOR PRODUT
THE TWO TESTS INTETION IS SAME I.E TO GET FEE BACK FROM 
CUSTMOR
 THE MAI THING WE HAVE TO KEEP IN MIND THAT AT EACH AND 
EVERY STEGE R PHASE THERE R REVIEWS INSECTIONS TO MODIFY 
THE PROCESS SUCH THAT WE CAN ENSURE BUG FREE 
PRODUCT/PROJECT/APPLICATION TO THE CLIENT
IF U WISH MORE MAIL ME
PHANI