CBIRFrame - An Object-oriented for Content-based Image Retrieval 

INVESTIGATORS

Mr. Kent K. T. Cheung, Dr. Horace H. S. Ip

BRIEF DESCRIPTION

Many Content-based Image Retrieval (CBIR) systems have been proposed in the literature. These systems share many similarities but subtle differences exist among them. To enable fast development of CBIR systems, there is a need for an reusable framework that can cater for the differences while providing the fundamental functionality of CBIR systems. A reusable object-oriented framework for CBIR systems is proposed. This framework, as discussed in our publications, help developers to develop high quality of CBIR systems effectively.

FUNDING AGENCY

N/A

PUBLICATIONS

  1. Kent K. T. Cheung, Horace H. S. Ip, Ringo W. K. Lam, R. Hanka, Lilian H. Y. Tang and G. Fuller, "An Object-oriented Framework for Content-based Image Retrieval Using a 5-tier Architecture", Proc. Asia Pacific Software Engineering Conference 99, 7-10 Dec. 1999, Takamatsu, Japan, pp 174-177.

  2. Kent K. T. Cheung, Ringo W. K. Lam, Horace H. S. Ip, Lilian H. Y. Tang, R. Hanka, "A Software Framework for Combining Iconic and Semantic Content for Retrieval of Histological Images", Proc. 4th Intl. Conf. Visual 2000, 2-4 Nov., 2000, Lyon, France, pp. 488-499.

5-tier Architecture




This architecture shows the various components of the system into separate layers so they these layers can be deveoped independently, thus providing the highest flexiblity.

The Domain Component (DC) is the central layer. Domain specific classes should be defined in this layer without regard how they are displayed or how to store or retrieve to the database. The user interface is provided in the User Interface Component (UIC) while the Data Management Component (DMC) provides database access functionality. These layers are similarity to an application based on the 3-tier architecture.

To further minimize the dependence among the layers, two additional layers, i.e., the facade layers, are added. The UI Facade provides a bridge between the UIC and the DC while the DM Facade bridges the gap between DC and DMC. The objects in the UI Facade forwards the requests of services in the UIC to the DC. Similarity, the DM Facade forwards database access requests from DC to DMC.

Advantages: By adding the two Facade layers, the three tiers become more independent so that any changes in one tier does not affect the others.

Domain Component




We define many classes related to image analysis and retrieval. Most of them are pure virtual and template claesses. This provides the maximum freedom for the framework user to choose the most appropriate data structures for the application at hand. To render the framwork directly, we have developed default classes for all these data structures so that applications that rely on simple and standard data structures may take advantage of the framework directly.

User Interface Component and User Interface Facade




The diagram shows the classes in the UIC and UI Facade.

Since the UIC is responsible for user interface handling, it is natural that classes in this layer are designed for a speicific operating environment. Nevertheless, our 5-tier architecture makes this less restrictive as we can easily deveop a CBIR system that operates on more than one platforms by writing different classes in the UIC only. The DM Facade successfully separates the UIC and the DC classes so that change of the UI platform has no effect on the application design.

As there are many systems that are designed to be run on a platform running Ms Windows platform, we defined a few classes that are suitable for use in this platform. If the application at hand is designed to be run on Windows, the framework user can use these classes.

Data Management Component and DM Facade


The diagram shows the how the objects in the DC request services to the DM Facade, which in turns requests services and obtain results from the DMC.

The DMC is actually the native DBMS API that performs the actual database processing. The DM Facade requests the DMC for database access on behalf of the objects in the DC. Therefore, if ther is any change in the DMC, we need only replace the DBMS API and the DM Facade without affecting the other modules of the system. See I-Browse for an advance use of this feature of CBIRFrame.

Applications