Download content based image retrieval and more Study Guides, Projects, Research Audiovisual Communication in PDF only on Docsity!
1. INTRODUCTION
Two different types of approaches, i.e., text- and content based, are usually adopted in image retrieval. In the text-based system, the images are manually annotated by text descriptors and then used by a database management system to perform image retrieval. However, there are two limitations of using keywords to achieve image retrieval: the vast amount of labor required in manual image annotation and the task of describing image content is highly subjective. There are inconsistencies between user textual queries and image annotations or descriptions. To alleviate the inconsistency problem, the image retrieval is carried out according to the image contents. Such strategy is the so-called content-based image retrieval (CBIR).
2. SYSTEM ANALYSIS
2.1 Existing System
- The vast amount of labor required in manual image annotation.
- Inconsistencies between users query and results..
2.2 Proposed System
- Uses the contents of an image such as color , shape , texture to represent and index the image.
- Satisfies users expectations by retrieving similar images.
3.3 Software Profile Front End: Microsoft. Net Microsoft .NET is a set of Microsoft software technologies for rapidly building and integrating XML Web services, Microsoft Windows- based applications, and Web solutions. The .NET Framework is a language-neutral platform for writing programs that can easily and securely interoperate. There’s no language barrier with .NET: there are numerous languages available to the developer including Managed C++, C#, Visual Basic and Java Script. The .NET framework provides the foundation for components to interact seamlessly, whether locally or remotely on different platforms. It standardizes common data types and communications protocols so that components created in different languages can easily interoperate. “.NET” is also the collective name given to various software components built upon the .NET platform. These will be both products (Visual Studio.NET and Windows.NET Server, for instance) and services (like Passport, .NET My Services, and so on). The .Net Framework The .NET Framework has two main parts:
- The Common Language Runtime (CLR).
- A hierarchical set of class libraries. The CLR is described as the “execution engine” of .NET. It provides the environment within which programs run. The most important features are
- (^) Conversion from a low-level assembler-style language, called Intermediate Language (IL), into code native to the platform being executed on.
- Memory management, notably including garbage collection.
- Checking and enforcing security restrictions on the running code.
- Loading and executing programs, with version control and other such features.
- (^) The following features of the .NET framework are also worth description: Managed Code The code that targets .NET, and which contains certain extra Information - “metadata” - to describe itself. Whilst both managed and unmanaged code can run in the runtime, only managed code contains the information that allows the CLR to guarantee, for instance, safe execution and interoperability. Managed Data With Managed Code comes Managed Data. CLR provides memory allocation and Deal location facilities, and garbage collection. Some .NET languages use Managed Data by default, such as C#, Visual Basic.NET and JScript.NET, whereas others, namely C++, do not. Targeting CLR can, depending on the language you’re using, impose certain constraints on the features available. As with managed and unmanaged code, one can have both managed and unmanaged data in .NET applications - data that doesn’t get garbage collected but instead is looked after by unmanaged code. Common Type System The CLR uses something called the Common Type System (CTS) to strictly enforce type-safety. This ensures that all classes are compatible with each other, by describing types in a common way. CTS define how types work within the runtime, which enables types in one language to interoperate with types in another language, including cross-language exception handling. As well as ensuring that types are only used in
Basic and C++ (as VB.NET and Managed C++), but there are also a number of new additions to the family. Visual Basic .NET has been updated to include many new and improved language features that make it a powerful object-oriented programming language. These features include inheritance, interfaces, and overloading, among others. Visual Basic also now supports structured exception handling, custom attributes and also supports multi-threading. Visual Basic .NET is also CLS compliant, which means that any CLS-compliant language can use the classes, objects, and components you create in Visual Basic .NET. Managed Extensions for C++ and attributed programming are just some of the enhancements made to the C++ language. Managed Extensions simplify the task of migrating existing C++ applications to the new .NET Framework. C# is Microsoft’s new language. It’s a C-style language that is essentially “C++ for Rapid Application Development”. Unlike other languages, its specification is just the grammar of the language. It has no standard library of its own, and instead has been designed with the intention of using the .NET libraries as its own. Microsoft Visual J# .NET provides the easiest transition for Java- language developers into the world of XML Web Services and dramatically improves the interoperability of Java-language programs with existing software written in a variety of other programming languages. Active State has created Visual Perl and Visual Python, which enable .NET-aware applications to be built in either Perl or Python. Both products can be integrated into the Visual Studio .NET environment. Visual Perl includes support for Active State’s Perl Dev Kit. Other languages for which .NET compilers are available include
• FORTRAN
• COBOL
Fig1. Net Framework ASP.NET XML WEB SERVICES
Windows Forms
Base Class Libraries Common Language Runtime Operating System
C#.NET is also compliant with CLS (Common Language Specification) and supports structured exception handling. CLS is set of rules and constructs that are supported by the CLR (Common Language Runtime). CLR is the runtime environment provided by the .NET Framework; it manages the execution of the code and also makes the development process easier by providing services.
C#.NET is a CLS-compliant language. Any objects, classes, or components that created in C#.NET can be used in any other CLS- compliant language. In addition, we can use objects, classes, and components created in other CLS-compliant languages in C#.NET .The use of CLS ensures complete interoperability among applications, regardless of the languages used to create the application.
Constructors and destructors:
Constructors are used to initialize objects, whereas destructors are used to destroy them. In other words, destructors are used to release the resources allocated to the object. In C#.NET the sub finalize
C#.NET supports structured handling, which enables us to detect and remove errors at runtime. In C#.NET, we need to use Try… Catch…Finally statements to create exception handlers. Using Try… Catch…Finally statements, we can create robust and effective exception handlers to improve the performance of our application.
The .Net Framework
The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet.
Objectives of. Net framework
- To provide a consistent object-oriented programming environment whether object codes is stored and executed locally on Internet-distributed, or executed remotely.
- To provide a code-execution environment to minimizes software deployment and guarantees safe execution of code.
- Eliminates the performance problems. There are different types of application, such as Windows-based applications and Web-based applications.
4. SYSTEM DESIGN
4.1 Block Diagram
5. PROJECT DESCRIPTION
The main objective of the project is to perform the effective image retrieval to perform desired task. The image retrieval process is associated with multimedia databases and digital image libraries. It contains large amount of images. Our project is used to perform effective image retrieval process. In traditional system the image retrieval process is implemented by text based annotations. The images are stored with name labels and it is used as the keyword for retrieval process. If any name labels are incorrect that particular images will not be retrieved in the retrieval process. In our system the images are retrieved based on their contents it doesnot depends on the keyword. Even though the names are incorrect the similar images are retrieved. The contents such as color, shape, texture are used for similarity comparison. The output similar images are displayed in deviation increasing order. During the comparison process the deviation between the input images and the output images that are in the databases are calculated if it fully similar with the input image, it will be displayed first. Based on the variations the output images are listed. The interactive genetic algorithm allows the user to evaluate their output and if they are not satisfied they can perform incremental search. But in traditional system the search has obtained for a long time to obtain the desired image. Our system will satisfy the users expectation within a short period of time. The input to our system is not a keyword, instead we are using image query. The images are stored in the system directories, which can be loaded when needed. The used can select input from a folder and which can be loaded in the source picture box. The output images displayed in gridview by displaying their deviation between the input image and output images. It is an effective and user friendly system. Consider a database which contains full of medical images, which can be
retrieved for different medical processing system. By using the keyword based system the user can retrieve the expected image only if he know the correct name but using our system the user can retrieve the similar or small varied images without domain knowledge. It can also used for company logo comparison, each companies have separate logo. While developing logo for their own company they have to compare with other company logo to check whether it is matched with any other company logo. If exists they have provide some changes. To perform this type of comparison our system provides better comparison outputs.
It contains following modules:
- Comparable Image selection
- Feature Extraction
- Visual feature comparison
- Similarity Images display
Comparable Image selection Using this module user can select the input image from the directory which is used for compare with other destination images which are in the same directory or different directory. Feature Extraction The features such as color, shape, texture will be extracted from the selected input image by using MPEG7 similarity descriptor such as edge histogram and scalable color descriptor.
6. SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. It provides a way to check the functionality of components, sub assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of ensuring that the Software system meets its requirements and user expectations and does not fail in an unacceptable manner. There are various types of test. Each test type addresses a specific testing requirement.
6.1 White Box Testing
White Box Testing is a testing in which in which the software tester has knowledge of the inner workings, structure and language of the software, or at least its purpose. It is purpose. It is used to test areas that cannot be reached from a black box level.
6.2 Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner workings, structure or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a definitive source document, such as specification or requirements document, such as specification or requirements document. It is a testing in which the software under test is treated, as a black box .you cannot “see” into it. The test provides inputs and responds to outputs without considering how the software works.
6.3 Unit testing
Unit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program inputs produce valid outputs. All decision branches and internal code flow
should be validated. It is the testing of individual software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a specific business process, application, and/or system configuration. Unit tests ensure that each unique path of a business process performs accurately to the documented specifications and contains clearly defined inputs and expected results.
6.4 Integration testing
Integration tests are designed to test integrated software components to determine if they actually run as one program. Testing is event driven and is more concerned with the basic outcome of screens or fields. Integration tests demonstrate that although the components were individually satisfaction, as shown by successfully unit testing, the combination of components is correct and consistent. Integration testing is specifically aimed at exposing the problems that arise from the combination of components.
6.5 Functional testing
Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals. Functional testing is centered on the following items: Valid Input : identified classes of valid input must be accepted. Invalid Input : identified classes of invalid input must be rejected. Functions : identified functions must be exercised. Output : identified classes of application outputs must be exercised. Systems/Procedures: interfacing systems or procedures must be invoked.
7.SCREEN LAYOUT
