Citizen Card Management System
Trust negation is a web based application which is used for government related departments. Government has various departments like RTO, PASSPORT, and Election Commission and so on. In order to avoid the queue system in government office and maintain the overall details of public the project called Trust Negotiation has developed. Once the public has registered with these sites they need not fill the form for every department at the time, in other words there is no work for manual registration. The registered form of the public is maintained globally so that any department can take the personal details of the public. If the public registered with site and apply for passport they need not apply in passport office just they can mention their National Id. The public get their National Id once they registered with this site. By using this National ID they can visit any government office and easily finish their work. This consumes the time for the public and government Employee. Suppose if the data given by Public is insuffient he /she has to approach the concerned government department.
PROJECT OUTPUT VIDEO:
Already in this type of applying for online application we does not use the privacy fact ,It can be viewed by everyone and it can be also editable, to achieve privacy we have to maintain the customers database and entry securely and privacy is the important fact which has to be focused . So here we use three tier architecture for registering the details in a secure way.
In this project we generally deal with the trust negotiation, we obtain the trust negotiation using an ontology based approach, we develop the project by using online pan card application and online license application to get the trust negotiation, the project mainly explains about the privacy of a customer who submits their document online. They no need to type their all personal details they give only their universal username and password its enough, after giving that all their personal details will come from the universal database.
- National Register Module
- Pan card Register Module
- Voter Id Register Module
- License Register Module
- Web Service Module
- Application Layer
- Business Layer
- Data Layer
- Admin Module
NATIONAL REGISTRATION MODULES:
As the name itself defines this is a registration module for public. The public has to give sufficient data for doing registration. This module contains sub module like PAN CARD Registration, Voter ID Registration and License Registration. Data will change from one sub module to another. Validation is done for the purpose that user should not miss any of the field in the particular registration form. Once the public has registered, he/she get a national ID which is unique. Using this national ID the public can claim one among or all above mentioned ID Proof (s).
WEB SERVICE MODULES:
Using Web services, your application can publish its function or message to the rest of the world.
Web services use XML to code and to decode data, and SOAP to transport it (using open protocols).
With Web services, your accounting department’s Win 2k server’s billing system can connect with your IT supplier’s UNIX server.
Web Services have Two Types of Uses
Reusable application components.
There are things applications need very often. So why make these over and over again?
Web services can offer applications components like currency conversion, weather reports, or even language translation as services.
Ideally, there will be only one type of each application component, and anyone can use it in their application.
Connect existing software.
Web services help to solve the interoperability problem by giving different applications a way to link their data.
With Web services you can exchange data between different applications and different platforms.
Web Services have three basic platform elements: SOAP, WSDL and UDDI.
SOAP is a simple XML-based protocol to let applications exchange information over HTTP.
SOAP is a protocol for accessing a Web Service.
SOAP stands for Simple Object Access Protocol
SOAP is a communication protocol
SOAP is a format for sending messages
SOAP is designed to communicate via Internet
SOAP is platform independent
SOAP is language independent
SOAP is based on XML
SOAP is simple and extensible
SOAP allows you to get around firewalls
SOAP is a W3C standard
WSDL is an XML-based language for describing Web services and how to access them.
- WSDL stands for Web Services Description Language
- WSDL is based on XML
- WSDL is used to describe Web services
- WSDL is also used to locate Web services
- WSDL is a W3C standard
UDDI is a directory service where businesses can register and search for Web services.
- UDDI stands for Universal Description, Discovery and Integration
- UDDI is a directory for storing information about web services
- UDDI is a directory of web service interfaces described by WSDL
- UDDI communicates via SOAP
- UDDI is built into the Microsoft .NET platform
A layer is a reusable portion of code that performs a specific function. In the .NET environment, a layer is usually setup as a project that represents this specific function. This specific layer is in charge of working with other layers to perform some specific goal. In an application where the presentation layer needs to extract information from a backend database, the presentation would utilize a series of layers to retrieve the data, rather than having the database calls embedded directly within itself. Let’s briefly look at the latter situation first.
When the .NET 2.0 framework became available to the world, there were some neat features that allowed the developer to connect the framework’s GUI controls directly to the database. This approach is very handy when rapidly developing applications. However, it’s not always favorable to embed all of the business logic and data access code directly in the web site, for several reasons:
- Putting all of the code in the web site (business logic and data access) can make the application harder to maintain and understand.
- Reusing database queries in the presentation layer often isn’t done, because of the typical data source control setup in the ASP.NET framework.
- Relying on the data source controls can make debugging more difficult, often due to vague error messages.
So in looking for an alternative, we can separate the data access code and business logic into separate “layers”, which we’ll discuss next.
The Data Layer
The key component to most applications is the data. The data has to be served to the presentation layer somehow. The data layer is a separate component (often setup as a separate single or group of projects in a .NET solution), whose sole purpose is to serve up the data from the database and return it to the caller. Through this approach, data can be logically reused, meaning that a portion of an application reusing the same query can make a call to one data layer method, instead of embedding the query multiple times. This is generally more maintainable.
But the question is how is the data returned? Multiple frameworks employ different techniques, and below is a summary:
- ADO.NET – Built into the .NET framework, ADO.NET contains a mechanism to query data out of the database and return it to the caller in a connected or disconnected fashion. This is the most common approach to working with data, because it’s already readily available Table Adapters/Strongly-Typed Datasets – Strongly-typed datasets and table adapters provide a similar means to querying the data through ADO.NET, but add strong-typing features, meaning custom objects are generated for you to work with.
- Enterprise Library – Enterprise library Data Access Application Block provides a flexible way to connect to databases of multiple types, without having to know anything about that database, through an abstract approach
- LINQ-to-SQL – LINQ to SQL is an ORM tool that uses a Data Context object as the central point to query data from the database. Auto-Generated Code – Tools like Code Smith Studio automatically generate the code for you based upon a database schema. Simply writing a script to output the code you want to use and the backend is generated in a short amount of time.
Most (if not all) options above take advantage of the CRUD (create, read, update, or delete) operations that databases support, so all of that is available as shown above. There are plenty of resources online to help you get started.
Though a web site could talk to the data access layer directly, it usually goes through another layer called the business layer. The business layer is vital in that it validates the input conditions before calling a method from the data layer. This ensures the data input is correct before proceeding, and can often ensure that the outputs are correct as well. This validation of input is called business rules, meaning the rules that the business layer uses to make “judgments” about the data.
However, business rules don’t only apply to data validation; these rules apply to any calculations or any other action that takes place in the business layer. Normally, it’s best to put as much logic as possible in the business layer, which makes this logic reusable across applications.
One of the best reasons for reusing logic is that applications that start off small usually grow in functionality. For instance, a company begins to develop a web site, and as they realize their business needs, they later decide to add a smart client application and windows service to supplement the web site. The business layer helps move logic to a central layer for “maximum reusability.”
The ASP.NET web site or windows forms application (the UI for the project) is called the presentation layer. The presentation layer is the most important layer simply because it’s the one that everyone sees and uses. Even with a well structured business and data layer, if the presentation layer is designed poorly, this gives the users a poor view of the system.
It’s best to remove as much business logic out of the UI and into the business layer. This usually involves more code, but in my mind, the excess time (which ranges from minimal to moderate, depending on the size of the application) pays off in the end.
However, a well-architected system leaves another question: how do you display it in an ASP.NET or windows application? This can be more of a problem in ASP.NET, as the controls are more limited to the type of inputs they can receive. If you use certain architectures, like passing datasets from the data to the presentation layer, this isn’t as much of a challenge; however, the challenge can come with business objectsthat support drill-through business object references.
The admin module plays a major role in the application. The Admin module is used to control all the administrative tasks of the administrator. The administrator takes care of entering all the essential information in site so that it is accessed world wide with a very fast accessing time and in a well defined manner. All the essential information is composed by integrating the information in a hierarchical manner. Each Government wing admin will do all the enhancements works like adding Sub modules, Editing and Updating the Public Details and so on.
Processor Type : Pentium -IV
Speed : 2.4 GHZ
RAM : 512 MB RAM
Hard Disk : 20 GB HD
Operating System : Win2000/XP
Programming Package : Visual Studio.Net 2.0.
Front End : Asp.Net with C#.
Back End : MS SQL Server2005.