"FRONT OFFICE AUTOMATION SYSTEMEquivalence Partitioning:In this method we divide input domain of a program into classes of data from whichtest cases are derived. An equivalence classrepresents a set of valid or invalid or asset ofrelated values or Boolean condition. The equivalence for these is: Input condition requires specific or non specific two classes.? Input condition requires as range-in the range-out or out of rangetwo classes.? Input condition specifies a member of a set belongs to a set or not belongs to a settwo classes.? Input condition is Boolean valid or invalid Boolean condition two classes.By these types of two classes, we can test for many cases.Boundary values analysis: No of errors usually occurs at the boundaries of the input domain generally. In thisa selection of test case is exercised using boundaries values i.e. around boundaries.By the above two techniques we eliminated almost all errors from the software andchecked from numerous test values for each and every input value. The results weresatisfactory.6.3 VALIDATION TESTING: Validation testing demonstrates the traces the requirements of the software. Thiscan be achieved through a serious of black box testing.DEPT OF IT, PDCE 2009-2010 Page 58 FRONT OFFICE AUTOMATION SYSTEMSystem testing:System testing is actually a series of different tests whose primary propose is tofully exercise to the computer based system. The various tests include recovery testing,stress testing, and performed testing.Code testing: Specific testing is done to check if the program does what it should do and how itshould behave under various conditions or combinations and submitted for processing inthe system and it is checked if any overlaps occur during the processing.Unit testing: The first level of testing is called as unit testing. Here different modules are testedagainst the specifications produced during the design of the modules. Unit testing is doneto test the working of individual modules with test Sql servers. Program unit is usuallysmall enough that the programmer who developed it can test it in a great detail. Unit testingfocuses first on that the modules to locate errors. These errors are verified and correctedand so that the unit perfectly fits to the project.System testing: This is the next level of testing and acceptance testing, and is done to check if thesystem has met its requirements and to find the external behavior of the system.System testing involves two kinds of activities:? Integration testing,? Acceptance testing.DEPT OF IT, PDCE 2009-2010 Page 59 FRONT OFFICE AUTOMATION SYSTEMPerformance time testing: Performance time testing is done to determine how long it takes to accept andrespond. It is essential to check the exception speed of the system, which runs well withonly a hand full of test transactions. Some system might be slow when fully loaded.Providing large set of data for processing does so testing. A system testing is designed touncover weaknesses that were not detected in the earliest tests.The total system is tested for recovery and fall back after various major failures toensure that no data is lost during an emergency. An acceptance test is done to ensure theabout the validity and reliability of the system.DEPT OF IT, PDCE 2009-2010 Page 60 "