unique id management

5/9/2018 Unique ID Management - slidepdf.com

http://slidepdf.com/reader/full/unique-id-management-559bf8f174a83 1/3

The Great Mind Challenge - Project Scenario Template

Note: Already filled information should not be changed

1.Name of theProject

Unique ID management.

2.Objective/Vision

Motive of this project is to provide a unique ID to

each and every citizen of India while providinghim/her a birth certificate. Citizens after attainingage of 18 must register at RTO office or Collectoroffice or Thasildar office and get a password toaccess the site. ID card will be provided to everyuser after registration. Later on they can changetheir password. Once they enter the site they canpay their electricity bill and telephone bill, book railway tickets and airline tickets and pay theirtaxes. During elections people can poll online.Government officials can verify details about a

person from the database for issuing vehiclelicense, passport, visa, etc.

3.Users of theSystem

A. All Indian citizens of age 18 and above.B. Authorized Government security officials.C. ModeratorsD. Administrator

4.FunctionalRequirements(Atleast Eight)

i. User Login: Every citizen can login and accestheir information page.

ii. Security: A normal user other than Governme

officials, moderators and administrator can onlyaccess his/her information. For any informationupdate they must approach corresponding office tget approval.

iii. Security Officials Login: Authorized securitypersons in police, army, and airlines should given unique ID and password to access the Securityofficials page which give access to information of users.

iv. Restriction for officials: Officials can accessuser’s information in demand. Unnecessary access

is prohibited.v. Moderator: Moderator can have access to

details of all the users. He can modify the entiredatabase.

vi. Admin: Admin can modify the entire codingand structure of the system.

vii. No moderator and admin can change his/herdetails without any approval.

viii. Change of photo of every user after 3 years imandatory.



5.Non-functionalrequirements(Atleast Four)

i. Secure access of confidential data (user’sdetails). SSL can be used.

ii. 24 X 7 availability

iii. Better component design to get betterperformance at peak time

iv. Flexible service based architecture will behighly desirable for future extension

6.Optionalfeatures

a. Online polling during elections.

b. If a person commits crime, his/her detawill be added to the crime database. This wibe useful for embassy, employment exchangand CBI officials.

c. Reducing online credit card usage forpayment and booking tickets. (User can refilamount for his/her ID either online or at theRTO office or Collector office or Thasildaroffice.)

d. Banking security issues.

7.User interfacepriorities

A. Professional look and feel

B. Use of AJAX at least with all registration form

C. Browser testing and support for IE, NN,Mozilla, and Firefox.

D. Use of Graphical tool like JASPER to showstrategic data to admin

E. Reports exportable in .XLS, .PDF or any othedesirable format

8. Reports

A. User ID and password.B. Moderator ID and password.C. Government official ID and password.D. Admin ID and password.

9.Other importantissues

A. Payment process is simple and secure.B. Easy access to user database.

10. Team Size 2 – 4 members

11.Technologies tobe used

UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA

12. Tools to be Used

•

ROSE/RSA / WebSphere Modeler• Eclipse/ RAD / Lotus Forms Designer / PortletFactory

• WebSphere Portal/ WAS/ WAS CE / WPS

• DB2 Express – ‘C’ or DB2 UDB

• Tivoli CDP/TSM / Tivoli Directory Server

• Linux will be the preferred OS.

13. FinalDeliverable

A. Online or offline help to above said users,Application deployment executive and



must include

developer

B. Application archive ( .war/.ear ) with sourcecode

C. Database backup and DDL Script

D. Complete Source code

unique id management

Documents