1

INTRODUCTION

This system is used to create a tool that manages the handling of passport and license using the unique identification associated with each individual. The application deals with allowing the citizens to register for a unique identity. The ID is supported with a pin. Citizens being issued passport or those have a passport is then associated with the UID. This helps the citizen to travel abroad without having the passport. The UID will provide access to the passport from the airport for the airline from the centralized server. The details and profile of the citizen with the photo can be viewed as part of security check.

The crime department can also use the application to trace or stop any person from travelling abroad. The airline gets a notification when the airport staff has access to the citizens passport. The crime department can stop or trace either using the UID or passport number. They could also pass the name of the person and the system can generate a list of photo previews of people having a passport.

The citizen uses the Aadhaar scheme to apply for license. The details of the citizen are picked from the registration database. The citizen is provided with the test details by the application. The details contain the location, date and time information. The test details are provided to the citizen on completion of the test. The license issue and denial is recorded.

Why Aadhar Card is required ? Features of the UIDAI Model

The Aadhaar will only provide identity: The UIDAI's purview will be limited to the issuance of unique identification numbers (Aadhaar) linked to a person's

demographic and biometric information. The Aadhaar will only guarantee identity, not rights, benefits or entitlements.

A pro-poor approach: The UIDAI envisions full enrolment of the residents, with a focus on enrolling India's poor and underprivileged communities. The Registrars that the Authority plans to partner with in its first phase such as the Mahatma Gandhi National Rural Employment Guarantee Scheme (NREGA), Rashtriya Swasthya Bima Yojna (RSBY), and Public Distribution System (PDS) will help bring large number of the poor and underprivileged into the UID system. The UID method of authentication will also improve service delivery for the poor.

Enrolment of residents with proper verification: Existing identity databases in India are fraught with problems of fraud and duplicate/ghost beneficiaries. To prevent this from seeping into the UIDAI database, the Authority plans to enrol residents into its database with proper verification of their demographic and biometric information. This will ensure that the data collected is clean right from the beginning of the program. However, much of the poor and underserved population lack identity documents and the UID may be the first form of identification they will have access to. The Authority will ensure that the Know Your Resident (KYR) standards do not become a barrier for enrolling the poor, and will devise suitable procedures to ensure their inclusion without compromising the integrity of the data.

A partnership model: The UIDAI approach leverages the existing infrastructure of government and private agencies across India. The UIDAI will be the regulatory authority managing a Central ID Repository (CIDR), which will issue Aadhaar, update resident information and authenticate the identity of the residents as required.

In addition, the Authority will partner with agencies such as central and state departments and private sector agencies, who will be 'Registrars' for the UIDAI. Registrars will process Aadhaar applications, and connect to the CIDR to de-duplicate resident information and receive Aadhaar. The Authority will also partner with service providers for authentication of identity.

The UIDAI will emphasize a flexible model for Registrars: The Registrars will ensure significant flexibility in their processes, including issuing cards, pricing, expanding KYR verification, collecting demographic data of residents for their specific requirements, and in authentication. The UIDAI will provide standards to enable Registrars to maintain uniformity in collecting certain demographic and biometric information, and in performing basic KYR activities. These standards will be finalised by the KYR and biometric committees constituted by the Authority.

Process to ensure no duplicates: Registrars will send the applicant's data to the CIDR for de-duplication. The CIDR will perform a search on key demographic fields and on the biometrics for each new enrolment, to minimise/eliminate duplicates in the database.

The incentives in the UIDAI system are aligned towards a self-cleaning mechanism. The existing patchwork of multiple databases in India provides scope to individuals to furnish different personal information to different agencies. Since de-duplication in the UIDAI system ensures that residents have only one chance to be in the database, individuals are made to provide accurate data. This incentive will become especially powerful as benefits and entitlements are linked to Aadhaar.

Online authentication: The Authority will offer a strong form of online authentication, where agencies can compare demographic and biometric information of the resident with the record stored in the central database. The Authority will support Registrars and Agencies in adopting the Aadhaar authentication process, and will help defining the infrastructure and processes they need.

The UIDAI will not share resident data: The Authority envisions a balance between 'privacy and purpose' when it comes to the information it collects on residents. The agencies may store the information of the residents they enrol if they are authorised to do so, but will not have access to the information in the Aadhaar database. The UIDAI will answer all requests to authenticate identity

only through a 'Yes' or 'No' response. The Authority will also enter into contracts with Registrars to ensure the confidentiality of the information they collect and store.

Data Transparency: The authority will place all the aggregated data for public to access under RTI. However Personal Identity Information (PII) will NOT be accessible by any entity.

Technology will undergird the UIDAI system: Technology systems will have a major role across the UIDAI infrastructure. The Aadhaar database will be stored on a central server. Enrolment of the residents will be computerised, and information exchange between Registrars and the CIDR will take place over a network. Authentication of the residents will be online. The Authority will also put systems in place for the security and safety of information. Languages & Technologies:

Our professionals utilize their expertise in the following programming languages, tools and technologies:

Programming Languages: C / C++ VB.NET / C# / ASP.NET PHP,JAVA

Technologies: Win API Win Sockets ActiveX OOP/ OOD COM/ DCOM OpenGL .NET Framework

Database Management Systems: MS Access SQL Server Oracle MYSQL

Web Development

I.T Department offers a wide range of custom IT programming services. We have outstanding experience in custom database development, desktop and distributed application design as well as various custom software components and web-project programming. We take all stages of the software development process seriously. Our primary goal is to meet all out customer needs and requirements as quickly as possible.

We believe that our high quality service provides a sound basis for a successful customer relationship. We consider the testing stage of the product to be one of the most important parts of the development process and we strive to exclude any errors before the product release milestone. Any programming issues discovered within a three-month warranty period will be resolved free of charge. By Web Design, we really mean design!

As a complete web solutions we offer customer-oriented and SEO friendly web design services and more importantly, deliver them effectively. Whether you are a small business or a large corporate, I.T Department can help you achieve an online presence that delivers the very best for you and your clients.

If your goal is to provide information, products, e-commerce or online services, we can ensure that the visitors to your site enjoy an informative, userfriendly and interactive experience. We utilize the skills of designers, experienced specialist programmers, search engine registration specialists and business management experts.

A Professional Approach: With many new and existing businesses wishing to exploit the incredible potential of the Internet, it is important to have a professionally designed and maintained website. Database driven websites and e-commerce solutions Interactive customer communication and service applications Database driven dynamic pages to keep site content up-to-date Intranet development for improved corporate communications and cost savings Online credit card and payment processing Solutions that meet your needs built on either a Linux or Microsoft platform.

Web Development We provide following web design and development solutions: Small Business Web Design HTML Web Design Flash Web Design Attorney Web Design Music Website Design Travel related web design services Hotel website designing CSS Web Design Portal Development Dating/Matrimonial website development Classified website Shopping cart solutions Blog Setup SEO friendly web design Third party software installation, setup, template, customization Website Redesign Website Maintenance services

PROBLEM SELECTION Existing System:

The citizen is identified by multiple identity cards. There is no unique identity in India. Passport has to be carried for travel abroad. Crime department cannot talk to the private airlines to trace or stop travel of a citizen instantly.

Disadvantage of Existing System: The citizen is identified by multiple identity cards. There is no unique identity in India unlike the SSN in the USA. An individual can hold more than one passport. Possibility of passport being lost or damaged. Crime department communicates with the Airport Authority of India physically on stopping or tracing a citizen in travel. License can be applied multiple times, duplication possible, lost or damaged anytime.

Proposed System: A citizen is provided with a UID. The id is associated with a pin number. A physical verification is taken up by the surveyor on whose confirmation the ID is issued. A citizen holding the ID can only apply for passport or license. Based on the type of application the application is forwarded either to the Police department for verification or to the RTA for driving test status. Citizen has an online mode where he can check the status of each application. The crime department integrates with the airlines and identifies citizen who has a conditional travel. Advantage of Proposed System For transaction related to government departments the ID and pin number should be quoted.

The citizen does not have to approach agents for applications. Aadhaar seva centers would facilitate the application processing. The citizen has his application auto-filled when he visits the seva centers. No commission is involved.

The UID doesnt allow duplicate application for any type of card. The citizen can apply the next time only when he fails a verification or test. Address changes easily updated.

System Features 1. Login & Security

The module allows only authorized users to use the application. The application comes with a default administrator account. This account has a user id Admin and password Admin by default. This user can change his password as and when necessary. The administrator maintains Aadhaar seva staffs that are authorized to handle the application and process transactions for the citizen.

2. Citizen Registration

The module allows the citizen to register for unique identity. The citizen provides his personal information, photo to the registration module. The module acknowledges by providing an application number. The citizen uses the application number to then check the status of the unique identity. The administrator is responsible to set the allocation status.

3. Process & Issue Unique Identity

The applications registered by the citizens are viewed by the administrator. When the administrator gets the physical verification report

10

only then he confirms the issue of the unique identity. The module generates unique identification number for each application (citizen). The uid is also associated with a password which can be changed by the citizen.

4. Apply Passport

The module allows the citizen to register application for passport. The module auto fills the application with the information already available in the uid regn database. Only when there is a change of information the citizen should update the uid regn database and then apply for passport. For citizens already having passport and wanted change of information updating the uid regn database automatically updates the passport database.

5. Passport Processing

The module allows the administrator to verify the details of the application, set the status of the passport. If the application is accepted then the administrator provides the passport number and the system automatically updates the date of issue and expiry. This information is now available to the citizen as well as to the airport authority. The passport is a digital passport. The verification of the citizen is done by the crime/police dept.

6. Crime Control

The module allows the crime department to view citizen information either using the uid or the passport number. They can also provide the name of

11

a person and have photos viewed for the citizens having identical names, highly useful when only the name of the person is known. The crime user can also set the status for a passport such as fly or no fly there by intimating the airport authority of flying restrictions for a citizen.

7. License Monitor

The module allows the citizen to apply for passport and have the details and the status of the test. The citizen will not have to submit any physical form nor have agents in between. The aadhaar scheme provides digital form and takes up citizen information from the registration database and dynamically fills the form. The test centers, their location are picked up based upon the pin code the citizen resides at. The RTA provides inputs on test schedules and test results to Aadhaar.

8. Reports

Passport & License Applications Application & Processing Status Fly & No Fly List.

Feasibility Study

The main purpose of feasibility analysis is to check the economic viability of the proposed system. The result of the feasibility study will indicate whether to proceed with the proposed system or not. If the results of the feasibility study are positive, then we can proceed to develop a system otherwise project should not be pursued.

Technical Feasibility

This system will be developed using Asp.net. As we require some time to learn all these technologies, All these technologies are easy to learn and can develop

12

system very rapidly. After developing and deploying the system, any user can view this site on the Internet.

Economical Feasibility

Proposed System requires development tools and software such as visual studio 2008 which are free of cost and available on internet. For developing proposed system, we need various resources such as computers systems, internet connection for e-help, recommended disk space, and memory speed as mention in technical requirement. By looking at all these expenses and comparing with proposed system, we have many benefits from proposed system such are As existing system is manual, where data may not accurate, up to date, and available on time. But proposed system will be computerized, so we can overcome all limitations of existing system. Also with this new system insertion, deletion, and modification of various data will be easier to handle. This system will reduce the paperwork. And quality of data will be improved.

So keeping all above mentioned benefits and comparing with various expenditures of resources, we conclude that proposed system is economical feasible.

Operational feasibility

Users of the system will the registered user of the website. To put an orders user should have only basic knowledge of computer and Internet which is not a big issue. Basic training is required for other users to handle and manage the information.

13

Requirement Validation Username and Password validation that is compulsory to enter within system (Not for visitor). The user must have the email id in Gmail, yahoo or any website. Phone No must be Numeric and length is of maximum 11 Digit. Name must be character not in digit. Pin code No. is of 6 digits. For every new entry of enter all data manually, made entry by adjustment form. So it reduces mismatch in data. The field denoted by (*) are compulsory. Most of the data are enter from the master table so it also reduces the chances of mismatch data.

14

15

Project Monitoring System

Project monitoring is the inevitable dimension of project management that empowers project owners, planners, managers, engineers and other stake holders to visualize various variables of project delivery like progress, cost, resources etc.Project Monitoring Systems(PMS) is the pioneer in the field of Project Monitoring especially visual simulation. Through its extensive research and development, PMS has contributed various innovative project monitoring products and services like 2D/3D visual monitoring, progress drawings, dashboards, enterprise project monitoring, claim analysis and various reports.

Project Monitoring Systems(PMS) is the pioneer in the field of Project Monitoring especially visual simulation. Through its extensive research and development, PMS has contributed various innovative project monitoring products and services like 2D/3D visual monitoring, progress drawings, dashboards, enterprise project monitoring, claim analysis and various reports. PMS is equipped with various solutions for planning and monitoring phases.

Project Management Dashboard(PMDB) provides a single dashboard to visually analyze the various project metrics like performance curves, Cost performance index, Schedule performance Index, Variation profile etc. PMDB generates various types of tabular and graphical reports which can be standard or customized.Variation profile is key differentiator of PMDB. Variation profile is the graphical representation of the various changes made to the schedule which is a major concern of the management.

Some typical changes are:

Activities that have been added or deleted Adding or deleting resources Added, deleted or changed relationships Changes to original and remaining durations

16

Changes to constraint types, percents complete, total and free floats Changes to descriptions Changes to activity logs Changes to actual starts and finishes Changes to activity codes and WBS changes etc. Changes to resource percents etc.

Modules were designed and implemented for planning & scheduling in Primavera software which will assist planners to plan their projects much faster and accurate than ever before.

Our Solutions for progress monitoring are fully or semi-automatic.Site progress reported by an engineer will update in QS section which is linked to the planning system- Primavera. This will enable the automatic progress calculation of Primavera activities.

Or in other words, a planner will get alerted the progress of activities in his system so that he can concentrate on his job rather than collecting information from others to update activities.

For example, company resource groups for different activities are coded to retrieve the resources in primavera based on the productivity and the quantity of the activity to perform. This will enable automatic loading of the resources on activities which will save lot of time with greater accuracy at the planning stage.

Office Engineering:

One of the major research and development areas of PMS is the enhancement of office engineering systems like, drawing, designing, analysis, calculations, etc., Custom made solutions based on customer need is the approach of PMS, which has a great advantage that employees need not to change their systems..

Example : CAD Enhancements/Automation in drawing generation

17

PMS has many implementations in various enhancement of CAD application. Following is a screen shot of a pipeline profile generator based on survey levels and design levels. Improvement in the productivity is observed is about 10 times more than the conventional method.

2D & 3D Visual Monitoring Systems:

It generates 3D project progress visualization for project stake holders like contractors and property owners. Using state of the art technology, Consim produces 3D simulations of planned and actual project progress for any day thereby giving user instant comprehension of the pace of the project.

General Features:

Target Visualize the project in various planning stages. GPA enables the team members to understand the sequence of activities in different areas. GPA can be used to validate the logic of the sequence.

Current Visualize the current status of the project illustrating the activities in different color codes based on their progress status i.e. completed, pending, delayed or progressing. Regular GPA users will be more aware of the project performance at the activity level than the Non-GPA users who stick to the conventional reports.

Past Visualize the As-built project status for any past date. Past project status generated by GPA can be used to explain claim related issues. New project members can use them to understand the project execution till the current date.

18

Future Visualize the Look-Ahead status for any future date with respect to the current pace of the project. GPA highlights the critical activities thereby enabling the users to focus on them and take the necessary acceleration measures.

Office Engineering:

One of the major research and development areas of PMS is the enhancement of office engineering systems like, drawing, designing, analysis, calculations, etc., Custom made solutions based on customer need is the approach of PMS, which has a great advantage that employees need not to change their systems..

Example : CAD Enhancements/Automation in drawing generation PMS has many implementations in various enhancement of CAD application. Following is a screen shot of a pipeline profile generator based on survey levels and design levels. Improvement in the productivity is observed is about 10 times more than the conventional method.

Brief History of Visual Basic.NET

Visual Basic was invented by Microsoft, but it's based on a much earlier language called BASIC invented by Dartmouth College professors John G. Kemeny and Thomas E. Kurtz in 1964. Since C was invented almost ten years later, BASIC is one of the earliest computer languages. Every version of BASIC has been a revolutionary event in the history of programming from the very beginning. In fact, the version of BASIC created by Microsoft founders Bill Gates and Paul Allen in February 1975 has an excellent claim to being the very first PC language since the first version was written in the native machine language for the what many consider to be the first PC, the MITS Altair 8800. Since the first PC version was written directly in machine language, nothing came before it.

19

Visual Basic (VB), formerly called Visual Basic .NET (VB.NET), is an objectoriented computer language that can be viewed as an evolution of Microsoft's Visual Basic (VB) implemented on the Microsoft .NET framework.

The first version of Visual Basic came out in May of 1991. It was revolutionary because it gave people the ability to create Windows programs easily and quickly for the first time. Before Visual Basic, Windows programs were usually written using the complicated syntax of C++ and the even more complicated requirements of Windows. It was a tricky job for even the most experienced programmers.

But Visual Basic opened Windows programming for everyone. That made it a key part of the amazing early success of Windows. During this era IBM and OS/2 had nearly all the money, most of the customers, and they made the computers. They had it all; Microsoft was a tiny, insignificant upstart by comparison.

The programming universe was literally turned upside down when Windows and Visual Basic became the most successful software system in the world. But Microsoft has never been a company that let history happen to them. They have always made their own history. In February 2002, Microsoft made a 300 billion dollar bet on a totally new technology base for their entire company. They called it .NET. Bill Gates, who usually says what he means, called .NET a "bet the company" move. If .NET had flopped, it probably would have been all over for Microsoft.

Visual Basic has always been a flagship language for Microsoft and this didn't change when .NET came out. Visual Basic remained a featured language for Microsoft development in the new .NET world.

There is also a .NET version of C++, but it's there mainly because a lot of companies put a lot of investment into early Windows software development in C++. It's just too much money to walk away from and it would be too difficult to recode all of it. There was a lot of pressure for Microsoft to provide a .NET version. Because the .NET Framework does most of the work, Visual Basic, and every other .NET language, is just the skin on top of .NET. Once we learn .NET ... switching to another language syntax is a lot easier. The really important things don't change.

20

There are getting to be quite a few .NET languages available now! Microsoft lists all these at their site: COBOL for Microsoft .NET. Perl for Microsoft .NET. Eiffel for Microsoft .NET. Python for Microsoft .NET. Pascal for Microsoft .NET. Mercury for Microsoft .NET. Mondrian for Microsoft .NET. Oberon for Microsoft .NET. Salford FTN95 (Fortran) for Microsoft .NET. SmallTalk for Microsoft .NET. Standard ML for Microsoft .NET. Language Used

I'll be using VB.NET for my project. Visual Basic.NET is one of the languages that are directed towards meeting the objectives of the .NET initiated of creating distributed applications. It has inherited the capability of rapid application development from its earlier versions and strengthened considerably the implementation of object oriented features. Visual Basic.NET is a powerful object oriented language that provides features such as abstraction, encapsulation, inheritance and polymorphism.

In addition, it provides many other features that did not exist in the earlier version, such as multithreading and structured exception handling. Some of the key features introduced in Visual Basic.NET are as follows: Inheritance, Constructors and destructors, Overloading Overriding, Structured exception handling, Multithreading.

VS.NET IDE (Integrated Development Environment) is the same for all of the .NET languages too. In fact, Visual Basic .NET, Visual C++ .NET, Visual C# .NET, and Visual J# .NET all use the same VS.NET IDE.

21

We don't need to buy any software for this project! We can use the new FREE Visual Basic Express Edition from Microsoft. We can download it. The download is quite large, but Microsoft allows us to order it on CD. We requires XP or greater. Microsoft has made it as easy as they can for us to learn Visual Basic .NET by giving away a really great development system absolutely free: Visual Basic .NET 2008 Express Edition. (The download link is

http://www.microsoft.com/express/download/default.aspx Visual Basic Express is Microsoft's free, downloadable version of Visual Basic designed to get us all hooked on the product. However we do have to register with Microsoft and obtain their Windows Live ID.

VB Express is a first class development system with many of the features of the one that Microsoft sells for thousands of US dollars. I took advantage of Microsoft and use VB.NET 2008 Express.

Visual Basic has two distinct environments, a Design environment and a Debug environment. Design Time is where we get to play about with the form, spruce it up, add textboxes, buttons, labels and code. Debug is where we can test our programme and see how well it performs. Things like buttons, textboxes, and labels are all things that we can add to our Forms. They are know as Controls, and are kept in the Toolbox for ease of use. The Toolbox can be found on the left of the screen. There are seven categories of tools available.

There are an awful lot of tools to choose from! I covered in this project how to write a program, the basics of language syntax and structure, and how to use the version of Visual Studio .NET that Visual Basic Express uses.

What is an ASP.NET File? An ASP.NET file is just the same as an HTML file An ASP.NET file can contain HTML, XML, and scripts Scripts in an ASP.NET file are executed on the server An ASP.NET file has the file extension ".aspx"

22

The Microsoft .NET Framework The .NET Framework is the infrastructure for the Microsoft .NET platform. The .NET Framework is an environment for building, deploying, and running Web applications and Web Services. Microsoft's first server technology ASP (Active Server Pages), was a powerful and flexible "programming language". But it was too code oriented. It was not an application framework and not an enterprise development tool.

The Microsoft .NET Framework was developed to solve this problem. .NET Frameworks keywords: Easier and quicker programming Reduced amount of code Declarative programming model Richer server control hierarchy with events Larger class library Better support for development tools The .NET Framework consists of 3 main parts: Programming languages: C# (Pronounced C sharp) Visual Basic (VB .NET) J# (Pronounced J sharp) Server technologies and client technologies: ASP .NET (Active Server Pages) Windows Forms (Windows desktop solutions) Compact Framework (PDA / Mobile solutions) Development environments: Visual Studio .NET (VS .NET) Visual Web Developer

New in ASP.NET Better language support Programmable controls Event-driven programming XML-based components

23

User authentication, with accounts and roles Higher scalability Increased performance - Compiled code Easier configuration and deployment Not fully ASP compatible

Language Support ASP.NET uses ADO.NET. ASP.NET supports full Visual Basic, not VBScript. ASP.NET supports C# (C sharp) and C++. ASP.NET supports JScript.

C Sharp C# (pronounced "see sharp") is a multi-paradigm programming language encompassing imperative, functional, generic, object-oriented (class-based), and component-oriented programming disciplines. It was developed by Microsoft within the .NET initiative and later approved as a standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270). C# is one of the programming languages designed for the Common Language Infrastructure.C# is intended to be a simple, modern, general-purpose, object-oriented programming language[6]. Its development team is led by Anders Hejlsberg. The most recent version is C# 3.0, which was released in conjunction with the .NET Framework 3.5 in 2007. The next proposed version, 4.0, is in development.

Features By design, C# is the programming language that most directly reflects the underlying Common Language Infrastructure (CLI). Most of its intrinsic types correspond to value-types implemented by the CLI framework. However, the language specification does not state the code generation requirements of the compiler: that is, it does not state that a C# compiler must target a Common Language Runtime, or generate Common Intermediate Language (CIL), or generate any other specific format. Theoretically, a C# compiler could generate machine code like traditional compilers of C++ or FORTRAN.

24

Some notable distinguishing features of C# are: There are no global variables or functions. All methods and members must be declared within classes. Static members of public classes can substitute for global variables and functions.

Local variables cannot shadow variables of the enclosing block, unlike C and C++. Variable shadowing is often considered confusing by C++ texts.

C# supports a strict Boolean datatype, bool. Statements that take conditions, such as while and if, require an expression of a type that implements the true operator, such as the boolean type. While C++ also has a boolean type, it can be freely converted to and from integers, and expressions such as if(a) require only that a is convertible to bool, allowing a to be an int, or a pointer.

C# disallows this "integer meaning true or false" approach on the grounds that forcing programmers to use expressions that return exactly bool can prevent certain types of common programming mistakes in C or C++ such as if (a = b) (use of assignment = instead of equality ==).

In C#, memory address pointers can only be used within blocks specifically marked as unsafe, and programs with unsafe code need appropriate permissions to run. Most object access is done through safe object references, which always either point to a "live" object or have the well-defined null value; it is impossible to obtain a reference to a "dead" object (one which has been garbage collected), or to a random block of memory.

An unsafe pointer can point to an instance of a value-type, array, string, or a block of memory allocated on a stack. Code that is not marked as unsafe can still store and manipulate pointers through the System.IntPtr type, but it cannot dereference them.

Managed memory cannot be explicitly freed; instead, it is automatically garbage collected. Garbage collection addresses the problem of memory leaks by

25

freeing the programmer of responsibility for releasing memory which is no longer needed.

In addition to the try...catch construct to handle exceptions, C# has a try...finally construct to guarantee execution of the code in the finally block.

Multiple inheritance is not supported, although a class can implement any number of interfaces. This was a design decision by the language's lead architect to avoid complication and simplify architectural requirements throughout CLI.

C# is more type safe than C++. The only implicit conversions by default are those which are considered safe, such as widening of integers. This is enforced at compile-time, during JIT, and, in some cases, at runtime. There are no implicit conversions between booleans and integers, nor between enumeration members and integers (except for literal 0, which can be implicitly converted to any enumerated type). Any user-defined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors and conversion operators, which are both implicit by default. Enumeration members are placed in their own scope.

C# provides properties as syntactic sugar for a common pattern in which a pair of methods, accessor (getter) and mutator (setter) encapsulate operations on a single attribute of a class. Full type reflection and discovery is available

26

Fig 1

Implementations The reference C# compiler is Microsoft Visual C#. Other C# compilers exist, often including an implementation of the Common Language Infrastructure and the .NET class libraries up to .NET 2.0: Microsoft's Rotor project (currently called Shared Source Common Language Infrastructure) (licensed for educational and research use only) provides a shared source implementation of the CLR runtime and a C# compiler, and a subset of the required Common Language Infrastructure framework libraries in the ECMA specification (up to C# 2.0, and supported on Windows XP only). The Mono project provides an open source C# compiler, a complete open 1source implementation of the Common Language Infrastructure including the required framework libraries as they appear in the ECMA specification, and a nearly complete implementation of the Microsoft proprietary .NET class libraries up to .NET 2.0, but not specific .NET 3.0 and .NET 3.5 libraries, as of Mono 2.0.

The DotGNU project also provides an open source C# compiler, a nearly complete implementation of the Common Language Infrastructure including the required framework libraries as they appear in the ECMA specification, and subset of some of the remaining Microsoft proprietary .NET class libraries up to .NET 2.0 (those not

27

documented or included in the ECMA specification but included in Microsoft's standard .NET Framework distribution). The DotNetAnywhere Micro Framework-like Common Language Runtime is targeted at embedded systems, and supports almost all C# 2.0 specifications.

SQL (Structured Query Language) SQL often referred to as Structured Query Language[2][3]) is a database computer language designed for managing data in relational database management systems (RDBMS), and originally based upon Relational Algebra. Its scope includes data query and update, schema creation and modification, and data access control. SQL was one of the first languages for Edgar F. Codd's relational model in his influential 1970 paper, "A Relational Model of Data for Large Shared Data Banks" [4] and became the most widely used language for relational databases.

Language Elements The SQL language is sub-divided into several language elements, including: Clauses, which are in some cases optional, constituent components of statements and queries.[9] Expressions which can produce either scalar values or tables consisting of columns and rows of data.

Predicates which specify conditions that can be evaluated to SQL three-valued logic (3VL) Boolean truth values and which are used to limit the effects of statements and queries, or to change program flow.

Queries which retrieve data based on specific criteria. Statements which may have a persistent effect on schemas and data, or which may control transactions, program flow, connections, sessions, or diagnostics.

SQL statements also include the semicolon (";") statement terminator. Though not required on every platform, it is defined as a standard part of the SQL grammar. Insignificant whitespace is generally ignored in SQL statements and queries, making it easier to format SQL code for readability.

28

Fig 2

Principal Design Features Interoperability: Because interaction between new and older applications is commonly required, the .NET Framework 2.0 provides means to access functionality that is implemented in programs that execute outside the .NET environment. Access to COM components is provided in the System.Runtime.InteropServices and System.EnterpriseServices namespaces of the framework; access to other functionality is provided using the P/Invoke feature.

Common Runtime Engine : Programming languages on the .NET Framework compile into an intermediate language known as the Common Intermediate Language (CIL). In Microsoft's implementation this intermediate language is not interpreted but rather compiled in a manner known as just-in-time compilation (JIT) into native code. The combination of these concepts is called the Common

29

Language Infrastructure (CLI). Microsoft's implementation of the CLI is known as the Common Language Runtime (CLR).

Language Independence The .NET Framework introduces a Common Type System, or CTS. The CTS specification defines all possible datatypes and programming constructs supported by the CLR and how they may or may not interact with each other. Because of this feature, the .NET Framework supports the exchange of instances of types between programs written in any of the .NET languages. This is discussed in more detail in Microsoft .NET Languages.

Base Class Library The Base Class Library (BCL), part of the Framework Class Library (FCL), is a library of functionality available to all languages using the .NET Framework. The BCL provides classes which encapsulate a number of common functions, including file reading and writing, graphic rendering, database interaction and XML document manipulation.

Assemblies The intermediate CLI code is housed in .NET assemblies. As mandated by specification, assemblies are stored in the Portable Executable (PE) format, common on the Windows platform for all DLL and EXE files.

30

Features Of Dot Net Framework

Interoperability: The ability of two or more systems or components to exchange information and to use the information that has been exchanged.

Common Language Runtime:

The Common Language Runtime (CLR) is the

virtual machine component of the .NET framework. All .NET programs execute under the supervision of the CLR, guaranteeing certain properties and behaviors in the areas of memory management, security, and exception handling.

Security: NET provides a common security model for all applications

Basics Of Dot Net

Data adapter It is always used in disconnected approach implement to open the connection & close the connection

31

Data set Created in application memory. Dataset is collection of tables.

Data reader It is used to display data read only,forward only. It is fastest way to read retrieve data from database.

Data table It is used to create temporary table.

Queries The most common operation in SQL is the query, which is performed with the declarative SELECT statement. SELECT retrieves data from one or more tables, or expressions. Standard SELECT statements have no persistent effects on the database. Some non-standard implementations of SELECT can have persistent effects, such as the SELECT INTO syntax that exists in some databases. Queries allow the user to describe desired data, leaving the database management system (DBMS) responsible for planning, optimizing, and performing the physical operations necessary to produce that result as it chooses. A query includes a list of columns to be included in the final result immediately following the SELECT keyword. An asterisk ("*") can also be used to specify that the query should return all columns of the queried tables. SELECT is the most complex statement in SQL, with optional keywords and clauses that include: The FROM clause which indicates the table(s) from which data is to be retrieved. The FROM clause can include optional JOIN subclauses to specify the rules for joining tables. The WHERE clause includes a comparison predicate, which restricts the rows returned by the query. The WHERE clause eliminates all rows from the result set for which the comparison predicate does not evaluate to True.

The GROUP BY clause is used to project rows having common values into a smaller set of rows. GROUP BY is often used in conjunction with SQL aggregation

32

functions or to eliminate duplicate rows from a result set. The WHERE clause is applied before the GROUP BY clause. The HAVING clause includes a predicate used to filter rows resulting from the GROUP BY clause. Because it acts on the results of the GROUP BY clause, aggregation functions can be used in the HAVING clause predicate.

The ORDER BY clause identifies which columns are used to sort the resulting data, and in which direction they should be sorted (options are ascending or descending). Without an ORDER BY clause, the order of rows returned by an SQL query is undefined.

The following is an example of a SELECT query that returns a list of expensive books. The query retrieves all rows from the Book table in which the price column contains a value greater than 100.00. The result is sorted in ascending order by title. The asterisk (*) in the select list indicates that all columns of the Book table should be included in the result set.

Data types Each column in an SQL table declares the type(s) that column may contain. ANSI SQL includes the following datatypes.

Character strings CHARACTER(n) or CHAR(n) fixed-width n-character string, padded with spaces as needed CHARACTER VARYING(n) or VARCHAR(n) variable-width string with a maximum size of n characters NATIONAL CHARACTER(n) or NCHAR(n) fixed width string supporting an international character set NATIONAL CHARACTER VARYING(n) or NVARCHAR(n) variable-width NCHAR string

33

Bit strings BIT(n) an array of n bits BIT VARYING(n) an array of up to n bits Numbers INTEGER and SMALLINT FLOAT, REAL and DOUBLE PRECISION NUMERIC(precision, scale) or DECIMAL(precision, scale) SQL provides a function to round numerics or dates, called TRUNC (in DB2, PostgreSQL, Oracle and MySQL) or ROUND (in Sybase, Oracle and Microsoft SQL Server)

Date and Time DATE TIME TIMESTAMP INTERVAL

Data control The Data Control Language (DCL) authorizes users and groups of users to access and manipulate data. Its two main statements are: GRANT authorizes one or more users to perform an operation or a set of operations on an object. REVOKE eliminates a grant, which may be the default grant.

34

35

System Study
The spiral model combines the idea of (prototyping) with the systematic, controlled aspects of the under control. At each iteration around the cycle, the products are extensions of an earlier product. This model uses many of the same phases as the waterfall model, in essentially the same order, separated by planning, risk assessment, and the building of prototypes and simulations

Documents are produced when they are required, and the content reflects the information necessary at that point in the process. All documents will not be created at the beginning of the process, nor all at the end (hopefully). Like the product they define, the documents are works in progress. The idea is to have a continuous stream of products produced and available for user review.

The spiral lifecycle model allows for elements of the product to be added in when they become available or known. This assures that there is no conflict with previous requirements and design. This method is consistent with approaches that have multiple software builds and releases and allows for making an orderly transition to a maintenance activity. Another positive aspect is that the spiral model forces early user involvement in the system development effort. For projects with heavy user interfacing, such as user application programs or instrument interface applications, such involvement is helpful. Determine the objectives, alternatives, and constraints on the new iteration. Evaluate alternatives and identify and resolve risk issues. Develop and verify the product for this iteration. Plan the next iteration.

Note that the requirements activity takes place in multiple sections and in multiple iterations, just as planning and risk analysis occur in multiple places. Final design, implementation, integration, and test occur in iteration 4. The spiral can be repeated multiple times for multiple builds. Using this method of development, some functionality can be delivered to the user faster than the

36

waterfall method. The spiral method also helps manage risk and uncertainty by allowing multiple decision points and by explicitly admitting that all of anything cannot be known before the subsequent activity starts

The Waterfall model is mostly used in large projects

Fig 3 The methodology to be used to complete the project will cover many steps. Basically it will be a step by step process to move toward the solution for the Web Portal. Following points give a concise description of the methodology which will be adopted. First phase would be to study the system in place which needs to be automated. In Second phase using automated tools and standards software for the client requirement data will be gathered. In Third phase, the solution designing will be done using software engineering tools. In Fourth phase, the .NET framework and other languages like Visual Basic.NET etc will be used for coding the software. Also the coding will

37

use different coding style to increase its readability and maintainability properties. In Fifth phase, the coded software will be tested using test cases. The test cases will include cases where there is a chance of exception generation. After this the clients data will be used to test the software. Finally, the help will be prepared so that user can independently use the software.

Maintenance Phase of SDLC:

Fig 4

38

INTEGRATION AND MAINTANENCE:

The Systems Development Life Cycle (SDLC) phases serve as a programmatic guide to project activity and provide a flexible but consistent way to conduct projects to a depth matching the scope of the project. Each of the SDLC phase objectives are described in this section with key deliverables, a description of recommended tasks, and a summary of related control objectives for effective management.

It is critical for the project manager to establish and monitor control objectives during each SDLC phase while executing projects. Control objectives help to provide a clear statement of the desired result or purpose and should be used throughout the entire SDLC process. Control objectives can be grouped into major categories (Domains), and relate to the SDLC phases

To manage and control any SDLC initiative, each project will be required to establish some degree of a Work Breakdown Structure (WBS) to capture and schedule the work necessary to complete the project. The WBS and all programmatic material should be kept in the Project Description section of the project notebook.

The WBS format is mostly left to the project manager to establish in a way that best describes the project work. There are some key areas that must be defined in the WBS as part of the SDLC policy. The following diagram describes three key areas that will be addressed in the WBS in a manner established by the project manager.

Maintenance includes all the activity after the installation of software that is performed to keep the system operational. As we have mentioned earlier, software often has design faults. The two major forms of maintenance activities are adaptive maintenance and corrective maintenance.

It is generally agreed that for large systems, removing all the faults before delivery is extremely difficult and faults will be discovered long after the system is

39

installed. As these faults are detected, they have to be removed. Maintenance activities related to fixing of errors fall under corrective maintenance.

Removing errors is one of the activities of maintenance. Maintenance also needed due to a change in the environment or the requirements of the system. The introduction of a software system affects the work environment. This change in environment often changes what is desired from the system.

Furthermore, often after the system is installed and the users have had a chance to work with it for some time, requirements that are not identified during requirement analysis phase will be uncovered. This occurs, since the experience with the software helps the user to define the needs more precisely. There might also be changes in the input data, the system environment and output formats. All these require modification of the software. The maintenance activities related to such modification fall under adaptive maintenance.

Maintenance work is based on existing software, as compared to development work, which creates new software. Consequently maintenance resolves around understanding the existing software and spares most of their time trying to understand the software that they have to modify.

Understanding the software involves not only understanding the code, but also the related documents. During the modification of the software, the effects of the change have to be clearly understood by the maintainer since introducing undesired side effects in the system during modification is easier.

To test whether those aspects in the system that are not supposed to be modified are operating as they were before modification, regression testing is done. Regression testing involves executing old test cases to test that no new errors have been introduced.

Thus, maintenance involves understanding the existing software (code and related documents), understanding the effects of change, making the changes - both

40

to the code and documents, testing the new parts (changes), and resetting of the old parts that were not changed.

Since often during development, needs of the maintainers are not kept in mind, little support documents are produced during development to aid the maintainer. The complexity of the maintenance task is coupled with the neglect of maintenance concerns during development which makes maintenance the most cost effective activity in the life of a software product.

System requirements/used: Server Requirement: Production server Database Server 64 GB RAM Quartz 16 Processor 1TB Hard Disk Server Model- Blade4

Software Requirement: Windows server 2003 or above IIS-6.0 or above .net Framework-3.5 or above MS SQL Server 2008

Devolpment Enviornment: Visual studio 2008 with service pack 1 and sql 2008 Database Server Hardware Requirement: 1TB or more than Hard Disk Quartz 16 Processor 64 GB RAM

41

42

SYSTEM ANALYSIS
System Analysis is the process of gathering and interpreting facts, diagnosing problems and using the information to recommended improvements to the System. This is the System Analysis.

System Analysis does more than to solve current problems. They are frequently called upon to help and handle the planned expansion of a business. Basically the analysis specifies what the system should be. Design states that how to accomplish the objective.

So in our case the old manual system was not in a position to provide any information in time. A lot of effort has to be exercised to provide any information available to the administration 0or customers. There was an immediate need for new computerized system therefore the following detailed investigation was made about:-

How and in what format the department maintained data in forms of ledgers and files? What reports did the administration and customers require? What were the major drawbacks responsible for poor functioning of the old system? After going through the outcomes of the above findings and further studying the limitations finally it was decided to have the new computerized loan-handling system eliminates completely the drawbacks existing in the old system.

INTRODUCTION

System analysis is the process of studying the business processors and procedures, generally referred to as business systems, to see how they can operate and whether improvement is needed. This may involve examining data movement and storage, machines and technology used in the system, programs that control

43

the machines, people providing inputs, doing the processing and receiving the outputs.

INVESTIGATION PHASE

The investigation phase is also known as the fact-finding stage or the analysis of the current system. This is a detailed study conducted with the purpose of wanting to fully understand the existing system and to identify the basic information requirements. Various techniques may be used in fact-finding and all fact obtained must be recorded. A thorough investigation was done in every effected aspect when determining whether the purposed system is feasible enough to be implemented. As it was essential for us to find out more about the present system, we used the following methods to gather the information:

Observation Necessary to see the way the system works first hand.

Document sampling: These are all the documents that are used in the They are necessary to check all the data that enters and leaves the system.

system.

Questionnaires: These were conducted to get views of the other employees who are currently employed in the system.

CONSTRAINTS AND LIMITATIONS The constraints and limitation within a system are the drawbacks that occur during the implementation of the system. These limitations and constraints can crop up in almost every system; the most important fact is to find a way to overcome these problems. Software design is the first of three technical activities design, code generation, and test that are required to build and verify the software. Each activity transforms information in manner that ultimately results in validated computer software. The design task produces a data design, an architectural design, an interface design and component design.

44

The design of an information system produces the details that clearly describe how a system will meet the requirements identified during system analysis. The system design process is not a step by step adherence of clear procedures and guidelines. When I started working on system design, I face different types of problems; many of these are due to constraints imposed by the user or limitations of hardware and software available.

Some times it was quite difficult to enumerate that complexity of the problems and solutions thereof since the variety of likely problems is so great and no solutions are exactly similar however the following consideration I kept in mind during design phased.

DESIGN: The primary objective of the design is to deliver the requirements as specified in the feasibility report. These are the some of the objectives, which I kept in mind.

Practicality: The system is quite stable and can be operated by the people with average intelligence. Efficiency: I tried to involve accuracy, timeliness and comprehensiveness of the system output. Cost: It is desirable to aim for the system with a minimum cost subject to the condition that it must satisfy the entire requirement. Flexibility: I have tried that the system should be modifiable depending on the changing needs of the user. Such modifications should entail extensive reconstructing or recreation of software. It should also be portable to different computer systems. Security: This is very important aspect which I followed in this designing phase and tried to covers the areas of hardware reliability, fallback procedures, and physical security of data.

DATA DICTIONARY: In our DFD, we give names to data flows, processes, and data stores. Although the names are descriptive of the data, they do not give details. So the following the DFD, our interest is to build some structured place to keep details of the contents of

45

data flow, processes, and data store. A data dictionary is a structured repository of data about data. It is a set of rigorous definition of all DFD data element and data structure.

A data dictionary has many advantages. The most obvious is documentation; it is valuable reference in any organization. Another advantage is improving analyst/user communication by establishing consistent definition of various elements, terms and procedures. During implementation, it serves as a common base against which programmers who are working on the system compare data description.

Also control information maintained for each data element is cross referenced in the data dictionary. E.g. program that use a given data element are cross referenced in a data dictionary, which makes it easy to identify them and make any necessary changes. Finally, a data dictionary is an important step in building a database. Most database management system has a data dictionary as a standard feature

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. DFDs can also be used for the visualization of data processing (structured design). On a DFD, data items flow from an external data source or an internal data store to an internal data store or an external data sink, via an internal process.

A DFD provides no information about the timing of processes, or about whether processes will operate in sequence or in parallel. It is therefore quite different from a flowchart, which shows the flow of control through an algorithm, allowing a reader to determine what operations will be performed, in what order, and under what circumstances, but not what kinds of data will be input to and output from the system, nor where the data will come from and go to, nor where the data will be stored (all of which are shown on a DFD).

46

47

SYSTEM DESIGN
INTRODUCTION System design is the process of developing specifications for a candidate system that meet the criteria established in the system analysis. Major step in system design is the preparation of the input forms and the output reports in a form applicable to the user. The main objective of the system design is to make the system user friendly.

System design involves various stages as: System design is the creative act of invention, developing new inputs, a database, offline files, procedures and output for processing business to meet an organization objective. System design builds information gathered during the system analysis. Data Entry Data Correction Data Deletion Processing Sorting and Indexing Report Generation

CHARACTERSTICS OF A WELL DEFINED SYSTEM In design an efficient and effective system is of great importance to consider the human factor and equipment that these will require to use. System analyst must evaluate the capabilities and limitations of the personal and corresponding factors of the equipment itself. The characteristics associated with effective system operations are: Accessibility Decision Making Ability Economy Flexibility Reliability Simplicity

48

Success is a new system pivots on its acceptance or non-acceptance by the organization.

Personnel: If the operating system is convinced that the new system will not benefit them, it appears one, and the system is in serious trouble. To overcome this resistance participation by operating personal during all phases of the changeover is necessary because they constitute the organization, which must use alive in with newly design system. An effective system produces not only information at the lowest cost pertinent and timely for making decision.

DATABASE DESIGN: The overall objective in the development of the database technology has been to treat data as an organizational resource and as an integrated whole. Database management system allows data to be protected and organize separately from other resources. Database is an integrated collection of data. The most significant of data as seen by the programs and data as stored on the direct storage access storage devices. This is the difference between logical and physical data. The organization of data in the database aims to achieve free major objectives: Data Integration Data Integrity Data Independence The databases are implemented using a DBMS package. Each particular DBMS has unique characteristics and general techniques for Database Design. The proposed Management Information System stores the information relevant for processing in the Microsoft SQL Server Database. This MS SQL Server contains tables, where each table is called a field or column. A table also contains records which is a set of fields. All records, in a table the same set of fields with different information. Each table contains key fields that establish relationships in a MS SQL server database and how the records are stored. There are primary key fields that uniquely identify a record in a table. There are also fields that contain the primary key from another table called foreign keys.

49

It is a known fact that the program cannot be written until the data are defined, so the database must be defined. The starting point for this process is data dictionary. The records data structures and elements to be stored in each database are identified and extracted. Next the analyst codes the source statements library

Eventually, the programmer will incorporate the source code into the various programs, thus assuring consistency and simplifying the coding process. The databases have been designed in such a way that there is no duplication of information and loss of information.

SCHEMA DESIGN: INTRODUCTION: In database design, several views of data must be considered along with the persons who use them. In addition to data structuring, where relationships are reflected between and within entities, we need to identify the application programs logical views of data within an overall logical data structure. The logical view is what the data look like, regardless of how they are stored. The physical view is the way data exist in physical storage. It deals with hoe data are stored, accessed, or related to other data in storage. The schema is the view that helps the DBMS decide in storage act upon as requested by the application program.

RELATIONAL MODEL: Certain rules followed in creating and relating databases in the relational databases. This governs how to relate data and prevent redundancy of the data in the databases. The first set of rules called relational rules ensures that the database is a relational database.The second set called the normalization rules simplifies the database and reduce the redundancy of the data. Proposed system this relational database rules are applied to reduce the redundancy make future changes to the table structure easier to and minimize the impact of these changes on users interface to the database.

50

This is done first determining what information is needed, how items are related, what constraints are established. Tables are created and linked by appropriate key fields.

The constraints on the data are used to guide the building of tables. The tables are created by making use of the normalization principles. The proposed system has its own tables in the third normal form.

CODE DESIGN When large volumes of data are being handled, it is important that the item be identified, stored or selected easily and quickly. To accomplish this, each data item must have unique identification and must be related to other items of the same type. Codes can provide brief identification of each item, which replace longer description that would be more awkward to store and manipulate.

VALIDATION CHECKS: A common problem with computer system is that it is very easy to put incorrect data into them. So the input data is validated to minimize errors and data entry. For certain data specific code has been given and validations are done which enable the user to enter the required data and correct them if they have entered wrong codes, e.g. you could mistype a link name or a URL in a database resulting in reports being occurred in the wrong link name.

If you put incorrect data into the computer system then you will get incorrect results out of it. Processing incorrect inputs will produce incorrect outputs. This lead to the acronym: GIGO (Garbage in Garbage Out). Sometimes incorrect data can actually cause a computer system to stop work temporarily. This is a particular problem in batch processing systems when data may be processed overnights. If incorrect data stops a batch processing systems for working then a whole night processing time may be lost. People who develop computer systems go through a lot of trouble to make it difficult for incorrect data to be entered. The two main techniques used for this purpose are:

51

VERIFICATION VALIDATION

(Fig 5)

VERIFICATION: A verification check ensures that data is correctly transferred into a computfrom the medium that it was originally stored on. Verification checks are usually used to check that a data entry worker has correctly typed information written on a data collection form into a computer.

Methods of Verification: The two most common methods of verification are: On-Screen prompts: After a user has entered some data it is redisplayed on the screen. The user is prompted to read the data and confirm that it has been entered correctly. If the user has entered any data incorrectly he should response that the data is inaccurate and retypes the incorrect parts.

Dual Inputs: This method is used when data is entered through the keyboard. The data to be entered is typed in twice by two different operations. The two copies of data are been compared, any difference are detected, the operators will be

52

prompted to retype the sections that differ until both copies agree/. When the two copies agree the computer assumes that the data has been entered correctly.

VALIDATION: A validation check is an automatic check made by computer to ensure that any data entered into the computer is sensible. A validation check does not make sure that data has been entered correctly. It only ensures that data is sensible. For this reason validation checks are not usually as effective as verification checks. They can however be carried out automatically by the computer and therefore require less work by the computer operators making them There are many different methods of validations. The most appropriate method to use will depend upon what data is being entered. The most common methods are listed here cheaper to use.

Methods of validation: Presence Checks: checks that data has been entered into the field and that it has not been left blank, e.g. checks that Project ID is always entered into each record in a database of project details.

Type Checks: checks that an entered value is of particular type. E.g. checks that a field is varchar, a number, etc.

Length Checks: checks that an entered value, e.g. Project ID is no longer than a particular number of characters.

Format Checks: Checks that an entered value has a particular format. E.g. a date must be consist of mm-dd-yy format.

Validation checks can be performed by any piece of software. If the user tries to do unauthorized operations the appropriate error messages are produced by the systems.

DATA DICTIONARY: In our DFD, we give names to data flows, processes, and data stores. Although the names are descriptive of the data, they do not give details. So the following the

53

DFD, our interest is to build some structured place to keep details of the contents of data flow, processes, and data store. A data dictionary is a structured repository of data about data.It is a set of rigorous definition of all DFD data element and data structure.A data dictionary has many advantages. The most obvious is documentation; it is valuable reference in any organization. Another advantage is improving analyst/user communication by establishing consistent definition of various elements, terms and procedures.

During implementation, it serves as a common base against which programmers who are working on the system compare data description. Also control information maintained for each data element is cross referenced in the data dictionary. E.g. program that use a given data element are cross referenced in a data dictionary, which makes it easy to identify them and make any necessary changes. Finally, a data dictionary is an important step in building a database. Most database management system has a data dictionary as a standard feature.

DFD (Data Flow Diagram)

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. DFDs can also be used for the visualization of data processing (structured design). On a DFD, data items flow from an external data source or an internal data store to an internal data store or an external data sink, via an internal process. A DFD provides no information about the timing of processes, or about whether processes will operate in sequence or in parallel. It is therefore quite different from a flowchart, which shows the flow of control through an algorithm, allowing a reader to determine what operations will be performed, in what order, and under what circumstances, but not what kinds of data will be input to and output from the system, nor where the data will come from and go to, nor where the data will be stored (all of which are shown on a DFD).

E-R DIAGRAM An entity-relationship (ER) diagram is a specialized graphic that illustrates the relationships between entities in a database. ER diagrams often use symbols

54

to represent three different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes. The E-R (entity-relationship) data model views the real world as a set of basic objects (entities) and relationships among these objects. This represents the overall logical structure of the database.

DFD: A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modelling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated. DFDs can also be used for the visualization of data processing (structured design). A DFD shows what kinds of data will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel (which is shown on a flowchart). DFD Symbols:

A square defines a source or destination of system data.

An arrow line identifies the data flow or data in motion. It is a pipeline

through which information flows.

55

A circle or bubble represents a process transform incoming data flow in to

outgoing data flow.

A horizontal line represents data stored or data at rest or a temporary rest

repository of data.

An open rectangle refers to the database storage

DATA FLOW DIAGRAM:

Fig 6

SEQUENCE DIAGRAM:

56

UML sequence diagrams model the flow of logic within your system in a visual manner, enabling you both to document and validate your logic, and are commonly used for both analysis and design purposes. Sequence diagrams are the most popular UML artifact for dynamic modeling, which focuses on identifying the behavior within your system A Sequence diagram is a two dimensional in nature. On the horizontal access, it shows the life of the object that it represents, while on the vertical axis, it shows the sequence of the creation or invocation of these objects.

1. LOGIN

Fig 7 User _ 1 : \ User login request \ _ Registrations _

AADHAAR _

2 : \ Prompt for uname _

& pwd \

3 : \ Enter uname & pwd \ _

4 : \ Verify\ _

5 : \ Return status _

( Success / Failure) \

6 : \ Load modules ( On success ) \ _

7 : \ Load error page ( On failure ) \ _

57

2. UID GENERATION

A:Admin

T:Admin Op Req UID Regn Prompt citizen info citizen Info validate save&update Uid db Req Uid process populate pending appn's from UID DB show appn,prompt appno appno fetch details from UID DB

C:citizen

show appn Info apply status genarate uid,pin save to uid db status status

Fig 8

3. APPLICATION

58

C:Citizen

S:Staff Op

P:pp Op

R:crime Op Req Uid,ply status prompt uid,status issue status

req passport prompt uid uid,pin

save&update uid db

populate presonal profile from uid db check issue status fetch status from uid db status save&update db req pp appn process fetch appn's with issue status show appn,prompt appno appno fetch profile Info show Info verification status report update passport Info UId DB status Digital pp/deny

Fig 9 4. SECURITY CHECK

59

S:Security officer Req entry prompt uid uid,pin

A:AAI Op

populate personal profile from db

check flying status from uid db

entry allowed/disallow

Fig 10

5. LICENSE CHECK

60

C:citizen req licence prompt uid uid, pin

S:Staff Op

R:RTA Op

populate personal profile from db save&update uid db req licence appn's fetch appn's with non-issue status show appn,prompt appno appno fetch profile Info show Info schedule test details update licence Info in uid db status status set test pass/fail Info issue/deny license

license details/fail

Fig 11

61

DATA DICTIONARY

Airport authority table

Admin Table

Aadhaar Staff Table

62

Citizen Table

License Table

Passport Table

63

Pin master Table

License Status Table

Transition Status

Passport Travel Table

64

ER Diagram

UID

PWD

AID

APWD D AAI

ADMIN

Main tain

SID ASTAFF

SPWD

Register

Main tain

Sname

Others SID
Reg ps& RTA

PINMAST

Sname

cregen

Others

stype pwd

area

cpwd cid cname

Figure 12

65

Figure 13

Figure 14

66

Figure 15

Figure 16

67

CLASS DIAGRAM: Class diagrams describe the static structure of a system, or how it is declared rather than how it behaves. These diagrams contain classes and associations.

Admin + Aid + pwd + Appno 0..1 UID ... + userid + pwd 0..1 + user type + signin ( ) + cancel ( ) 0..1 StaffOp + uid + ppno + Doi + Doe + Lno + Dor + view ppAppno ( ) + view Lic Appn ( ) + process pp ( ) + process Lic ( ) + check flystatus ( ) + reports ( ) Citizen Op + uid + pwd + cname + contact + photo + regn ( ) + view uid ( ) + reg pp ( ) + reg Lic ( ) + view pp ( ) + view Lic ( ) AAI Op + uid + crime status + do check + set status ( ) 0..1 0..1 0..1

Crime Op + uid + fly status + set status ( ) + revoke staatus ( ) + view uid ( )

+ RegnInfo ( ) + process UID ( )

0..1

RTA Op + uid + appno + status + Doi + Dot + Dor + view Lic app ( ) + process Lic ( ) Po Op + uid + appno + status + ppno + Doi + Doe + view pp App ( ) + security status ( ) + issue,deny pp ( )

Fig 17

68

DEPLOYMENT DIAGRAM: The Environment model view encompasses the structural and behavioral aspects of the domain in which a solution must be realized. This view is also known as the deployment or physical view. This view is composed of deployment diagrams. These diagrams describe the configuration of processing resources elements and the mapping of software implementation components onto them. These diagrams contain nodes, components and their relationships

Citizen

Apply UID

Admin

VIEW UID

Staff

Application Process Middle Tier Tomcat JSP UIDDB

Crime

Investigatio n

RTA

Schedule test

AAI

Flying status

Fig 18

69

INPUT DESIGN: The input design is the link between the information system and the user. It comprises developing specification and procedure for data preparation and those steps that are necessary to put transaction data into a usable form for processing data entry. The activity of putting data into the computer for processing can be achieved by instructing the computer to read data from a written or printed document or it can occur by having people key data directly into the system. The design of inputs focuses on controlling the amount of inputs required, controlling errors, avoiding delay, avoiding extra steps and keeping the process simple.

The system needs the following information for processing: Information regarding Project Details Information regarding Project Design Details Information Employees Details

OUTPUT DESIGN

In output design, emphasis is given on producing a hard copy of the information required as the output on the CRT screen in some predefined manner. Computer output is the most important and direct source of information to the use. Since the reports are directly referred by the management for taking the decisions and to draw conclusions, they must be designed with utmost care and the details in the reports must be simple, descriptive and clear to the user. The options for the outputs and reports are given the system menu.

Table Structure It is a coherent collection of data with some inherent meaning, designed, built and populated with data for a specific purpose. A database stores data that is useful to us.

70

71

SYSTEM TESTING

Software testing is the process of testing the software product. Effective software will contribute to the delivery of the higher quality software products, more satisfied users; lower maintenance cost and more accurate and reliable results and ineffective testing will adversely effect these factors. Hence software testing is very

necessary and important activated of software development process. It is a

expensive process and consumers one third to half of the cost of a development project. Good testing involves much more than just running the program, a few timer to see whether it works. Through analysis of program helps us to test more systematically and more effectively.

Thus testing is the process of executing a program with the intent of find It is the critical element of the software quality assurance and represent the ultimate

review of specification design and code generation. The increasing visibility of software as system element and the associated cost with the software failure are motivating forces for well planned testing. Software development organization

expands between 30-40% of the project efforts as the code is frequently the only product that can be executed and where actual behavior can be observed.

Testing is the phase where errors remaining from all previous phases must be detected. Thus testing consumes more resources than any other phase in software development because of resources.

There is a need to ensure both that the individual programs have written correctly and that the individual programs have been written correctly and that the system as a whole will work. System processing is an expert but critical process that can take as much as 50 percent of the budget for the program development. The common view of testing held by users is that it is performed to prove that there are no errors in the program. Therefore, the most useful and practical approach is with the understanding that testing is the process of executing a program with the explicit intention of finding

72

errors that is making the program fail. Effective testing program does not guarantee system reliability.

Unit testing

Module testing

Subsys testing

System testing

Acceptance testing

Component testing

Integration testing (Fig 19)

User testing

Testing Strategies Diagram

DETAILED TESTING STRATEGIES There are two general strategies for testing software discussed as under:

PROGRAMME CODE TESTING The code testing strategy examines the logic of the program. To follow this method the analyst develops test cases that result in executing every instruction in the program of module that is every path through the program is tested. A path is a specific combination of conditions that is handled by the program.

73

On the surface code testing seems to be and ideal method for testing software. However, even if code test can be performed entirely it does not guarantee against software failures.

This testing strategy determines whether all aspects are even implemented. Code testing also does not check the range of data that the program will accept so when software failures occur in actual use, it is frequently because users submitted data outside of expected ranges.

SPECIFICATION TESTING To perform specification testing, the analyst examines the specification stating that the program should do and how it should perform under various conditions. Then test case are developed for each condition or combination of conditions and submitted for processing. By examining the result the analyst can determine whether the program performs according to its specified requirements. This strategy treats the program as if it were a block box: the analyst does not look into the program to study the code and is not concerned about whether every instruction or path through the program is tested. In that sense specification testing is not complete testing. However the assumption is that if the program meets the specifications, it will not fail. A common pattern in these familiar forms is that we evaluate a product in terms of our expectations, not with the respect to a specification or a standard. Consequently, goal is not to find faults, but to demonstrate performance. Because of this we tend to approach system testing from a functional standpoint rather than from a structural one. Since it is so intuitively familiar, system testing in practice tends to be less formal than it might be, and is compounded by the reduced testing interval that usually remains before a delivery deadline. The software should actually be tested on many different hardware set ups, although the full range of memory, processor, operating system, and peripheral possibilities may be to large for complete testing. There are many types of

specifications, and we should be aware of those as we perform system testing.

74

There are many instance, there may be a specified level of performance required of the software this may involve measurement of response time under various loads and operating conditions. It may also require measurement of main and disk

memory usage. Software reliability should also be measured during all other tests of the integrated product. If minimum and average up time behavior of the product was specified, and then these should be also be met. The time and effort needed to recover from failures should

recorded and compared with specifications. These specifications should

represent customers wants and needs.

Neither code nor specification testing strategy is ideal. However specification testing is a more efficient strategy since, it focuses on the way software is expected to be used. It also shows once again how important the specifications developed by analysts are throughout the entire system development process.

So during the final testing, user acceptance is tested and is the most important amongst all the phases of system development life cycle. Testing is necessary to see that designed system meets with the objectives and goals decided during project identification stage.

Software testing is the process of testing the software product. Effective software will contribute to the delivery of the higher quality software products, more satisfied users; lower maintenance cost and more accurate and reliable results and ineffective testing will adversely effect these factors. Hence software testing is

necessary and important activated of software development process. It is a very expensive process and consumers one third to half of the cost of a Good testing involves much more than just running the

development project.

program, a few timer to see whether it works. Through analysis of program helps us to test more systematically and more effectively.

Thus testing is the process of executing a program with the intent of find It is the critical element of the software quality assurance and represent the ultimate review of specification design and code generation.

75

The increasing visibility of the software as system element and the associated cost with the software failure are motivating forces for well planned testing. Software development organization expands between 30-40% of the project efforts as the code is frequently the only product that can be executed and where actual behavior can be observed. Testing is the phase where errors remaining

from all previous phases must be detected.

Thus testing consumes more resources than any other phase in software development because of resources. There is a need to ensure both that the individual programs have written Correctly and that the individual programs have been written correctly and that the system as a whole will work. System processing is an expensive but critical process that can take as much as 50 percent of the budget for the program development. The common view of testing held by users is that it is performed to prove that there are no errors in the program. Therefore, the most useful and practical approach is with the understanding that testing is the process of executing a program with the

explicit intention of finding errors that is making the program fail. Effective testing program does not guarantee system reliability.

LEVELS OF TESTING UNIT TESTING Unit testing is the process of taking a module and running it in isolation from the rest of the software product by using prepared test cases and comparing the actual results with the results predicted by the specifications and design of the module? One purpose of testing is to find and remove as many errors in the software as practical. There are number of reasons in support of unit testing than testing the entire product: The size of a single module is small enough that we can locate an error fairly easily. The module is small enough that we can attempt to test it in some demonstrably exhaustive fashion. Confusing interactions of multiple errors in widely different parts of the, are eliminated. software

76

INTEGRATION TESTING The purpose of unit testing is to determine that each independent module is correctly implemented. This gives little chance to determine that the interface between modules is also correct, and for this reason integration testing must be performed. One specific target of integration testing is the interface: whether

parameters match on both sides as to type, permissible ranges, meaning and utilization. There are several classical integration strategies that really have little basis in a rational methodology. Top downintegration proceeds down the invocation hierarchy, adding one module at a time until an entire tree level is integrated, and thus it eliminates the need for drivers. The bottom up strategy works similarly from the bottom and has no need of stubs. A sandwich strategy runs from top and bottom concurrently, meeting some ware in the middle.

A common pattern in these familiar forms is that we evaluate a product in terms of our expectations, not with the respect to a specification or a standard. Consequently, goal is not to find faults, but to demonstrate performance. Because of this we tend to approach system testing from a functional standpoint rather than from a structural one.

Since it is so intuitively familiar, system testing in practice tends to be less formal than it might be, and is compounded by the reduced testing interval that usually remains before a delivery deadline. The software should actually be tested on many different hardware set ups, although the full range of memory, processor, operating system, and peripheral possibilities may be to large for complete testing. There are many types of specifications, and we should be aware of those as we perform system testing. There are many instance, there may be a specified level of performance required of the software this may involve measurement of response time under various loads and operating conditions. It may also require

measurement of main and disk memory usage. Software reliability should also be measured during all other tests of the integrated product.

77

If minimum and average up time behavior of the product was specified, and then these should be should also be met. The time and effort needed to recover from failures

recorded and compared with specifications. These specifications

should represent customers wants and needs.

This strategy treats the program as if it were a block box: the analyst does not look into the program to study the code and is not concerned about whether every instruction or path through the program is tested. In that sense specification testing is not complete testing. However the assumption is that if the program meets the specifications, it will not fail.

A common pattern in these familiar forms is that we evaluate a product in terms of our expectations, not with the respect to a specification or a standard. Consequently, goal is not to find faults, but to demonstrate performance. Because of this we tend to approach system testing from a functional standpoint rather than from a structural one.

Since it is so intuitively familiar, system testing in practice tends to be less formal than it might be, and is compounded by the reduced testing interval that usually remains before a delivery deadline. The software should actually be tested on many different hardware set ups, although the full range of memory, processor, operating system, and peripheral possibilities may be to large for complete testing. There are many types of specifications, and we should be aware of those as we perform system testing.

There are many instance, there may be a specified level of performance required of the software this may involve measurement of response time under various loads and operating conditions. It may also require measurement of main and disk memory usage. Software reliability should also be measured during all other tests of the integrated product.

78

SYSTEM TESTING

Of the three levels of testing, the system level is closest to everyday experience. A common pattern in these familiar forms is that we evaluate a product in terms of our expectations, not with the respect to a specification or a standard. Consequently, goal is not to find faults, but to demonstrate performance. Because of this we tend to approach system testing from a functional standpoint rather than from a structural one.

Since it is so intuitively familiar, system testing in practice tends to be less formal than it might be, and is compounded by the reduced testing interval that usually remains before a delivery deadline. The software should actually be tested on many different hardware set ups, although the full range of memory, processor, operating system, and peripheral possibilities may be to large for complete testing. There are many types of specifications, and we should be aware of those as we perform system testing.

There are many instance, there may be a specified level of performance required of the software this may involve measurement of response time under various loads and operating conditions. It may also require measurement of main and disk memory usage. Software reliability should also be measured during all other tests of the integrated product. If minimum and average up time behavior of the product was specified, and then these should be met.

The time and effort needed to recover from failures should also be recorded and compared with specifications. customers wants and needs. These specifications should represent

A common pattern in these familiar forms is that we evaluate a product in terms of our expectations, not with the respect to a specification or a standard. Consequently, goal is not to find faults, but to demonstrate performance. Because of this we tend to approach system testing from a functional standpoint rather than from a structural one. Since it is so intuitively familiar, system testing in practice

79

tends to be less formal than it might be, and is compounded by the reduced testing interval that usually remains before a delivery deadline. The software should actually be tested on many different hardware set ups, although the full range of memory, processor, operating system, and peripheral possibilities may be to large for complete testing. There are many types of specifications, and we should be aware of those as we perform system testing. There are many instance, there may be a specified level of performance required of the software this may involve measurement of response time under various loads and operating conditions.

It may also require measurement of main and disk memory usage. Software reliability should also be measured during all other tests of the integrated product. If minimum and average up time behavior of the product was specified, and then these should be met. The time and effort needed to recover from failures should also be recorded and compared with specifications. These specifications should represent customers wants and needs.

GUIDELINES FOR CHOOSING TEST CASES DURING SYSTEM TESTING The first is that testing the systems capabilities is more important than testing its components. This implies that failures that are catastrophic should be looked for whereas failures that are merely annoying need not worry us. The idea is that a user can deal with a badly formatted report, but probably cannot deal with unavailability of the report.

Second rule is that testing the usual is more important than testing the exotic. This can be accomplished by subjecting the software to the kind that is representative of actual use. The user may be able to help with this kind of testing. In fact, software engineers may exhibit blind spots that cause them to notice exotic problems; while they ignore problems that user would spot immediately.

Third, if we are testing after modification of an existing product, we should test old capabilities rather than new ones. The rationale here is that the user is not

80

depending on the new functions of the Software, and would not be paralyzed if these were not right. But a failure in the old functionality could do just that paralyze the users entire operation.

SYSTEM IMPLEMENTATION Total integration computerization of the activities of corporation will be done in four phases. Phase I - Preparations for computerization. Phase II - Implementation and integration of activities. The implementation plan in the form of bar chart brings out all the steps required for the change from manual / partially computerized system to Integrated Computer System. The detailed steps would be as under.

PREPARATION OF COMPUTERIZATION Approval of study report. Placement of order for purchase of computer / up gradation of computers and allied equipment. Delivery and installation of computer and allied equipment at the office.

INTEGRATION AND IMPLEMENTATION OF ACTIVITIES Detailed system study. Approval of input / output forms. Software development of activities. Training of staff for use of application software staff identified for working on computer will have to be trained on the use of computers and in data entry on personal computers. A high accuracy rate will be expected, as the quality of the data entered will of the outputs received from the computer. Moreover, they

determine the quality

will also be trained to use the software developed for various activities. Also, managers and senior officials should be trained in the fundamentals of data processing and some hands on computers.

81

Finally, the analysts and the programmers must deliver the new system into operation training end-users and providing for a smooth transition from the old system to the new system.

These phases are collectively as systems implementation. Implementation is concerned with detail physical creation of the candidate system. The key point is actual operation and user acceptance testing before the system is released to the user. Implementation follows on from the detailed design stage. Implementation would cover the following steps:Training of the staff. Programming. System Testing Master file conversion Change over Procedures.

MAINTENANCE OF THE SYSTEM After installation phase is completed and the user staff is adjusted to the changes created by the candidate system, evaluation and maintenance begins. Like any system there is an aging process that requires periodic maintenance of hardware and software. If the new information is inconsistent with the design specification then changes have to be made.

Hardware also requires periodic maintenance to keep in tune with design specifications. The importance of maintenance is to continue to bring new system to standards user priorities change in organizational requirements or environmental factors also call for system enhancement

82

83

Snap Shots of Project

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

2.

Validations

# 1

Field PAN Card

Validations JOB ID will be put to upper case. JOB ID format is validated for 5 character, 4 numbers and 1 character Will not accept any spaces in between Job Card Starts with MH Will be put to upper case. Will not accept any spaces in between the Job Card No. Accepts alphanumeric,/,and -

NREGA Job Card

Passport

Passport will be put to upper case. Passport should be alphanumeric, will accept / and - , no other Characters allowed. Will not accept any spaces in between First 3s character are alphabet and next 7s are Numeric

EPIC No.

100

101

Coding
Style.css /* Design by Free CSS Templates http://www.freecsstemplates.org Released for free under a Creative Commons Attribution 2.5 License */

body { margin: 0; padding: 0; background: #000000 url(images/img01.jpg) repeat left top; font-family: "Trebuchet MS", Arial, Helvetica, sans-serif; font-size: 13px; color: #837669; }

h1, h2, h3 { margin: 0; font-family: Georgia, "Times New Roman", Times, serif; font-weight: normal; color: #D53707; }

102

h1 { font-size: 44px; }

h2 { font-size: 20px; }

h3 { }

p, ul, ol { margin-top: 0; line-height: 240%; text-align: justify; font-family: "Trebuchet MS", Arial, Helvetica, sans-serif; font-size: 11px; }

ul, ol { }

blockquote { }

a { color: #D53707; }

a:hover { text-decoration: none; }

a img { border: none; }

103

img.left { float: left; margin: 7px 30px 0 0; }

img.right { float: right; margin: 7px 0 0 30px; }

hr { display: none; }

.text1 { padding: 5px 10px 5px 10px; background: #FF6600; color: #000000; }

/* Header */

#header-wrapper { }

#header { height: 80px; margin: 0 auto;

104

padding: 0 20px; background: url(images/img02.jpg) repeat; border-bottom: 4px solid #910000; }

/* Menu */

#menu { float: left; width: 680px; height: 40px; }

#menu ul { margin: 0; padding: 25px 0 0 20px; list-style: none; line-height: normal; }

#menu li { display: block; float: left; }

#menu a {

105

display: block; float: left; margin-right: 17px; padding: 5px 12px; text-decoration: none; font: 14px Georgia, "Times New Roman", Times, serif; color: #FFFFFF; }

#menu a:hover { text-decoration: underline; background: #C03511;

#menu .current_page_item a { background: #910000; color: #FFFFFF; }

/* Search */

#search { float: right; width: 305px; height: 40px;

106

#search form { float: right; margin: 0; padding: 28px 20px 0 0; }

#search fieldset { margin: 0; padding: 0; border: none; }

#search input { float: left; font: 12px Georgia, "Times New Roman", Times, serif; border: none; }

#search-text { width: 135px; height: 18px; padding: 3px 0 0 5px; background: #ECF9E4; color: #658453;

107

#search-submit { height: 21px; margin-left: 12px; color: #39561D; }

/* Page */

#page { margin: 0 auto; padding: 0 40px; }

/** LOGO */

#logo { height: 148px; }

#logo h1, #logo p { float: left; margin: 0; padding: 0; line-height: normal;

108

#logo h1 { padding-top: 45px;}

#logo h1 a { padding: 5px 0 5px 10px; text-decoration: none; background: #000000; color: #E46115; }

#logo h1 a:hover { text-decoration: none; }

#logo p { padding: 65px 0 0 15px; font: italic 13px Georgia, "Times New Roman", Times, serif; color: #B6ACA2; }

#logo p a { text-decoration: none; color: #B6ACA2; }

#logo p a:hover { text-decoration: underline; }

109

/* Content */

#content { float: left; width: 75%; }

/* Post */

.post { margin-bottom: 25px; }

.post .title { margin-bottom: 3px; padding: 2px 0px 2px 15px; background: url(images/img03.jpg) repeat left top; }

.post .meta { margin: 0 0 3px 0; padding: 2px 30px 2px 15px; font: italic 10px Georgia, "Times New Roman", Times, serif; color: #B6ACA2; }

110

.post .meta a { color: #B6ACA2; }

.post .entry { padding: 25px 15px; }

.post .links { margin: 0 250px 0 0; padding: 0 0 0 0px; }

.post .links .comments { }

.post .links .permalink { padding-left: 17px; }

/* Sidebar */

#sidebar { float: right; width: 20%; margin-top: -100px; padding-left: 30px; }

111

#sidebar ul { margin: 0; padding: 0; list-style: none; line-height: normal; }

#sidebar li { margin-bottom: 30px; padding: 0 0 20px 0px; }

#sidebar li ul { line-height: 200%; }

#sidebar li li { margin: 0; padding: 0 0 0 15px; }

#sidebar p { padding: 0 15px; }

112

#sidebar h2 { margin: 0 0 20px 0px; padding: 6px 0 6px 15px; background: url(images/img03.jpg) repeat left top; font-size: 18px; }

#sidebar p { line-height: 200%; }

/* Calendar */

#calendar { }

#calendar caption { padding-bottom: 5px; font-weight: bold; }

#calendar table { width: 100%; border-collapse: collapse; border: 1px solid #0F0E0E;

113

#calendar thead th { padding: 5px 0; text-align: center; border-top: 1px solid #0F0E0E; border-left: 1px solid #0F0E0E; background: #0F0E0E; }

#calendar tbody td { padding: 5px 0; text-align: center; }

#calendar tfoot td { padding: 5px; }

#calendar tfoot #next { text-align: right; }

#calendar #today { background: #0F0E0E; }

114

/* Footer */

#footer { margin: 0 auto; padding: 0; background: url(images/img02.jpg) repeat; border-top: 4px solid #910000; }

#footer p { margin: 0; padding: 20px 0; text-align: center; line-height: normal; color: #FFFFFF; }

#footer a { color: #FFFFFF; }

Web Config <?xml version="1.0"?> <!-Note: As an alternative to hand editing this file you can use the

115

web admin tool to configure settings for your application. Use the Website->Asp.Net Configuration option in Visual Studio. A full list of settings and comments can be found in machine.config.comments usually located in \Windows\Microsoft.Net\Framework\v2.x\Config --> <configuration> <configSections> <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"> <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"> <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/> <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

116

<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/> <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>

<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/> <section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/> </sectionGroup> </sectionGroup> </sectionGroup> </configSections> <appSettings/>

117

<connectionStrings> <add name="ConnectionString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Database.mdf;Integ rated Security=True;User Instance=True" providerName="System.Data.SqlClient" /> </connectionStrings> <system.web> <!-Set compilation debug="true" to insert debugging symbols into the compiled page. Because this affects performance, set this value to true only during development. --> <compilation debug="true"> <assemblies> <add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> </assemblies> </compilation> <!--

118

The <authentication> section enables configuration of the security authentication mode used by ASP.NET to identify an incoming user. --> <authentication mode="Windows"/> <!-The <customErrors> section enables configuration of what to do if/when an unhandled error occurs during the execution of a request. Specifically, it enables developers to configure html error pages to be displayed in place of a error stack trace.

<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm"> <error statusCode="403" redirect="NoAccess.htm" /> <error statusCode="404" redirect="FileNotFound.htm" /> </customErrors> --> <pages> <controls> <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add tagPrefix="asp" namespace="System.Web.UI.WebControls"

119

assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> </controls> </pages> <httpHandlers> <remove verb="*" path="*.asmx"/> <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false"/> </httpHandlers> <httpModules> <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> </httpModules> </system.web> <system.codedom>

120

<compilers> <compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"> <providerOption name="CompilerVersion" value="v3.5"/> <providerOption name="WarnAsError" value="false"/> </compiler> <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" warningLevel="4" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"> <providerOption name="CompilerVersion" value="v3.5"/> <providerOption name="OptionInfer" value="true"/> <providerOption name="WarnAsError" value="false"/> </compiler> </compilers> </system.codedom> <!-The system.webServer section is required for running ASP.NET AJAX under Internet Information Services 7.0. It is not necessary for previous version of IIS. --> <system.webServer> <validation validateIntegratedModeConfiguration="false"/>

121

<modules> <remove name="ScriptModule"/> <add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> </modules> <handlers> <remove name="WebServiceHandlerFactory-Integrated"/> <remove name="ScriptHandlerFactory"/> <remove name="ScriptHandlerFactoryAppServices"/> <remove name="ScriptResource"/> <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

122

</handlers> </system.webServer> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/> <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/> <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/> </dependentAssembly> </assemblyBinding> </runtime> </configuration>

123

Admin Applied Jobs

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq;

public partial class admin_applied_jobs : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) {

} }

Admin Category using System;

124

using System.Collections; using System.Configuration; using System.Data; using System.Data.SqlClient; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq;

public partial class admin_country : System.Web.UI.Page { SqlConnection con = null; SqlDataAdapter adp = null;

public void category() { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

string query = "select * from Category";

125

adp = new SqlDataAdapter(query, con); DataSet ds = new DataSet(); adp.Fill(ds);

DropDownList1.DataSource = ds.Tables[0]; DropDownList1.DataTextField = "category_name"; DropDownList1.DataValueField = "category_id"; DropDownList1.DataBind(); DropDownList1.Items.Insert(0, new ListItem("select", "0"));

con.Close(); }

public void area() { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

string query = "select * from area"; adp = new SqlDataAdapter(query, con); DataSet ds = new DataSet(); adp.Fill(ds);

DropDownList2.DataSource = ds.Tables[0];

126

DropDownList2.DataTextField = "area_name"; DropDownList2.DataValueField = "area_id"; DropDownList2.DataBind(); DropDownList2.Items.Insert(0, new ListItem("select", "0"));

con.Close(); }

protected void Page_Load(object sender, EventArgs e) { if (!IsPostBack) { category(); area();

} } protected void Button1_Click(object sender, EventArgs e) { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

string qry = "insert into Category(category_name) values ('" + TextBox1.Text + "')";

127

SqlCommand cmd = new SqlCommand(qry, con);

cmd.ExecuteNonQuery();

clear();

public void clear() {

TextBox1.Text = ""; TextBox2.Text = ""; TextBox3.Text = "";

} protected void Button2_Click(object sender, EventArgs e) { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

string qry = "insert into area(category_id,area_name) values (" + DropDownList1.SelectedValue + ",'" + TextBox2.Text + "')";

128

SqlCommand cmd = new SqlCommand(qry, con);

cmd.ExecuteNonQuery();

clear();

} protected void Button3_Click(object sender, EventArgs e) { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

string qry = "insert into post(area_id,post_name) values (" + DropDownList2.SelectedValue + ",'" + TextBox3.Text + "')";

SqlCommand cmd = new SqlCommand(qry, con);

cmd.ExecuteNonQuery(); clear(); } } Admin Comp Packages

129

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq;

public partial class admin_comp_packs : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) {

} }

Admin Country using System; using System.Collections; using System.Configuration;

130

using System.Data; using System.Data.SqlClient; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq;

public partial class admin_country : System.Web.UI.Page { SqlConnection con = null; SqlDataAdapter adp = null;

public void country() { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

string query = "select * from Country"; adp = new SqlDataAdapter(query, con); DataSet ds = new DataSet();

131

adp.Fill(ds);

DropDownList1.DataSource = ds.Tables[0]; DropDownList1.DataTextField = "country_name"; DropDownList1.DataValueField = "country_id"; DropDownList1.DataBind(); DropDownList1.Items.Insert(0, new ListItem("select", "0"));

con.Close(); }

public void state() { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

string query = "select * from State"; adp = new SqlDataAdapter(query, con); DataSet ds = new DataSet(); adp.Fill(ds);

DropDownList2.DataSource = ds.Tables[0]; DropDownList2.DataTextField = "state_name"; DropDownList2.DataValueField = "state_id";

132

DropDownList2.DataBind(); DropDownList2.Items.Insert(0, new ListItem("select", "0"));

con.Close(); }

protected void Page_Load(object sender, EventArgs e) { if (!IsPostBack) { country(); state(); } } protected void Button1_Click(object sender, EventArgs e) { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

string qry = "insert into Country(country_name) values ('" + TextBox1.Text + "')";

SqlCommand cmd = new SqlCommand(qry, con);

133

cmd.ExecuteNonQuery();

clear();

protected void Button2_Click(object sender, EventArgs e) { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

string qry = "insert into State(country_id,state_name) values (" + DropDownList1.SelectedValue + ",'" + TextBox2.Text + "')";

SqlCommand cmd = new SqlCommand(qry, con);

cmd.ExecuteNonQuery();

clear(); }

protected void Button3_Click(object sender, EventArgs e) {

134

con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

string qry = "insert into City(state_id,city_name) values (" + DropDownList2.SelectedValue + ",'" + TextBox3.Text + "')";

SqlCommand cmd = new SqlCommand(qry, con);

cmd.ExecuteNonQuery();

clear(); }

public void clear() {

TextBox1.Text = ""; TextBox2.Text = ""; TextBox3.Text = "";

} }

Admin Employee Profile

135

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq;

public partial class admin_emp_profiles : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) {

} }

Admin Jobs using System; using System.Collections; using System.Configuration;

136

using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq;

public partial class admin_jobs : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) {

} }

Admin Profiles using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security;

137

using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq;

public partial class admin_js_profiles : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) {

} }

Admin Login

using System; using System.Collections; using System.Configuration; using System.Data; using System.Data.SqlClient; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI;

138

using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq;

public partial class admin_login : System.Web.UI.Page { SqlConnection con = null; SqlDataReader dr = null; SqlCommand cmd = null;

protected void Page_Load(object sender, EventArgs e) {

} protected void Button1_Click(object sender, EventArgs e) { bool Flag = false;

con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

cmd = new SqlCommand();

139

cmd.Connection = con; cmd.CommandType = CommandType.Text; cmd.CommandText = "select * from Login"; dr = cmd.ExecuteReader(); string Role = "";

while (dr.Read()) { string UserName = dr[0].ToString(); string PassWord = dr[1].ToString();

if (tbaun.Text == UserName && tbapw.Text == PassWord) { Role = dr[2].ToString(); Flag = true; }

} dr.Close();

if (Flag == false) { Label4.Visible = true; Label4.Text = "Not authorized"; }

140

if (Flag == true) {

if (Role=="admin") { Label4.Visible = true; Label4.Text = "Authorized"; Response.Redirect("~/admin_unpw.aspx"); } } con.Close(); } }

Admin Save Candidate

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls;

141

using System.Web.UI.WebControls.WebParts; using System.Xml.Linq;

public partial class admin_saved_cands : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) {

}} Search By Company

using System; using System.Collections; using System.Configuration; using System.Data; using System.Data.SqlClient; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq;

public partial class search_by_company : System.Web.UI.Page

142

{ SqlConnection con = null; SqlDataAdapter adp = null; SqlCommand cmd = null;

protected void Page_Load(object sender, EventArgs e) { if (!IsPostBack) { company(); } } public void company() { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open(); string query = "select * from Job_post j1, Company c1 where j1.company_id = c1.company_id"; adp = new SqlDataAdapter(query, con); DataSet ds = new DataSet(); adp.Fill(ds); DropDownList1.DataSource = ds.Tables[0]; DropDownList1.DataTextField = "company_name"; DropDownList1.DataValueField = "company_id";

143

DropDownList1.DataBind(); DropDownList1.Items.Insert(0, new ListItem("select", "0")); con.Close(); } protected void Button4_Click(object sender, EventArgs e) { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open();

int cid = 0; cid = Convert.ToInt32(Session["Cid"].ToString()); int rws = 0; rws = Convert.ToInt32(GridView1.Rows.Count.ToString()); // Label22.Text = GridView1.Rows.Count.ToString(); for (int i = 0; i < rws; i++) { CheckBox chk = (CheckBox)GridView1.Rows[i].FindControl("CheckBox3");

if (chk.Checked == true) { String a = GridView1.Rows[i].Cells[19].Text; string query = "insert into Saved_jobs (candidate_id,jobpost_id) values (" + cid + "," + a + ")";

144

cmd = new SqlCommand(query, con); cmd.ExecuteNonQuery(); } } } protected void Button3_Click(object sender, EventArgs e) { con = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=C:\\Users\\Pratik\\Desktop\\Jobadd a\\App_Data\\JobportalDB.mdf;Integrated Security=True;User Instance=True"); con.Open(); string query = "select Jobpost_id,company_name,job_title,category_name,area_name,country_name,s tate_name,city_name,post,no_vacancy,start_date,end_date,expr_req,skills_req, edu_req,basic_req,salary_min,salary_max from job_post,Area,Category,City,State,Country,Company where Job_post.area_id=Area.area_id and Area.category_id=Category.category_id and Job_post.city_id=City.city_id and State.state_id=City.state_id and Country.country_id=State.country_id and Job_post.company_id=Company.company_id and Job_post.company_id="+ DropDownList1.SelectedValue; adp = new SqlDataAdapter(query, con); DataSet ds = new DataSet(); adp.Fill(ds); GridView1.DataSource = ds; GridView1.DataBind();

145

} protected void GridView1_SelectedIndexChanged(object sender, EventArgs e) {

} } Search Job using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class search_job : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } }

146

Saved Candidates using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class saved_candidates : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void GridView1_SelectedIndexChanged(object sender, EventArgs e) { } protected void GridView1_RowCommand(object sender, GridViewCommandEventArgs e) { } }

147

148

CONCLUSION

The application can now identify each individual uniquely. Every citizen is identified for all the Govt transactions with the help of his Aadhaar card. The application integrates various Govt departments into a single point of Contact. This helps in avoiding unnecessary delays or find where the delay is happening when applications are processed. The application can be extended to all the Govt departments with modification. New modules can be added without affecting the existing modules.

149

SCOPE OF THE PROJECT

Citizen Registration, identification of each citizen using UID(Unique identification number) Secure passport application Passport application verification by the police authority in online mode. Passport Issue & Denial Provide crime department to integrate with the airport to stop someone from flying. Apply for License. Provide Test details and scenario - RTA. Provide test result. Issue or deny License. Change of address in one ID reflects the change in others.

150

BIBLIOGRAPHY

Name of the Book

Authors Name

Publications

ASP.NET 2.0 Learning MySql ODBC using ADO.Net C# And .NET frame Work ASP.NET Visual Studio .Net With C# Software Engineering

William Jones Trudy Pelzer Kevi Kline Robert Powell James Grusong Herbert K Mathews

BPB Publications. Tata McGraw Hill Tata McGraw Hill New Age International Prentice Hall Publications Prentice Hall Publications

K.K. Aggarwal & Yogesh New Age International Singh

World Wide Web www.wikipedia.com www.yahoo.com www.google.com www.astatalk.com

151