Computer Science Project Topics

A Framework for Nation-wide Integration of Biometric Information

A Framework for Nation-wide Integration of Biometric Information

A Framework for Nation-wide Integration of Biometric Information

Chapter One

Aim and Objectives

The aim of this research work is to develop a framework for nation-wide integration of biometric information.

The following objectives combine to achieve the aim:

  1. To develop a platform that can serve as a wrapper for biometric data captured;
  2. To develop a centralized database system of biometric information of Nigerian nationals; and
  3. To integrate security control of access to system.

CHAPTER TWO

LITERATURE REVIEW

This chapter gives an overview of the basic concepts that relate to the research, starting with explanation of some basic concepts in database systems, to biometric technology, with emphasis on fingerprinting, as it is the biometric feature adopted in this study. It also presents a review of some previous works that have been done by other researchers.

 Overview of Database Systems

A database management system (DBMS) is software that allows creation, definition and manipulation of database (Ramez & Navathe, 2011). A DBMS is actually a tool used to perform any kind of operation on data in a database. A database is a collection of related data organized in a way that data can be easily accessed, managed and updated (Malik & Patel, 2016). A DBMS also provides protection and security to a database (Deepika & Soni, 2013).

Any piece of information can be a data, for example, an image, a number, an address, even a biometric template. A database is a place where related pieces of information are stored and various operations can be performed on it (Kulkarni & Urolagin, 2012). Some examples of popular DBMSs are MySQL, Oracle, Sybase, Microsoft Access and IBM DB2.

Evolution of Database Technology

The earliest forms of database systems were the hierarchical and network systems, introduced from the mid-1960s through to the 1980s (Ramez & Navathe, 2011). Although they provided large organizations with large record support, they had challenges of flexibility in accessibility and changes in requirements. Next, the era of relational systems began in the early 1980s, providing answers to data abstraction and program-data independence. However, the need to transit from simple to complex structured objects led to the object-oriented database systems.

The object-oriented database systems were introduced in the 1980s; they included object-oriented paradigms like abstraction, inheritance, and encapsulation. They provided a more general data structure but unfortunately, did not gain much attention as expected. They are now mainly adopted for use in specialized applications, with less than 5% penetration (Ramez & Navathe, 2011).

Presently, with the success in traditional databases, developers are expanding the capabilities of database systems to support more diverse applications ranging from scientific, image storage and retrieval, time series, to data mining etc. (Ramez & Navathe, 2011).

Database Architecture

As per the architecture of a database, logically, it can be divided into two:

  • 2-tier client architecture
  • 3-tier client architecture

 Two-Tier Architecture

Two-tier Client/Server architecture is used for user interface programs and application programs that run on the client side. An interface called ODBC (Open Database Connectivity) provides an API that allows client-side programs to call the DBMS. Most DBMS vendors provide ODBC drivers. A client program may connect to several DBMSs. In the architecture, some variation in client functionality is also possible. For example in some DBMSs, more functionality is transferred to the client including data dictionary and optimization. Such clients are called data server. If the architecture of DBMS is two-tier, then it must have an application through which the DBMS can be accessed. Programmers use two-tier architecture where they access the DBMS by means of an application. Here the application tier is entirely independent of the database in terms of operation, design, and programming (Ramez & Navathe, 2011).

Three-Tier Architecture

Three-tier client/server database architecture is a commonly used architecture for web applications. An intermediate layer called application server or web server stores the web connectivity software and the business logic (constraints) part of application used to access the right amount of data from the database server. This layer acts like a medium for sending partially processed data between the database server and the client (Ramez & Navathe, 2011).

 

CHAPTER THREE

RESEARCH METHODOLOGY

This chapter discusses the way in which the implementation of the research work was carried out, explaining the methods, languages and software used in implementing the thesis work.

Data Collection

The data set used for this research includes both hard biometrics, soft biometric traits and other relevant data of individuals.

As hard biometrics, the following were used:

  1. Fingerprint templates: the fingerprints captured were for both thumbs. The fingerprints were captured using the digital persona U4500 fingerprint scanner. This fingerprint scanner uses fingerprint minutiae data format to store
  2. Facial images: full 24-bit colour frontal images were taken with facial expression neutral, teeth closedand both eyes  In addition, three samples of facial images were taken, with one left and one right and one frontal (for the central database). They were captured using an Android phone device and were stored in JPEG format.

The soft biometric traits used were:

  1. Gender
  2. Height
  3. Ethnicity

Other data sets included in the data set were:

  1. Address
  2. Language
  3. Place of birth

 Model Description and Architecture

The system focused on reducing multiple enrolment of individuals’ fingerprint data. The approach taken for designing the platform for this is that any of the organizations (NIS, Banks, INEC) that want to register/enrol an individual, will have to verify from the central database first to ensure that this individual has not been previously enrolled in any other organization. If the individual has been enrolled previously, then he or she would be registered without collecting fingerprints again (since he or she has been verified). Otherwise, if not been registered, then he or she would be registered and his or her fingerprints collected. This is in order to have only one capturing point for fingerprints. Only one organization would enrol an individuals’ fingerprints. Every other organizations may only verify an individual from the central database but may not collect and store the fingerprint data.

The flow chart of the system is shown below:

CHAPTER FOUR

RESULTS AND DISCUSSION

This chapter presents the results obtained from the various steps of the development of the framework for this project. Ranging from the development of the various organizations’ web application, the forms designed, the various tabs, modules contained therein. It also presents an insight into the database created.

Organizations’ Web Applications

The applications are for the four different organizations involved, NIS, NIMC, INEC and Commercial Bank. Each of them has the query module, the enrolment module, the verification and finally the admin module. The enrolment module gives the interface for new individuals to be registered using the applicants’ enrolment form, which was designed on visual studio.

The verification module is used to verify (using both left and right fingerprints as discussed in section 3.6)

CHAPTER FIVE

SUMMARY, CONCLUSION AND RECOMMENDATION

 Summary

This thesis presented a framework for different organizations, providing a common platform among them to carry out authentication of individuals they want to enrol into their organization. The data collected for use included biometric information like fingerprint and facial image, while other basic information for identifying the individuals was collected too. This includes name, address LGA, state, gender etc. The above-mentioned data were used to create databases for the different organizations that were represented (NIS, INEC, Banks, NIMC). After this, the interface applications were designed using C#.net.

Conclusion

This research work developed a platform that can easily be adopted by the other organization and NIMC in achieving their long time plan of integrating the biometric information from different organizations. The platform further gives ease for authentication of Nigerians from any organization location that has access to the central database. This, it will stop the long time culture of continuously collecting and storing biometric information of individuals by various organizations while still having no use in authenticating an individual from any point outside the collecting organization. Just as in the case of the BVN which the central bank has used to create harmony across commercial banks, this platform will also create harmony across various government organizations and agencies by giving them a central point for authenticating an individual independent of the organization where this individual’s biometrics was previously captured.

Recommendation

After successfully developing this framework to serve as a wrapper for biometric information captured by various organizations, the following recommendations are made:

  1. The framework should be implemented and deployed for use by the NIMC as a platform upon which a nation-wide identity system can be
  2. Government should strictly urge and enforce other organizations against indiscriminate collection of biometric information of its citizens. Henceforth, any new capturing of biometrics should be verified first from NIMC, the central point from which other organizations can make use of for authentication/verification.

Suggestions for Further Work

In further research, the following points are raised as suggestions:

  • Other biometric traits such as iris and facial recognition should be included as options for authentication and not only
  • Toachieve a better platform, better SDKs should be used in building the  The one used for this thesis work was a free trial version with various limitations.
  • Inaddition, various fingerprint readers with different formats can be used in order to have different formats for saving the fingerprints to add a more realistic flavour to the

REFERENCES

  • Ahuja, M. S., & Chabbra, S. (2011). Biometric encryption: Combining fingerprints and cryptography. Communications in Computer and Information Science, 169 CCIS, 505–514. https://doi.org/10.1007/978-3-642-22577-2_69
  • Bala, D. (2008). Biometrics and information security. Proceedings of the 5th Annual Conference on Information Security Curriculum Development – InfoSecCD ’08, 64–66. https://doi.org/10.1145/1456625.1456644
  • Bamigbade, K., & Onifade, O. (2014). Gehe : a Mul Tif Actored Model of Soft and Hard Biometric Trait for Ease of. IEEE.
  • Bolade, P. (2015). Active Telephone Lines In Nigeria Hit 145.4 Million – NCC. Retrieved January 1, 2001, from http://techcabal.com/2015/06/05/active-telephone-lines-in-nigeria-hit-145-4- million-ncc/
  • Breedt, M., & Martin, O. (2004). Using A Central Data Repository For Biometric Authentication In Passport Systems. Issa, (2054024), 1–12. Retrieved from http://dblp.uni- trier.de/db/conf/issa/issa2004.html#Breedt04
  • Charles, W., Patrick, G., & Ramaswamy, C. (2007). SP 800-76-1. Biometric Data Specification for Personal Identity Verification.
WeCreativez WhatsApp Support
Our customer support team is here to answer your questions. Ask us anything!