Implementation

Having extensively discussed each module in our face detection, normalization and recognition system,
we shall now describe an implementation of the complete system. We shall also briefly discuss the
software design and the constraints on performance and efficiency. The system's user-friendly interface
is then described. It facilitates the control of the algorithm and displays the localization and recognition
results visually. To test the feature detection capabilities of the system, the localization results are verified
for a few arbitrary input images. A large, standard database of faces is then used to test the recognition
rates of the system. We follow the recognition and localization tests with a sensitivity analysis that provides
us with some insight on the inter-dependence of these two components (recognition and localization) in the
overall algorithm.

Operating in the fast changing environment of banking and financial services means new demands are constantly being put on your applications. These demands may call for minor corrections or enhancements in the applications. It is important that your business activities do not suffer any disruptions while these changes are being implemented. You can achieve this by employing our Business as Usual testing services, which involves testing all through bug corrections, parameter changes and minor enhancements to applications that require no separate release.

Our domain focused test teams work with you to conduct BAU testing. A dedicated test team, the size of which is decided in consultation with you, checks for bugs in your application during the testing phase (Defect Fix Testing) or once the application has been released for production (Product Support Testing). We help ensure that your business runs as usual, even as minor corrections or enhancements/upgrades are being made to your applications. We test applications using customer specific parameters to ensure that your specific issues/bugs are resolved. Any defects identified during the testing are raised to the development team for fixing. Defects that are re-tested and closed are moved to a defect repository for future use. After all the required reviews are completed, the regression test pack is updated with the revised test ware.