FINGERPRINT BASED EXAM HALL AUTHANTICATION

Abstract:

Multi-biometric systems are being increasingly deployed in many large-scale biometric

applications because they have several advantages such as lower error rates and larger population
coverage compared to uni-biometric systems.  In this paper propose a fingerprint based
examination hall authentication system. The system is designed to pass only users verified by
their fingerprint scan and block non-verified users. In the examination hall we are use the
fingerprint verification system for verified the authorized user or not. If authorized user then it
allow to the examination hall. Otherwise cannot be allowed.
 CHAPTER I

Introduction:

There are two types of systems that help automatically establish the identity of a person:
1) authentication (verification) systems and 2) identification systems. In a verification system, a
person desired to be identified submits an identity claim to the system, usually via a magnetic
stripe card, login name, smart card, etc., and the system either rejects or accepts the submitted
claim of identity (Am I who I claim I am?). In an identification system, the system establishes a
subject’s identity (or fails if the subject is not enrolled in the system data base) without the
subject’s having to claim an identity (Who am I?).

The topic of this paper is a verification system based on fingerprints, and the terms
verification, authentication, and identification are used in a loose sense and synonymously.
Accurate automatic personal identification is becoming more and more important to the
operation of our increasingly electronically interconnected information society. Traditional
automatic personal identification technologies to verify the identity of a person, which use
“something that you know,” such as a personal identification number (PIN), or “something that
you have,” such as an identification (ID) card, key, etc., are no longer considered reliable enough
to satisfy the security requirements of electronic transactions.

All of these techniques suffer from a common problem of inability to differentiate

between an authorized person and an impostor who fraudulently acquires the access privilege of
the authorized person. Biometrics is a technology that (uniquely) identifies a person based on his
physiological or behavioral characteristics. It relies on “something that you are” to make
personal identification and therefore can inherently differentiate between an authorized person
and a fraudulent impostor. Although biometrics cannot be used to establish an absolute “yes/no”
personal identification like some of the traditional technologies, it can be used to achieve a
“positive identification” with a very high level of confidence, such as an error rate of 0.001%.

In this paper propose a fingerprint based examination hall authentication system. The
system is designed to pass only users verified by their fingerprint scan and block non-verified
users. In the examination hall we are use the fingerprint verification system for verified the
authorized user or not. If authorized user then it allow to the examination hall. Otherwise cannot
be allowed.
 CHAPTER II

SYSTEM DESIGN

Existing System:

In our existing system use the RFID-based authentication system and GSM-GPRS based
authentication system. There are issues with all these device-based solutions. The GSM-GPRS
based systems use the location of Examination hall for Authentication checking.

Drawback:

Problem with RFID based authentication systems is that RFID cards can get lost, stolen,
and it requires the installation of RFID detectors.
RFID cards can also not eliminate impersonation.

Proposed System:

 In this paper propose a fingerprint based examination hall authentication system. The
system is designed to pass only users verified by their fingerprint scan and block non-verified
users. In this system consist of admin and user/Student. At first the student registers our own
details such as fingerprint, name, and details about student…. The admin will check the
authorized user or not by using the fingerprint verification system. If the fingerprint is matched
then it all student to perform examination. Otherwise it is not allowed.

Advantage:

It is accurately check authorized user or not.

It is suitable for large type of application.
 CHAPTER III
SYSTEM REQUIREMENTS
HARDWARE REQUIREMENTS
 Hard Disk : 40 GB
 Processor : Any processor above 500 MHz
 RAM : Above 512 MB
 Input device : Standard Keyboard and Mouse.
 Output device : VGA and High Resolution Monitor.
 Fingerprint device

SOFTWARE REQUIREMENTS
 Operating system : Windows Family
 Front End : Microsoft Visual Studio .NET 2010
 Back End : SQL Server 2005
 Language : DotNet
 CHAPTER IV

SYSTEM IMPLEMENTATION

Modules:

Registration
Fingerprint Verification

Module description:

Registration:

The Student whose are attend the exam at first register the user details like personal
detail, id no, hall ticket no and also set the finger print for authentication.

Finger print verification:

In fingerprint verification the user are put the fingerprint on the fingerprint device. In
fingerprint verification is success then it is a valid user else invalid user. If the valid user then it
allow the user can attend the exam.
 CHAPTER V

SYSTEM DESIGN

Architecture Diagram:

Student Register our details Student Put fingerprint

Verification success then allows

attend Examination

Fingerprint Scanning

Flow Diagram:

Student Register our details

Put the fingerprint

Finger print scanner scans the

fingerprint

No

If success Not allowed to attend exam

Yes

Valid user allow to attend exam

Usecase Diagram:

Register user details

Put fingerprint

Student

Admin
Fingerprint verfication

Sequence Diagram:

Student
Admin

Studen register our examination details with fingerprint to the admin

Admin store into the database

Put the fingerprint

Admin verfy the fingerprint by using the scanner

If verfication is scuess then allow user to perform the examination task

Collaboration Diagram:

2. Admin store into the database

4. Admin verfy the fingerprint by using the scanner
5. If verfication is scuess then allow user to perform the examination task

1. Studen register our examination details with fingerprint to the admin

3. Put the fingerprint
Student Admin

Activity Diagram:

Registration

Put the student fingerprint

No Not Allow to attand the exam

If check valid or
not
Yes
Allow to attand the exam
Statechart Diagram:

Registration

Put the student fingerprint

Allow to attand the exam

Data Flow Diagram:

Verification Put Fingerprint

Student Registration Process

Fingerprint scanner
scans the fingerprint

Valid user then allow to attend

exam
 CHAPTER VI
INPUT AND OUTPUT DESIGN
6.1 INPUT DESIGN
Input facilities the entry of data into the computer system. Input design involves the
selection of the best strategy for getting data into the computer system at the right time and as
accurately as possible. This is because the most difficult aspect of input design in accuracy .The
use of well-defined documents can encourage users to record data accurately without omission.
During design of input, the analyst should decide on the following details:

 What data to input

 What medium to use

 How data should be arranged

 How data should be coded i.e. data representation conventions

The dialogue to guide users in providing input i.e. informative messages that should be
provided when the user is entering data. Like saying, "It is required. Don't leave it blank." Data
items and transactions needing validation to detect errors Methods for performing input
validation and steps to follow when errors occur. The design decisions for handling input specify
how data are accepted for computer processing. The design of inputs also includes specifying the
means by which end-users and system operators direct the system in performing actions.
For example, if the customer makes transaction is the input. This input can process the
withdraw the specific amount from the customer account. For inputting user data, attractive
forms are designed. User can also select desired options from the menu, which provides all
possible facilities.
6.2 OUTPUT DESIGN:
Output refers to the results and information that are generated by the system. In many
cases, output is the main reason for developing the system and the basis on which the usefulness
of the system is evaluated. Most end-users will not actually operate the information system or
enter data through workstations, but they will use the output from the system.

While designing the output of system, the following factors should be considered:

 Determine what information to present

 Decide on the mode of output, i.e. whether to display, print, or "speak" the
information and select the output medium

 Arrange the presentation of information in an acceptable format

 Decide how to distribute the output to intended recipients

Example In our project the output is the processing result of input (The customer get the
output result as the mint statement from the withdrawal input).
 CHAPTER VII
SYSTEM STUDY

FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put forth
with a very general plan for the project and some cost estimates. During system analysis the
feasibility study of the proposed system is to be carried out. This is to ensure that the proposed
system is not a burden to the company. For feasibility analysis, some understanding of the major
requirements for the system is essential.
Three key considerations involved in the feasibility analysis are

 ECONOMICAL FEASIBILITY
 TECHNICAL FEASIBILITY
 SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY

This study is carried out to check the economic impact that the system will have on the
organization. The amount of fund that the company can pour into the research and development
of the system is limited. The expenditures must be justified. Thus the developed system as well
within the budget and this was achieved because most of the technologies used are freely
available. Only the customized products had to be purchased.

TECHNICAL FEASIBILITY
This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the available
technical resources. This will lead to high demands on the available technical resources. This
will lead to high demands being placed on the client. The developed system must have a modest
requirement, as only minimal or null changes are required for implementing this system.
SOCIAL FEASIBILITY

The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system and
to make him familiar with it. His level of confidence must be raised so that he is also able to
make some constructive criticism, which is welcomed, as he is the final user of the system.
 CHAPTER VIII

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.

TYPES OF TESTS
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.

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.

Functional test
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.

Organization and preparation of functional tests is focused on requirements, key functions, or

special test cases. In addition, systematic coverage pertaining to identify Business process flows;
data fields, predefined processes, and successive processes must be considered for testing.
Before functional testing is complete, additional tests are identified and the effective value of
current tests is determined.

System Test
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing is the
configuration oriented system integration test. System testing is based on process descriptions
and flows, emphasizing pre-driven process links and integration points.

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.

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.
Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted as
two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail.

Test objectives

 All field entries must work properly.

 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.
Features to be tested

 Verify that the entries are of the correct format

 No duplicate entries should be allowed
 All links should take the user to the correct page.
Integration Testing
Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by interface
defects.

The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company level –
interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional requirements.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.
 CHAPTER IX

Software Environment

Features Of .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:

1. The Common Language Runtime (CLR).

2. 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 appropriate ways, the runtime also
ensures that code doesn’t attempt to access memory that hasn’t been allocated to it.

Common Language Specification

The CLR provides built-in support for language interoperability. To ensure that you can
develop managed code that can be fully used by developers using any programming language, a
set of language features and rules for using them called the Common Language Specification
(CLS) has been defined. Components that follow these rules and expose only CLS features are
considered CLS-compliant.

THE CLASS LIBRARY

.NET provides a single-rooted hierarchy of classes, containing over 7000 types. The root
of the namespace is called System; this contains basic types like Byte, Double, Boolean, and
String, as well as Object. All objects derive from System. Object. As well as objects, there are
value types. Value types can be allocated on the stack, which can provide useful flexibility.
There are also efficient means of converting value types to object types if and when necessary.

The set of classes is pretty comprehensive, providing collections, file, screen, and
network I/O, threading, and so on, as well as XML and database connectivity.

The class library is subdivided into a number of sets (or namespaces), each
providing distinct areas of functionality, with dependencies between the namespaces kept to a
minimum.

LANGUAGES SUPPORTED BY .NET

The multi-language capability of the .NET Framework and Visual Studio .NET enables
developers to use their existing programming skills to build all types of applications and XML
Web services. The .NET framework supports new versions of Microsoft’s old favorites Visual
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
 Eiffel

Fig1 .Net Framework

ASP.NET Windows Forms

XML WEB SERVICES

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 procedure is available. The sub finalize procedure is used to
complete the tasks that must be performed when an object is destroyed. The sub finalize
procedure is called automatically when an object is destroyed. In addition, the sub finalize
procedure can be called only from the class it belongs to or from derived classes.

GARBAGE COLLECTION

Garbage Collection is another new feature in C#.NET. The .NET Framework monitors
allocated resources, such as objects and variables. In addition, the .NET Framework
automatically releases memory for reuse by destroying objects that are no longer in use.

In C#.NET, the garbage collector checks for the objects that are not currently in use by
applications. When the garbage collector comes across an object that is marked for garbage
collection, it releases the memory occupied by the object.

OVERLOADING

Overloading is another feature in C#. Overloading enables us to define multiple

procedures with the same name, where each procedure has a different set of arguments.
Besides using overloading for procedures, we can use it for constructors and properties in a
class.
 MULTITHREADING:

C#.NET also supports multithreading. An application that supports multithreading

can handle multiple tasks simultaneously, we can use multithreading to decrease the time
taken by an application to respond to user interaction.

STRUCTURED EXCEPTION HANDLING

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

1. To provide a consistent object-oriented programming environment whether object codes is

stored and executed locally on Internet-distributed, or executed remotely.

2. To provide a code-execution environment to minimizes software deployment and

guarantees safe execution of code.

3. Eliminates the performance problems.

There are different types of application, such as Windows-based applications and Web-based
applications.

ASP.NET

Overview ASP.NET

ASP.NET is a technology for creating dynamic Web applications. It is part of

the .NET Framework; you can author ASP.NET applications in any .NET compatible
language, including Visual Basic .NET, C#, and J#. ASP.NET pages (Web Forms) are
compiled, providing better performance than with scripting languages. Web Forms allow you
to build powerful forms-based Web pages. When building these pages, you can use
ASP.NET server controls to create common UI elements, and program them for common
tasks. These controls allow you to rapidly build a Web Form out of reusable built-in or
custom components, simplifying the code of a page.

ASP.NET provides a programming model, and infrastructure, to make creating scalable,

secure and stable applications faster, and easier than with previous Web technologies.

ASP.NET offers several important advantages over previous Web development models:

Enhanced Performance: ASP.NET is compiled common language runtime code running on

the server. Unlike its interpreted predecessors, ASP.NET can take advantage of early
binding, just-in-time compilation, native optimization, and caching services right out of the
box. This amounts to dramatically better performance before you ever write a line of code.

World-Class Tool Support: a rich toolbox and designer in the Visual Studio integrated
development environment complement The ASP.NET framework. WYSIWYG editing, drag-
and-drop server controls, and automatic deployment are just a few of the features this
powerful tool provides.

Power and Flexibility: Because ASP.NET is based on the common language runtime, the
power and flexibility of that entire platform is available to Web application developers.
The .NET Framework class library, Messaging, and Data Access solutions are all seamlessly
accessible from the Web. ASP.NET is also language-independent, so you can choose the
language that best applies to your application or partition your application across many
languages. Further, common language runtime interoperability guarantees that your existing
investment in COM-based development is preserved when migrating to ASP.NET.

Simplicity: ASP.NET makes it easy to perform common tasks, from simple form submission
and client authentication to deployment and site configuration. For example, the ASP.NET
page framework allows you to build user interfaces that cleanly separate application logic
from presentation code and to handle events in a simple, Visual Basic - like forms processing
model. Additionally, the common language runtime simplifies development, with managed
code services such as automatic reference counting and garbage collection.
 Manageability: ASP.NET employs a text-based, hierarchical configuration
system, which simplifies applying settings to your server environment and Web applications.
Because configuration information is stored as plain text, new settings may be applied
without the aid of local administration tools. This "zero local administration" philosophy
extends to deploying ASP.NET Framework applications as well. An ASP.NET Framework
application is deployed to a server simply by copying the necessary files to the server. No
server restart is required, even to deploy or replace running compiled code.

Scalability and Availability: ASP.NET has been designed with scalability in mind, with
features specifically tailored to improve performance in clustered and multiprocessor
environments. Further, processes are closely monitored and managed by the ASP.NET
runtime, so that if one misbehaves (leaks, deadlocks), a new process can be created in its
place, which helps keep your application constantly available to handle requests.

Customizability and Extensibility: ASP.NET delivers a well-factored architecture that allows

developers to "plug-in" their code at the appropriate level. In fact, it is possible to extend or
replace any subcomponent of the ASP.NET runtime with your own custom-written
component. Implementing custom authentication or state services has never been easier.

Security: With built in Windows authentication and per-application configuration, you can
be assured that your applications are secure.

Authentication is the process of accepting credentials from a user and validating those
credentials against a designated authority. The user's (or potentially an application's or
computer's) identity is referred to as a security principal. The client must provide credentials
to allow the server to verify the identity of the principal. After the identity is known, the
application can authorize the principal to access resources on the system.

Authorization is the process of determining whether the proven is allowed to access a

specific resource.

SQL Server 2005:

Microsoft SQL Server is a relational database management system that scales from
laptops and desktops and enterprise servers, with a compatible version, based on the pocket
operating system, available for handheld devise such as pocketPCs and bar-code scanners.
 SQL Server was originally developed in the 1980s at Sybase for UNIX systems and later
ported to Windows NT systems by Microsoft. Since 1994, Microsoft shipped SQL Server
releases developed independently of Sybase, which stopped using the SQL Server name in
the late 1990s. The latest available release is SQL Server 2005, available in personal,
developer, standard, and enterprise edition, localized for many languages around the world.
In this chapter, the term SQL, server refers to all of these editions of SQL Server 2005.
SQL Server provides replications services among multiple copies of SQL. Server as well
as with other database systems. With analysis services, an integral part of the system
includes online analytical processing (OLAP) and data mining facilities. SQL Server
provides a large collection of graphical tools and “wizards” that guides database
administrators through task such as setting up regular backups, replicating data among
servers, and tuning a database for performance. Many development environment support
SQL Server, including Microsoft’s, visual studio, and related products, in particular the .NET
products and services.

Tables

Tables are the database objects that contain all the data in a database. A table definition
is a collection of columns. Each row represents a unique record and each column represents a
field within the record.

Indexes

Indexes in data base are similar to indexes in books in a database; an index allows the
database program to find data in a table without scanning the entire table.

Views

A view is a virtual table whose contents are defined by the query. Stored procedures
Stored procedure in SQL Server is similar to procedure in other programming language like

-They accept input parameter and returns values

-It contains programming statements

Triggers

A trigger is an action which gets fired when some event occur. These are some of the
features of SQL Server 2005.

Structured Query Language

SQL (Structured Query Language) is a database sub language for querying and
modifying relational databases. It was developed by IBM Research in the mid 70's and
standardized by ANSI in 1986.

The Relational Model defines two root languages for accessing a relational database --
Relational Algebra and Relational Calculus. Relational Algebra is a low-level, operator-
oriented language. Creating a query in Relational Algebra involves combining relational
operators using algebraic notation. Relational Calculus is a high-level, declarative language.
Creating a query in Relational Calculus involves describing what results are desired.

SQL is a version of Relational Calculus. The basic structure in SQL is the statement.
Semicolons separate multiple SQL statements.

There are 3 basic categories of SQL Statements:

SQL-Data Statements -- query and modify tables and columns

SELECT Statement -- query tables and views in the database

INSERT Statement -- add rows to tables

UPDATE Statement -- modify columns in table rows

DELETE Statement -- remove rows from tables

SQL-Transaction Statements -- control transactions

COMMIT Statement -- commit the current transaction

ROLLBACK Statement -- roll back the current transaction

 SQL-Schema Statements -- maintain schema (catalog)

CREATE TABLE Statement -- create tables

CREATE VIEW Statement -- create views

DROP TABLE Statement -- drop tables

DROP VIEW Statement -- drop views

GRANT Statement -- grant privileges on tables and views to other users

REVOKE Statement -- revoke privileges on tables and views from other users

Language Structure:

SQL is a keyword-based language. Each statement begins with a unique keyword. SQL
statements consist of clauses that begin with a keyword. SQL syntax is not case sensitive.

The other lexical elements of SQL statements are:

Names: names of database elements: tables, columns, views, users, schemas; names must begin
with a letter (a - z) and may contain digits (0 - 9) and underscore (_)

Literals: quoted strings, numeric values, date time values

Features of SQL-SERVER

The OLAP Services feature available in SQL Server version 7.0 is now called
SQL Server 2005 Analysis Services. The term OLAP Services has been replaced with the term
Analysis Services. Analysis Services also includes a new data mining component. The
Repository component available in SQL Server version 7.0 is now called Microsoft SQL Server
2005 Meta Data Services. References to the component now use the term Meta Data Services.
The term repository is used only in reference to the repository engine within Meta Data Services

SQL-SERVER database consist of six type of objects,

They are,

1. TABLE
 2. QUERY

3. FORM

4. REPORT

5. MACRO

TABLE:

A database is a collection of data about a specific topic.

VIEWS OF TABLE:

We can work with a table in two types,

1. Design View

2. Datasheet View

Design View

To build or modify the structure of a table we work in the table design

view. We can specify what kind of data will be hold.

Datasheet View

To add, edit or analyses the data itself we work in tables datasheet view
mode.

QUERY:

A query is a question that has to be asked the data. Access gathers data that answers the
question from one or more table. The data that make up the answer is either dynaset (if you edit
it) or a snapshot (it cannot be edited).Each time we run query, we get latest information in the
dynaset. Access either displays the dynaset or snapshot for us to view or perform an action on it,
such as deleting or updating.

Future Scope and Further Enhancement:

This system can be used in the company’s internet or intranet environment. Since the
scope of the system is internet, it can be readily used across various other branches spread across
within and outside the country.
Since the system uses latest technology for the development, that is not machine
dependant, does automatic garbage collection and filled with various new generation features,
the product is sure to work on any platform that has the Common Language Runtime
Environment. The System can support heavy workload and is faster then conventional systems
that are developed in the older technologies.
Bibliography

(1) Jeff Weft, Developing Web Applications with Microsoft VisualBasic.NET And Visual
C#. NET, Microsoft, 2003.
(2) Programming C#, Third Edition by Jesse Liberty 2002.
(3) ASP.NET in a Nutshell, Second Edition by G. Andrew Duthie, 2004.
(4) Programming .NET Components by Juval Lowy, 2003.
Programming Microsoft ASP.NET by Dino Esposito

(5) Applied Microsoft .NET Framework Programming by Jeffrey Richter

(6) C# and the .Net Platform by Andrew Troelsen
(7) Microsoft SQL Server 2005 - Programming by Example by carlos Eduardo Fernando
G.Guerrero
(9) http://www.asp.net/

(10) http://www.w3schools.com/
 CHAPTER X

CONCLUSION:

The Exam hall authentication system using fingerprints. The implemented minutiae
extraction is much more accurate and faster than our previous feature-extraction. In our proposed
system accurately verify the fingerprint is valid user or not. If valid user then it allow attending
the exam else not allowed. In our experimental result shows our proposed method is suitable for
all the authentication based application and also it robust.