Essay --

5 SOFTWARE REQUIREMENT SPECIFICATIONS This chapter discusses the software requirement specification about the project followed the functional and non-functional requirement of the â€Å"INTERACTIVE SKETCHED BASED IMAGE SEARCH†. 5.1 Purpose When a sketch is input by a human there will clearly be a degree of accuracy to which the point of reference and scale of the shapes will remembered, and so errors with comparison to the target image or images will be present. The edges of objects and neighborhood within the image define shapes; extraction of these shapes can be used for image similarity. This supports indexing leads to imaginative memory usage since the indexes are always smaller than images themselves. Indexing speeds up the search process lengthily which is very important in the image search application. 5.2 Scope The input plan of this project is the improvement of a system to allow the searching of database of images using the visual data stored within the images. Here the aim is to develop a system which allows query upon the image content of the images, with the user providing a sketch of the image or images that they desire to retrieve. The key aim is the development of a speedy and correct algorithm for the extraction and comparison of the visual data from images. Some important point takes in consideration while development they are as follows: †¢ Identification of the restriction of current content based images retrieval systems so that these areas can be improved upon. †¢ Research into the field of content based image retrieval and rapid algorithm development. †¢ Design and accomplishment of a system to perform content based image retrieval using sketched input. †¢ Expansion of an algorithm for the extraction and sim... ... for that. In Unit testing, is the first level of testing and is performed prior to integration testing. All error handling paths should be tested. Drivers and/or stubs need to be developed to test incomplete software. 7.2.2 Integration Testing In integration testing the individual tested units are grouped as one and the interface between them is tested. There are mainly three approaches to do integration testing, Top-down approach, Bottom-up approach Big bang approach Integration testing is a software testing methodology used to test individual software components or units of code to verify interaction between various software components. Main program used as a test driver and stubs are substitutes for components directly subordinate to it. Subordinate stubs are replaced one at a time with real components (following the depth-first or breadth-first approach).