Sei sulla pagina 1di 60

Driving License Management System

A Project Report

Submitted By

SAJIB CHAKRABORTY (C131050)


ADNUN BIN ABDULLAH CHOWDHURY (C131057)

Project Submitted In Partial Fulfilment of the Requirement for the Degree of Bachelor of
Computer Science and Engineering

Department of Computer Science and Engineering

International Islamic University Chittagong

Bangladesh

1
CERTIFICATE OF APPROVAL

The project entitled as “Driving License Management System” submitted by Sajib


Chakraborty(C-131050) and Adnun bin Abdullah Chowdhury (C131057),to the Department of
Computer Science & Engineering (CSE) of International Islamic University Chittagong (IIUC)
has been accepted as satisfactory for the partial fulfillment of the requirements for the Degree of
Bachelor in Computer Science & Engineering.

Supervised & approved by:

___________________________

Mohammad Mahmudur Rahman

Assistant Professor

Dept. of CSE, IIUC.

International Islamic University Chittagong

2
DECLARATION
We hereby declare that the work have been done by ourselves under the supervision of
Mohammed Mahmudur Rahman, Assistant Professor, Department of Computer Science &
Engineering, International Islamic University Chittagong. No portion of the work contained in
this project has been submitted in support of any application for any other degree or qualification
of this or any other university or institute of learning.

Supervised by:

Mohammed Mahmudur Rahman


Assistant Professor
Department of Computer Science & Engineering
International Islamic University Chittagong

Submitted by:

SAJIB CHAKRABORTY
C131050

Department of CSE, IIUC.

ADNUN BIN ABDULLAH CHOWDHURY


C131057

Department of CSE, IIUC.

3
ACKNOWLEDGEMENTS
First we express our heartiest thanks and gratefulness to almighty for His divine blessing makes
both of us possible to do this project successfully and an opportunity to pursue the B.Sc.
(Honour’s) program at International Islamic University Chittagong.
We take this immense opportunity to express our heartfelt & sincere gratitude towards our
supervisor Mohammed Mahmudur Rahman, Assistant Professor, Department of CSE, IIUC for
his invaluable guidance. It would have never been possible to complete this work without his
continuous support and encouragement. In spite of his very busy schedule, he was always
approachable and available to attend to my problems, discuss the solutions, and give the
appropriate advice. Doing work of project under his supervision was a very enlightening and
enjoyable experience.
We also wish to thank all the faculty members of the Department of Computer Science and
Engineering for the invaluable knowledge they have imparted us and for teaching the principles
in most exciting and enjoyable way.
Specially, a great thank to our parents for supporting and taking us to this stage in life; it was
their blessings, which always gives us courage to face all challenges and made our path easier.

4
DEDICATION

This project is dedicated to


Our Parents & Our beloved Teachers.

5
ABSTRACT

This project deals with Online based ‘Driving License Management System’.

Bangladesh Road Transport Authority, widely known as BRTA, is the authority to issue driving
licences in Bangladesh. It provides the facilities to hold thorough driving tests to determine if an
applicant is able to abide by certain rules and get the licence to drive motor vehicle or not. To
drive a motor vehicle in a public place every one must have driving licence. To obtain a driving
licence one should hold a learner driving licence before appearing the driving test. Application
for the learner's licence to be submitted to the licensing authority in the prescribed form along
with related papers and fees. Successful candidate of the driving test have to submit application
in the prescribed form to the licensing authority along with the related papers & fees. During this
process due to corruption, people are constantly falling victim to extreme suffering.

So,the objectives of this project is to provide greater facilities for all user for motor-vehicles
license system and also get the impression from user,to make the system usable for all. So our
aim is that to help this people by this online based license system to free from their sufferings.

The project has been developed in back-end: PHP Server side script and MySQL Database and
front-end: HTML, CSS, and JavaScript.

6
Table of Contents
CHAPTER 1: INTRODUCTION………………………………………………………….10-11

1. Introduction………………….…………………………………………….…….……10

1.2 Old System…………………………………………………………………….…….10

1.3 Present System……………………...…………………………………………….…11

1.4 Objective ……………………………………………………………………….…..11

1.5 Summary………………………………………………………………………….....11

CHAPTER 2: METHODOLOGY……………...………………………………………….12-18

2.1 Necessity of Methodology…………….……………………………………………..12

2.2 Software Development Life Cycle (SDLC)……………………………………...13-15

2.2.1 Feasibility Study……………………………………………………….......14


2.2.2 Requirement Definition…............................................................................14
2.2.3 System Specification……………………………………………………....14

2.2.4 System Design……………………………………………………..………14

2.2.5 Program Design & Coding…………………………………………..…….14

2.2.6 Testing…………………………………………………………………….14

2.2.7 Implementation……………………………………………………………..15

2.2.8 Change Request Definition…………………………………………………15

2.3 Software Process Model………………………………………………………..........15

2.3.1 Waterfall Model…………………………………………………………....15

2.4 Why We Use This Model?......................................................................................... 16

2.5 Gantt Chart………………………………………………………………….……….17


2.6 Time Period………………………………………………………………………….18
2.7 Summary…………………………………………………………………………….18

7
CHAPTER 3: Requirement Collection and Analysis………………………..….…...……19-22

3.1 Requirement Engineering………………………………………………..…………19

3.2 Requirements Engineering Process Model………………………………...……….19

3.3 Technical Feasibility……………………………………………………….……….20

3.4. Technical Criteria…………………………………………………….…………….20

3.5. Economic Feasibility………………………………………………………………..21


3.6 Operationally Feasibility…………………………………………….…….……...…21
3.7 Schedule Feasibility…………………………………………………………………21

3.8 Testing ………………………………………………………………….………...21-


22

CHAPTER 4: SOFTWARE DESIGN DESCRIPTION……………………...…………..23-35

4.1 Software Design Description………………………………………………...……....23

4.2 Overall Design……………………………………………………………………24-35

4.2.1 Flow Chart………………………………………………………………………....24

4.2.1.1 Flow Chart for Admin ………………………………..…..24

4.2.1.2 Flow Chart for User ………………………………….…..25

4.2.2 Use Case Diagram………………………………………....…...…...…26-


28

4.2.3 Entity Relationship Diagram (ERD)………………………..……..………29

4.2.4 Data Flow Diagram …………………………………….……….......


……..30

4.2.5 Process or Function………………………………….……..…..……….…30

4.2.6 External Entities……………………………………….…..……..…….….30

4.2.7 Data Stores…………………………………………….…………………..28

4.2.8 Data Flows………………………………………….……………………..31

4.2.9 Steps of DFD……………………………………….….………...………..31

4.3.1 Level of DFD………………………………………....……….......………32

8
4.3.2 Level 0 DFD…………………………………..…………………………..32

4.3.3Level 1 DFD for Admin…………...……………………………….………


33
4.3.4 Level 1 DFD for User……………………….…………………….……...34
4.4 Activity Diagram of user ……………………….………………………….35

CHAPTER 5: DATABASE …………………………………………………..……………36-40

CHAPTER 6: DESIGN AND IPLEMENTATION……….…………….....…….………..41-57

6.1 Overview……………………………………………………...……..……...….....41
6.2 Graphical Representation………………………………………..……………41-57

CHAPTER 7: CONCLUSION………………………...………..…………….…………..……58

REFERENCES……………………….……………………………………………….…..….…59

9
Chapter 1

INTRODUCTION
1. INTRODUCTION
“Driving License Management System” is an online based project. We introduce our
transportation sector to people through this system.

Right now BRTA is dedicated to regulatory functions like registration and fitness certification of
vehicles under existing relevant laws. If the whole gamut of its functionalities could be brought
under coverage of IT based software-driven system, the organizational discipline and functional
transparency could be better ensured.

The main aim of this project is to design an automatic verification system is to “Save time,
Money & Harassments during License system in BRTA.”

1.2 OLD SYSTEM


Bangladesh Road Transport Authority (BRTA) was has functioned since January 1988.
BRTA is a regulatory body to control, manage and ensure discipline in the road transport sector
of Bangladesh, as well as to maintain road safety. It works under the Ministry of Communication
to carry out the purposes set out for it under the Motor Vehicle Ordinance. But About 50 percent
of driving licenses carried by drivers across the country are fake and prepared through
irregularities and corruption and most of the drivers were not issued by BRTA.

Not only the fraudsters, a section of staffs of BRTA and the Ministry of Communications are
also are providing drivers with fake licences. The government faced a loss of Taka 20 crore in
revenue income in the last five years due to corruption at BRTA.

In Existing system, if a person needs any relevant information regarding any vehicle, than he/she
will have to go to that concern office and fill up a lot of forms and details manually and then they
are able to collect information. So it is not very effective as the license process takes a lot of time
and harassment.

1.3 PRESENT SYSTEM

This project deals with Online based Automobiles driving license System. The main goal of the
project is to automate the whole driving license process carried out in the organization with
improved performance and realize the vision of transportation sector.

10
1.4 OBJECTIVE
 To provide greater facilities for all user for motor-vehicles system

 To help Government & peoples for motor vehicles registration & license procedure.
 To get the impression from user

 To issue license after conducting competency test for drivers, conductors & driving
instructors and to take measures for renewal of the same.
 To issue and renew roadworthiness certificate of motor vehicles.
 To issue and renew route permit for passenger & goods vehicles.
 To make the system usable for all.

 Due to corruption and brokers, people are constantly falling victim to extreme suffering.
So our aim is that to help this people by this online based license system to free from
their sufferings.

 Removing the information gap.

 Disperse the disadvantage of Transport sector.

 Develop and digitalized our country.

1.5 SUMMARY
“Driving License Management System” is an online based project.
The main aim of this project is to provide greater facilities for all users for motor-vehicles license
system. This web based vehicle identification system reduces the load and makes the way easy
for getting all the relevant details regarding vehicles license and access it in one click whenever
needed.

11
Chapter 2

METHODOLOGY

Software engineering is the practice of using selected process techniques to improve the quality
of a software development effort. This is based on the assumption, subject to endless debate and
supported by patient experience, which is a methodical approach to software development results
in fewer defects and, therefore, ultimately provides shorter delivery time and better value. The
document collection of policies, process, and procedures used by a development team or
organization to practice software engineering is called its software development methodology
(SDM) or software development life cycle (SDLC).

A methodology is a formalized approach to implementing the SDLC (i.e. it is a list of steps and
deliverables). There are many different system development methodologies, and each one is
unique because of its emphasis on process verses data and the order and focus it places on each
SDLC phase.

2.1 Necessity of Methodology


Software is a complex artefact created by human being. The entire complex is being produced in
a step-by-step procedure, which is called methodology for that artefact. Therefore, methodology
is needed for software in order to build it with consistency.
To discuss this topic in software engineering point of view, at first we have to decide the basic
theory and then realize its necessity. Analysing about points, we are completely aware of our
purpose. To determine by how we will proceed successfully, we will introduce a methodology,
which contains the steps for developing our software depending on proposed system. Methods
are simply techniques that we apply to accomplish some objectives. Methods include guidelines,
techniques, and tools for building a software system. In order to develop the “Driving License
Management System” we need a methodology. An Advanced SDLC is the appropriate
framework at this point.

12
2.2 Software Development Life Cycle (SDLC)

Software Development Life Cycle gives us an overview and guidelines to develop quality
software. For “Driving License Management System” we follow SDLC to make it reliable for
the user.

System Request
Change Request

Feasibility
Study (1)
Change Request
Requirement
Definition (8)
Definition (2)

System
Implementation Specification
(7) (3)

System Design
Testing (6) (4)

Program
Design &
Coding (5)

Figure 2.1: Software Development Life Cycle

13
2.2.1 Feasibility Study
At first stage of SDLC we have to measure feasibility study of our proposed system that is
system feasibility study of economics, implementation etc.

2.2.2 Requirement Definition


At this stage, we have to develop system’s requirement by using well-known requirement
engineering framework.

RE involves three major frames are:

 Requirement Analysis
 Requirement Specification
 Requirement Validation

2.2.3 System Specification

In system specification, our first concern is ERD (Entity Relationship Diagram), which shows
entity with their attributes, relationship with entities involving one to one, one to many, many to
one or many to many, assigning primary keys & perform normalizations to reduce data
redundancy.

2.2.4 System Design

System Design accomplished by two ways; overall design and Detailed design. Overall design
sets structure of shape of the software. “Structure Charts” might be used here as part of
functional design strategy. Detailed design defines the processing that is carried out through the
whole program. Stepwise refinement might be applied for our proposed system.

2.2.5 Program Design & Coding

In SDLC model, program design and coding occupies as little as 10% of project effort. Here we
write the coding by using well-known programming language such as PHP, HTML, JavaScript,
AJAX, and CSS.

2.2.6 Testing

Testing is one of the most important steps to develop a system. Testing is a process of finding
errors. Testing can be implemented in our proposed by two ways,

 White Box Testing &


 Black Box Testing

14
2.2.7 Implementation

In SDLC model, this stage involves implementing our “Driving License Management System”
to getting driving license system for users & sees how it works or sees is its meet user’s intent.

2.2.8 Change Request Definition

If any request comes after delivering the system then this stage defines the processing of
development of the delivered system. This type of maintenance is very important.

2.3 Software Process Model

Process is an activity, which operates on an object and changes its state. Model is the graphical
representation of an object. Therefore, a process model shows the activities of software
graphically. We need process model because process is important than product (software). If the
process is good, the product also is good. While developing the “Driving License Management
System” we follow the water fall Model; particularly The waterfall model is a sequential (non-
iterative) design process, used in software development processes, in which progress is seen as
flowing steadily downwards (like a waterfall) through the phases of conception, initiation,
analysis, design, construction, testing, production/implementation and maintenance.

2.3.1 Watrerfall Model:

Waterfall model is shown below:

15
Figure: Waterfall Model

2.4 Why We Use This Model?

In our ‘Driving License Management system’ we follow waterfall model. The waterfall model
is a popular version of the systems development life cycle model for software engineering. Often
considered the classic approach to the systems development life cycle, the waterfall model
describes a development method that is linear and sequential. Waterfall development has distinct
goals for each phase of development. Imagine a waterfall on the cliff of a steep mountain. Once
the water has flowed over the edge of the cliff and has begun its journey down the side of the
mountain, it cannot turn back. It is the same with waterfall development. Once a phase of
development is completed, the development proceeds to the next phase and there is no turning
back
We Prefer Waterfall Model, because of its following advantages: -

 Very good approach for small projects.


 Easy to use and follow.
 Cost effective.
 Each phase completely developed.
 Development processed in sequential manner so very less chance to rework.
 Easy to manage the project.
 Easy documentation.

Limitation of Waterfall Model:


 Not very useful for the large project.
 Less effective if requirements are not very clear at the beginning.
 Very difficult to move back to change on the previous phase.
 Testing starts once development completes, so more and more chances of bugs to be
found.
 High risk.
 Less flexible.

16
2.5 Gantt Chart

One of the oldest and still one of the most useful of presenting schedule information is the
GANTT CHART. Gantt chart is a pioneer in the field of scientific management. The Gantt chart
show planned and actual progress for a number of tasks displayed horizontal timescale.
A feasibility study is usually conducted after procedures have discussed a series of business ideas
or scenarios. The feasibility study helps to “frame “and “flesh-out” specific business scenarios.
So they can be studied in-depth. During this process the number of business alternatives under
consideration is usually quickly reduced.
To complete this project, we have some roles and responsibility. And if we want to complete this
within due time, we should maintain the roles and responsibility.

Gantt chart Time/Week


0 1 2 3 4 5 6 7 8 9 10 11
Task
Number

Task1
Initial study
Task2
Task3 Feasibility study

Task4 Requirement Analysis


Task5 Design
Task6 Review report
Task7 Coding
Task8 Testing

Implementation &
review
System & user manual

Figure: Gantt chart

17
2.6 Time Period

The time period should match the system life cycle. The system life cycle includes the following
important stages/phase:

a) Feasibility study
b) Design
c) Development
d) Implementation
e) Operation
f) Maintenance

Summary

Through this chapter we have discussed with methodology, which is use to implement the SDLC
and software process model, which shows the activity of software in the system. Therefore, we
must follow the SDLC that have been described above to develop our system.

18
Chapter 3

Requirement Collection and Analysis


The Software Requirement Specification Process is a document that lists out stakeholders needs
and communicates these to the technical community that will design and build this system. It
involves scoping the requirements so that it meets the customer’s need. It allows the
collaboration between the end-users who often do not have any technical knowledge and a
technical system analyst who is likely to approach the situations in technical terms.

3.1 Requirement Engineering

Requirement analysis, also called requirements engineering is the process of determining user
expectations for a new or modified product. These features called requirements must be
quantifiable, relevant and detailed. In software engineering, such requirements are often called
functional specifications. Requirements analysis is an important aspect of project management.

3.2 Requirements Engineering Process Model

We must follow all process of Requirements Engineering to develop our software.

User Feedback

User

Specification Validation
Elicitation

Problem Domain

Fig: The requirements Engineering Process Model

There are three processes in the model. They are,

19
1. Requirement Analysis/ Elicitation
2. Requirement Specification
3. Requirement Validation
In our project, we will try to fulfil many issues. As during the development of a project we can
face different issues like technical, operational and economical. In feasible study it depends on
some different area. They are-

1. Technical Feasibility
2. Economic Feasibility
3. Operational Feasibility
4. Schedule Feasibility

3.3 Technical Feasibility

A system request is technically feasible if the organization can obtain the equipment to develop,
install and operate the system. The technical needs of the system may vary considerably but
might include.

1. The facility to produce outputs in a given time


2. Response time under certain conditions
3. Ability to process a certain volume of transaction at a particular speed.
4. Facility to communicate data to distant locations.

3.4. Technical Criteria:

For this system the minimum hardware requirements are

1. PC: Intel core i3 processor.


2. RAM: 2GB
3. Keyboard
4. Mouse

For this system the software requirements are

1. OS: windows 7/8/10.


2. Database: MySQL.
3. Server: XAMP(Localhost)
4. Browser: Mozilla Firefox/ Google Chrome and more.

20
5. Platform: PHP, HTML, CSS, JavaScript.
6. Code Editor: Sublime text/php Storm

3.5. Economic Feasibility

Economic analysis is the most frequently used method for evaluating the effectiveness of a
candidate system. More commonly known as cost benefit analysis, the procedure is to determine
the benefits and saving that are expected from a candidate system and compare them with cost.

 Estimate of hardware, software, development team and training.


 Estimate of benefits from the proposed system
 Estimate the cost of needed equipment. For example: need of personal Computer.

3.6 Operationally Feasibility

Operational feasibility is a step by step process which solves problem of system and user
requirements. Operational feasibility is concerned with some topics which are-

 How the user will accept the system?


 What kind of requirements it needs?
 If the system will be able to meet the user expectation?

3.7 Schedule Feasibility

Schedule feasibility referred to a schedule time in which the system will take to develop. In other
word, it can be said that it indicates the time in which a system need to develop. It also sees if the
system will be completed in the given time by using methods for its development, if it needs
more time to complete. Schedule feasibility ensures that a system can be completed before the
system becomes unnecessary.

3.8 Testing

Software testing is an investigation conducted to provide stakeholders with information about the
quality of the product or service under test. Software testing can also provide an objective,
independent view of the software to allow the business to appreciate and understand the risks of
software implementation.

Software testing can be stated as the process of validating and verifying that a software
application:

1. meets the requirements that guided its design and development;

21
2. Works as expected, and

3. Can be implemented with the same characteristics.

The techniques for testing application are given below:

• Unit testing
• Black box testing
• White box testing

Unit Testing

This is a process of testing individual code modules before they integrated with other modules.
Unit testing being tested may be a function, subroutine, procedure or method. Units may be
relatively small groups of interrelated modules that are always executed as a group. The goal of
unit testing is to identify and fixed as many errors as possible before modules are combined into
a larger software unit. Errors become much more difficult and expensive to locate and fixed
when many modules are combined.

White Box Testing

White box testing is based on knowledge of the internal logic of an application’s code. Internal
software and code working should be known for this type of testing. Tests are based on coverage
of code statements, branches, paths, conditions.

In white box testing we can see how the system works with the input data. We have tested all of
our functions in the code and examined the operation of the function and found that it worked
properly.

Black Box Testing

Internal system design is not considered in this type of testing. Tests are based on requirements
and functionality.

22
CHAPTER 4

SOFTWARE DESIGN DESCRIPTION

4.1 SOFTWARE DESIGN DESCRIPTION


Software Design is a process by which the software requirements are translated into a
representation of software components, interfaces and data necessary for the implementation
phase. Software Design Description describes the design of subject of interest of a Computer
Software Configuration Item (CSCI). It describes the CSCI-wide design decisions, the CSCI
architectural design, and the detailed design needed to implement the software. An SDD is a
document used to specify system architecture and application design in a software related
project. The purpose of the Software Design Description is to document information that:

• Describes the functional structure, data, and algorithms to be implemented,


• Identifies required system resources,
• Can be used to assess the impact of requirements changes,
• Assist in producing test cases,
• Can be used to verify compliance with requirements

23
4.2 OVERALL DESIGN

4.2.1 Flow Chart:


A flow chart is a graphical or symbolic representation of process. The flow chart symbols
are linked together with arrows showing the process flow direction.

4.2.1.1 Flowchart for Admin:

24
Figure 3.4: Flow Chart for Admin

4.2.1.2 Flow Chart for User:

25
Figure: Flow Chart for User

26
4.2.2 Use Case Diagram
A use case is simple method which is used to identify and organize system requirements in
system analysis. This method is made up the possible sequences of interactions between the
systems and users in a particular goal.

Symbol Meaning

Actor

Use Case

System name
System Boundary

Association

Figure : Symbols of Use Case diagram

27
 Use case of Admin :

User Maintenance

Website Content Update

Payment Review

New License Check

Vehicle Registration Check


CheckbVeVerify

Ownership Change Check

License Renew Check

Log Maintenance

Figure : Use Case diagram of Admin

28
 Use case of User :

Registration

Sign In

License Payment

New License Registration

Vehicle Registration
RegistrationCheckbVeVerif
y
Ownership Change

License Renew

Log Out

Figure : Use Case diagram of User

29
4.2.3 Entity Relationship Diagram (ERD):

Figure: ERD Diagram for Driving License Management System

4.2.4 Data flow diagram (DFD):

30
A graphical representation of the flow of data though an information system is known as Data
Flow Diagram (DFD). It represents the process of our information system from the viewpoint of
the data.

System analysts use data flow diagram to design information-processing systems. DFD helps
them as a way to model whole organization.

There are four main components of data flew diagram. They are:

1) Process
2) External entities(rectangle)
3) Data stores ( two horizontal, parallel lines or sometimes an eclipse)
4) Data Flows (curved or straight line with arrowhead indicating flew direction).
4.2.5 Process or Function:

Process is transformation and manipulation of input data to produce output data.

Function

4.2.6 External Entities:

External entities sent and receive the data from the system. It represents a person, a machine, an
organization etc. that is external to the system being modelled. Flows outgoing from external
entities go to process.

Entities

4.2.7 Data Stores:

31
Data stores is the location of containing data permanently or temporarily. It can respond to
request for storing and accessing data, but cannot initiate any action.

4.2.8 Data Flows

A flow represents data in motion. It conveys data between process, external entities and data
stores.

Data Flow

4.2.9 Steps of DFD:

The steps of DFD are given below

1. Building the context diagram.


2. Creating DFD fragments for each scenario.
3. Organizing DFD fragments in level 0
4. Decomposing level 0 DFDs as needed.
5. Validating DFDs with user.

4.3.1 Level of DFD:

32
A context level DFD or 0 level DFD is the most basic form of Data Flow Diagram. It is used to
show how the entire system works at a glance. There is one process only in the system and all the
data flows either into or out this process. Context level DFD maintains the interaction between
the process and external entities. It does not contain Data Stores.

4.3.2 Level 0 DFD:

Control

Admin
Administration System

Add/Edit Info

View

Content
User

Response

Figure: Level 0 Data Flow Diagram for Driving License Management System

33
4.3.3Level 1 DFD for Admin
Content Exam Registration Payment

1.0 2.0 3.0 4.0

Manage Checking Registration Check


Content Exam info. Payment

Registration info. Payment Info.


Content Info.
Exam Info

Driving License Management System

6.0
5.0
Manage user
Manage
Requirement
Update

UserRequirement info.
Update info.

User
Update

Figure: Level 1 DFD for Admin

34
4.3.4 Level 1 DFD for User

Form Content Address NID

1.0 2.0 3.0 4.0

Fill-up Form View View View


Content Address NID

NID Info.
Form Info. Address info.
Content info.

Driving License Management System

7.0 6.0
5.0
5.0 6.0
Skill Test License issue
Giving Exam Check Result

Skill info. License info


Exam Info Result info.
Info.

Skill License
Exam Result
Info.
NnNearestNea
rest

Figure: Level 1 DFD for User

35
4.4 Activity Diagram of user:

Activity diagram is another important diagram in UML to describe the dynamic aspects of the
system. Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system. The control flow is
drawn from one operation to another. The activity diagram of user has given below:

Figure: activity diagram

36
Chapter 5
Database
 Database driving license

 Table structure for table admin:

Column Type Null Key

id int(50) No Primary

admin_name varchar(50) No

admin_pass varchar(50) No

 Table structure for table exam

Column Type Null Key

id int(100) No Primary

name varchar(100) No

written int(100) No

skill int(100) No

oral int(100) No

remarks varchar(100) No

 Table structure for table newlicense

37
Column Type Null Key

id int(100) No Primary

user_id int(110) No

father_name varchar(100) No

mother_name varchar(100) No

blood_group varchar(100) No

birthdate date No

vehicle_type varchar(100) No

profile_photo varchar(255) No

signature varchar(100) No

medical_documents varchar(255) No

job_role varchar(100) No

present_address varchar(100) No

permanent_address varchar(100) No

national_Id varchar(100) No

phone_number varchar(100) No

license_type varchar(255) No

trainer_name varchar(100) No

trainers_driving_license_number varchar(100) No

 Table structure for table oldlicense:

Column Type Null Key

id int(100) No Primary

38
user_id int(11) No

father_name varchar(100) No

mother_name varchar(100) No

blood_group varchar(100) No

birthdate date No

vehicle_type varchar(100) No

profile_photo varchar(255) No

signature varchar(255) No

job_role varchar(100) No

present_address varchar(100) No

permanent_address varchar(100) No

national_Id varchar(100) No

phone_number varchar(100) No

license_type varchar(100) No

old_license_number varchar(100) No

trainer_name varchar(100) No

trainers_driving_license_number varchar(100) No

 Table structure for table ownershipchange:

Column Type Null Key

id int(100) No Primary

old_Owner_name varchar(100) No

new_Owner_name varchar(100) No

39
old_nid int(50) No

license_type varchar(100) No

license_number int(100) No

new_nid int(100) No

vehicle_type varchar(100) No

user_id int(100) No

 Table structure for table payment:

Column Type Null Key

id int(100) No Primary

name varchar(100) No

tr_id varchar(100) No

license_type varchar(100) No

amount int(150) No

 Table structure for table user:

Column Type Null Key

id int(50) No Primary

name varchar(100) No

email varchar(100) No

pwd varchar(100) No

confirm_password varchar(100) No

40
 Table structure for table vehicle_reg:

Column Type Null Key

id int(100) No Primary

cc int(100) No

engine_no int(100) No

company_name varchar(100) No

issue_date date No

pay_slip varchar(100) No

vehicle_type varchar(100) No

Chassis_no int(100) No

CHAPTER 6
DESIGN AND IPLEMENTATION

6.1 Overview
In this chapter, we have provided the experimental result analysis of our developed system for
web application. We have provided snapshots of every step that an admin and a customer can go
through.

6.2 Graphical Representation


The obtained results for both web application are graphically showed in the next sections.

Web Application :
 UI
Driving License Management System Home page:

41
 Login:
User can login in this system.

42
 Password Recovery:

 Registration:
Registration page for new user

43
 Traffic Rules:

In this page User can learn all the traffic rules and traffic signs.

44
 Bus Rent:
Here user can find the bus rent of Chittagong and Dhaka.

 New License:

45
 Ownership Change:

46
 Vehicle Regstration:

47
 License Price:

48
 Payment:

49
Here user can pay their payment by using transaction system.

 Contact Page:

50
User can easily contact with their problems.

 Admin Sign In:

51
 Admin Index:

 Exam List:

52
 User List:

 New License List:

53
 Old License List:

 Database :

54
 Admin Table:

 User Table:

 Exam Table:

55
 New License Table:

 Ownership Change Table:

56
 Old License Table:

 Vehicle Registration Table:

57
 Payment Table:

 About Us:

Chapter 7

58
Conclusion
7.1 Introduction

“Driving License Management System” is an online based project. We introduce our transportation
sector license system to people through this system. The main aim of this project is “Save time, Money&
Harassments during License system in BRTA.”

7.2 Limitations of the Project


 User can’t search manually many things.
 This is a huge sector. So, we will trying to enrich our site with all the information about it

7.3 Future Work of the Project

Even though we tried our best to develop our system as a perfect system that came to our mind.
With our shortest experience and knowledge. We studied about BRTA problems and implement
our best. We are planning on increasing the capacity of our system by adding more features such
as-
Adding advanced searching with advanced sorting.

 Creating android apps.


 Database will be more secured.
 Adding blog from admin user.
 We will implement GPS tracking system for registered user.
 We will update our system with more new features & update.
 Provides great impression in transport sector

7.4 CONCLUSION:

It is a great achievement to work with this project. It develops our thinking skill, real life
problem solving, and communication skill. It gives us confidence to extend our thinking with
real life problems

References

59
[1] https://en.wikipedia.org/wiki/Bangladesh_Road_Transport_Authority

[2] www.brta.gov.bd

[3] Dawn Griffiths and David Griffiths : Head First Android Development, 2nd Edition

[4] Silberschatz, Korth, Sudarshan : Database System Concepts, 5th Edition

[5] Ian Sommerville, “Software Engineering”, 7th Edition, Pearson Education, 2004.

[6] Roger S. Pressman, “Software Engineering – A Practitioner’s Approach”, 5th Edition,

McGraw-Hill International Edition, 2001.

[7] Abraham Silberchatz, Henry F. Korth, S. Sudarsham, “Database System Concept”, 4th

Edition, The McGraw-Hill Companies, NY, USA, 2002.

[8] Software Design Center (2006), “How to Draw Data Flow Diagrams”, 2006,

Collected from “http://www.smartdraw.com/tutorials/software-dfd/dfd2.htm”,

[9] Software Design Center (2006), “How to draw Entity Relationship Diagrams”, 2006,

Collected from “http://www.smartdraw.com/tutorials/software-erd/erd3.htm”,

[10] Wikipedia, “Software Testing”, Collection from “http://www.w3c.org/TR/1999/RE Chtm

[11] Software DIA for diagram “http://dia-installer.de”

[12] Alan Dennis, Barbara Haley Wixom, “System Analysis and Design”, 2000.

60

Potrebbero piacerti anche