26-06-2012, 12:41 PM
Govt Transactions with the Help of AadhaarCcard
Govt Transactions.docx (Size: 1.81 MB / Downloads: 39)
SYSTEM ANALYSIS
Existing System
In the current scenario each citizen is provided with all identity cards for each services to avail the same by the user. As the services are not integrated, to a single control, it locks monitoring giving rise to misuse of identity cards. A single user can avail multiple cards of the same service (not in duplicate ) where a single identity is required.
Ex: Single person can avail multiple voter ids, ration cards from multiple areas. This increases burden on issuing authority. It also makes it complicated to trace the identity of the civilian.
Disadvantages:
1. The services are individual functioning entities and are not integrated.
2. Work is performed and maintained in registers or offline software’s.
3. Improper vigilance by the respective authority.
4. Lack of tracking of multiple issued cards.
5. Increased burden on the respective authorities.
Proposed system
In the proposed architecture, the civilian is suggested to register himself to the central authority where a unique id is provided to the user. All the public services are handled by central authority, making it easy to track the availed citizens list.
Each citizen is given with a unique id that is to be submitted for availing the respective service. A digital copy of the issued service (local service id ) is given to citizen which resembles his uniqueness for that service. The citizen can perform his transactions of booking the tickets using his passport, vehicles using his license (digital) by providing hid identity of uniqueness.
The modules included are
1. Login
2. Administrator
3. License Issue Authority
4. Passport Issue Authority
5. Bookings
6. Investigation
Login
This module accepts the username and password from the user which on validation passes the control to respective modules. It also allows the user to register himself with the required data for availing the AADHAAR id.
Administrator
This module contain privileges to register various services where each is identified by unique id, approval or rejection of citizen request for AADHAAR id.
License Issue Authority
This module contain privileges to maintain requests made by the civilians and their verification with their approval or rejection. If the user request is approved, a unique id is assigned as license no. (digital form).
Hardware Interfaces
As the application is deployed in the server machine and the users or clients are at remote areas, there needs to exist an hardware interface connecting the server and the client. Hence they require hardware interface containing cables, hubs, switches, etc to put all the users under a single network.
Software Interfaces
As the application that is proposed is a website, deployed under the server system, the server needs to contain respective framework, the web-service ( Tomcat ) in working condition and server system with network facility. The administrator of that server is soul responsible for its maintenance.
On the other hand, the clients reside at the remote areas ( end-users ) and require the browser enabled operating system with network facility to interact with the server. The clients need not maintain any additional software to work with it.
Communication Interfaces
Since the application is web based and supports client server architecture both the server and the clients require connectivity using the network layer containing cables, hubs, switches, modems etc. These elements act as data transporting layers between server and client systems.