final review1

8/6/2019 Final Review1

1/47

ON-LINE DRIVING LICENSE SYSTEM

BY B.VIDYA(08J11AO505)

D.SREE VACHANA(08J11AO514) N.VENKATESH KUMAR(08J11AO545) NITESH K AGARWAL( 08J11A0544)

Under the guidance of


2/47

Existing system:

Time consuming process.

Applicants has to fill the forms.

Submit to the corresponding officer.

If he is qualified in the test ,Learner s License isissued.

Later he need to apply for permanent license.


3/47

Drawbacks of existing system:

Needs a lot of manual work.

It s a time consuming process.

Does not provide user status when ever he wants .


4/47

P roposed system:

On-line Driving License System aims at the automationof issuing License.

The present system provides the user with manyfacilities.

The applicant has to select the Test center and datefor LLR Test.


5/47

Types of Users:

Administrator.P rometric.

User.


6/47

Administrator Module:

Updating the database.

Scheduling exam dates.

Updating the status of the user.Maintaining the personal details.


7/47

P rometric module:

Conducting test.

Submitting result to User & Admin.


8/47

User Modules :

Registration. Apply for LLR.

P ermanent License.


9/47

Requirements:

Hardware requirements:

Processor : PENTIUM(R)

Primary Memory (RAM) : 1GBSecondary Memory : 160 GB HDD(HardDisk)Operating system :Windows Xp


10/47

Sof tware requirements:F ront-end: JavaScript , HTML, JSP.Back-end: Oracle 11g.Server :Web Server (Apache Tomcat 5.5).API :Java EE 5.5/Java SE 1.6.


11/47

Design & Diagram


12/47

Use-case diagram


13/47

Use-case for FillApplication

F ill p s l ils

S l s

S l s

> Appli

E i ils


14/47

Use-case for Take a test

Update status

Administrator

Test result

Enter applicationnumber

Get question from database Applicant

Submit answers


15/47

Sequence diagram for Fill Application

: Databa e controller : Databa e1: tart interface

2: Fill a lication

3: ubmit detail

4: tore detail5: Generate a lication number

6: get a number

7: Get a number


16/47

For Registration

: Databa e controller : Databa e

1: tart interface

2: Fill regi tration form detail

3: get id and a word4: Regi tration ucce ful

5: ubmit detail

6: ubmit detail7: tore detail


17/47

For Test

Database controller Database

1 Start interface

3 Get app number

2 Enter app number

5 Get details

6 Validate

7 Issue Test8 Display test

9 Submit answers 10 Submit answers11 Get answers

12 Validate

13 Update details14 Disp lay result15 Display result

4 send app number


18/47

Collaboration Diagram for fill application


5: Generate a lication number

2: Fill a lication

1: tart interface

3: ubmit detail

4: tore detail

6: get a number

7: Get a number

Prometric Databa eU er


19/47

Collaboration diagram for Registration


7: tore detail

2: Fill regi tration form detail

3: get id and a word4: Regi tration ucce ful

1: tart interface

5: ubmit detail

6: ubmit detail

U er Prometric Databa e


20/47

For Test


6: Validate12 : Validate

2: nter a number 9: ubmit an wer

8: Di lay te t15 : Di lay re ult

1: tart interface7: I ue Te t

14 : Di lay re ult

3: Get a number 10 : ubmit an wer

5: Get detail11 : Get an wer

13 : U date detail

4: end a number

U er Prometric Databa e


21/47

Class diagram

Addressadmin _idapp_nodnocitypincode

give address()get user id()get admin id()

administrator admin_idadmin_locadmin_name

update details()iss ue LLR()iss ue PL()

applicantusernamepasswdapp_no

Login()register()fill application()take test()

License UI

displays Registrationform()diplays login page()displays application form()dispalys test login page()displays test()

1

1

1

1

1..*

1

1..*

1 Database

provide info()store applicant details()store admin details()store credit card info()store test details()

Database controller

validate user login()start interface()validate app number()validate test()

1..*1 1..*1 11 11


22/47

Entity-Relationship diagram:


23/47

CL I NT

licationWill Be Loaded

WebC ontainer

HTTP

D

PTOR

DynamicC ontentHandler

taticC ontentHandler

System Architecture


24/47

Administrator Functional Architecture

E nter ID&PWDC heck withDataba e

If Valid

elect an ctionand enter Info

Di lay ction

tore In Databa e


25/47

User Functional Architecture

E nter ID&PWD

C heck withDataba e

If Valid

elect an ctionand enter Info

Di lay ction

tore In Databa e

Prometric ID


26/47

Reports Functional Architecture

S elect the Re ort S end the Reque t

Get the InformationDi lay Re ort


27/47

H OME PAGE


28/47


29/47


30/47

Forms


31/47

LLR Form


32/47

Select date


33/47

Test Cases


34/47

REGISTRATION

Test Case: RegistrationTest Description: The details of the user are stored in DatabaseP re- conditions: Database Connectivity and Server is RunningP ost- conditions: User should fill all the fields. P assword must be atleast of 6 characters,Confirming password redirect tohomepage.A ction P erformed: Store detailsin todata base and redirect to homepage.Ex pected Results: Alerts when post conditions are not followedConditions verified: YesResults: Success


35/47

FILL APP LICATION

Test Case: FillApplicationTest Description: The details of the Applicant are stored in DatabaseP re- conditions: Database Connectivity and Server is RunningP ost- conditions: Already filled or notA ction P erformed: If not filled,Store detailsin todata base andredirect to home page.Else redirect to user status page.Ex pected Results: Details should not be stored in Database whenapplication is already filled.Conditions verified: Yes

Results: Success


36/47

3 .CH ECK CARD OP TIONS

Test Case: Check card optionsTest Description: Validate user submitted card detailsP re- conditions: Database Connectivity and Server is Running

P ost- conditions: Card number and card type should exist in DatabaseA ction P erformed: updating balanceEx pected Results: Alerts when post conditions are not followedConditions verified: YesResults: Success


37/47

Conclusion

Finally we can say that this system reduces

manual work and saves time.

since this system is not proposed byGovernment, this may be considered as modelto develop the actual system.


38/47

THANK YOU


39/47


40/47


41/47

REGISTER TABLE

A ttribute Data ty e S ize Key

UN AME V A RC H A R2 15 PRI MA RY K E Y

P S WD Varchar2 15 Not Null

FN AME Varchar2 20 not null

L N AME Varchar2 20 not null

F ATN AME Varchar2 20 not null

GE NDE R Varchar2 8 not null

A DDR V A RC H A R2 40 not null

DOB D ATE - not null


42/47

APP LICANT TABLE


A PPNO NU M BE R 15 PRI MA RY K E Y

FN AME Varchar2 20 Not Null

L N AME Varchar2 20 not null

F ATN AME Varchar2 20 not null

GE NDE R Varchar2 8 not null

A DDR V A RC H A R2 40 not null

DOB D ATE - not null


43/47

APP LICANT TABLE


C VE HICL E V A RC H A R2 20 NOT NU LL

A GPRO Varchar2 20 Not Null

A DRPRO Varchar2 20 not null

S T ATUS Varchar2 20 not null


44/47

CH ECKCARD TABLE


C A RDNO NU M BE R 20 PRI MA RY K E Y

B A L A NC E NUM BE R 20 Not Null


45/47

SELECT DATE TABLE


LOC ID V A RC H A R2 30 FOR E IGNKE Y/(R E FE RE NC ES LOC ATION)

TD A

TE

D A

TE -

Not Null

AV A IL I A BIL ITY Varchar2 20 not null

C OUNT NU M BE R 5 not null


46/47

TEST RESULT TABLE


A PPNO NU M BE R 15 PRI MA RY K E Y

LOC ID Varchar2 20 Not Null

TD ATE D ATE - not null

RES ULT Varchar2 20 not null


47/47

TEST TABLE


QNO NU M BE R 4 PRI MA RY K E Y

QU ES TION Varchar2 50 Not Null

OPT1 Varchar2 2 not null



A NS V A RC H A R2 2 not null

final review1

Documents