3 Driving License Management

CHAPTER THREE
1 PROPOSED SYSTEM
1.1 Introduction
In this chapter, requirements of the software system are defined through human natural language
and use case. The document is provided in order to ensure that the software we produce will be
consistent with the need of the system’s user. Stating these requirements explicitly helps ensure
that any potential miscommunications are corrected at early stage. Detailing System
Requirements is the initial step of constructing the whole software system. It is a description of
the project requirements that we have been gather and analyze. The goal of this document is to
gather and analyze and give an in-depth insight of the system by defining the current system
problem statement in detail.
1.2 Purpose of the system

The proposed of the system is to create a web-based system that enables the daily manual form
of work to be automatically set. The system is secured as well as there are different types of roles
that are controlled by administrator by entering the login password and user name which is
assigned to him/her by the administrator he/she can get the service intended. This makes the
system secure and it also has got different roles so that they can delete, edit, create as well as see
the detail information. The system adopts existing forms but it will have many improvements in
regard to the data collected from the customer and employee.
The system will basically store every detail of students (trainee) and the subjects that are related
to them. It also has basic functionalities like to register trainee online which only can be done
manually by the training center. The proposed system also has report forms.
The other part of the project is which check legality and renewal of the driving license will
control by traffic police. The users can also get general information about tariff and traffic
symbols (sign). The transport agency can give appointment to exam date and give permission for
training institution to start training.
Page | 1
1.3 Overview of proposed system
License Certificate Training Institute are one of the major parts for managing driving licenses
files and its part of work is registering new trainee. So that driving certificate trainee
management system is design to provide fast and easy way of controlling all above activities. It
is also used to communicate with transport offices using the web, keep the data for the longest
time for reference.
Our proposed system provides an easy way for traffics online checking of legality of license.
And also, for transport office to Control all license files. This includes accepting seeing notice
from training center, posting new happenings deleting updating and inserting new driving license
files. The system also provides an easy way for institutes having drivers to check the legality of
license simply viewing by using the web page.
Generally, driving license management system is concerned on managing driving license,

providing easy and understandable way of controlling the activities of training institutes for
driving certificate providers and making easy and fast of communication held between traffic
polices, drivers, transport office and certificate providers.
1.4 Functional requirement

Functional requirements consist of a specification of a function that the system must support in
this section we discuss what is our web-based system is expected to do. The type of user in this
system is trainee (user), traffic polices and transport agency and administrator.
As a trainee:
 The system should enable customer to register online.

 The system should enable customer access information about car accident and
placard.
 The system should enable customer access traffic signs (symbol) and transportation
tariff.
As Training institute Manager:
 The system should enable the manager record customer information.
Page | 2
 The system should enable manager to delete, update and add and remove trainee
(customer) data.
 The system should enable manager to send and request information with transport
agency.
 The system should generate report.
As Traffic police:
 The system should enable traffic police to check legality and renewal of driving
license.
 The system should generate daily report.
 The system should enable traffic police to access general information.
As Transport agency/admin:
 The system should enable admin to manage training center (institute) data (update,
delete).
 The system should enable admin to manage account (add, remove, modify).
 The system should enable admin to view and send request information with training
institute.
 The system should enable admin to view reports.
1.5 Non-functional requirement

This section provides a detailed description of how the system should behave all inputs into and
outputs from the system. Non-functional requirements may include using specific hardware
platform for the system, security requirements, how the system should deal with failures and
faults, and how to provide backward compatibility with an old system that the client is unwilling
to retire. Therefore, some of the non-functional requirement that needs to be met in order for the
proposed system to operate or done correctly can be:
 Control and Security: This system uses different security systems to protect its data.
Among this: Password and user name. The system users are allowed to perform
activities or make a modification to the data if and only if they are authorized which
will be checked by their username, password, and account type.
Page | 3
 Performance: The amount of time needed to get the response for a transaction or
request is minimized and also the system has fast response time because of a light
weighted code in HTML, PHP, CSS and JavaScript.
 Portability: This system is portable, since it runs on different desktop platforms.

Running on different platforms in desktop computer browser makes the system
accessible by users.
 Availability: The system is available in the presence of Extranet connection. So, the
users of system can access the system successfully for provide different services but
the exam is taken periodically.
 Reliability: The system should handle invalid inputs and displays error message to
users. Reliability is one feature of the system significantly validates user inputs.
 Backups: In addition to authorizing access to users, the system could have problems
in such areas of data crime, disaster, and human errors. For this purpose, incremental
backup copies (copies of only the challenge to files) and full backup copies (copies
of all files) will be made and stored in a secured location.
 Usability: The system has an interactive and attractive GUI which eases users’ usage
problem. It needs simple training. Because it is easy to use and adapt.
1.5.1 User Interface and Human Factors

The new system shall be more users friendly and the user of the new system is any one with
minimal knowledge Internet usage, functionality of the system should be more usable by using
user understandable signs. Training should be given for the system administrators and a user
guide manual should be prepared
1.5.2 Hardware consideration

The system will be deployed in a dedicated Apache web server and the database will be resided
on a separate database server. Requires computer, internet connection, electric power and
scanner. The device can be a mobile phone or a tablet with capability of wireless
communication.
Page | 4
1.5.3 Security Issues of the system
Security objectives will be done by using login username and password for each users and
members. User information like password should be stored in the database in encrypted form.
Although it may not able to fully enhancing the security purpose, but it can prevent unauthorized
login.
For instance, normal users are not allowed to view report except manager or admin due to reports
is considered as private and confidential. All data are stored in databases and admin keeps
backup so if system crashed or get damaged, it can restore soon.
1.5.4 Performance Characteristics

Use responsive page layout uses both relative units and media queries. As the browser increases
or decreases in width, a responsive layout will flexible. The button used in the page should be
easy.
 Efficiency: The proposed system must have 3 second response time and 10 second
response time in the worst case.
 Effectiveness: More effective when compared to the manual approach, resulting in
fast accomplishment of task with in some amount of time.
 Response Time: The output should be generated within a maximum of 5 seconds
depending on the internet connection speed and peak hours of the Internet usage in
case of tracking.
 Interoperability: it can work with web-based applications developed using PHP and
java script.
 Capacity: When we come to the capacity of our System can serve users.
 Resource Utilization: The application utilizes minimum amount of CPU and
memory of the device.
 Extensibility: Adding features and carry-forward of customizations at next major
version upgrade.
Page | 5
1.5.5 Error Handling and Extreme Conditions
For every systems error are assumed to occurred, it is not possible to avoid errors rather
minimize, errors can be coursed by different factors, it can be from the user side or unhandled
bugs in the software.
The new system should manage exceptions and handle it in java while the user enters incorrect
input. If any of those exceptions occur, the system will provide a feedback to the user by
displaying error message with notification for the user in clear and understandable way.
1.5.6 Quality Issues of the System

When the clients are using this web-based system, they may find something, which needs
improvement and efficiency, or they may have their own appreciation about the application. So
we will provide them with a page to fill it and from the feedback we collect, the system can be
improved as they need.
Availability: the system should be available for all user when they need it.
Reliability: the system should not fail more than once in a year.
Usability: the system that we develop should be easy to learn and operate. It will need only one
day free training to give the users knowledge about how to use the system, the significance of the
system.
1.5.7 System modifications

As the world is capable of change from time to time; there will be future change to the system as
a result of new technology invention. The future new technology will be invented so in our
system upgrades to make it compatible to future technology. System is a summation of simple
modules that focuses to perform specific task. So, the updating or editing is easy rather than
studying the whole parts.
1.5.8 Physical environment

The system can be affected by the physical environment a power loss and loss of internet
connection can affect the system. External conditions such as weather condition will not have
any effect on the performance of the system.
Page | 6
1.5.9 Resource Issues of the system
Server
The minimum hardware requirement for MySQL is-
 CPU: 32 bit or 64 bits

 Cores: AMD Dual-core processor C70
 RAM: 2GB (or higher is recommended)
 Display resolution 1366x768(or lower is recommended)
Client
 Web browser
 Graphics and interface tools to load display
 Internet connection
Page | 7

3 Driving License Management

Uploaded by

Copyright:

Available Formats

3 Driving License Management

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3 Driving License Management

Uploaded by

Copyright:

Available Formats

CHAPTER THREE

1.2 Purpose of the system

Generally, driving license management system is concerned on managing driving license,

1.4 Functional requirement

 The system should enable customer to register online.

As Training institute Manager:

 The system should enable the manager record customer information.

1.5 Non-functional requirement

 Portability: This system is portable, since it runs on different desktop platforms.

1.5.1 User Interface and Human Factors

1.5.2 Hardware consideration

1.5.4 Performance Characteristics

1.5.6 Quality Issues of the System

1.5.7 System modifications

1.5.8 Physical environment

The minimum hardware requirement for MySQL is-

 CPU: 32 bit or 64 bits

You might also like