Screenshot Notes

i
CONTENTS
Page No
Acknowledgement i
Preface ii
1. Introduction
1.1 Project Overview……………………………………………....1
1.2 Project Description…………………………………………….1
1.3 Definitions, Acronyms, and Abbreviations……………………2
2. Problem Definition
2.1 Disadvantages………………………………………………....3
2.2 Proposed System .…………………………………………….3
2.3 Product Functions……………………………………………..4
2.4 User Characteristics……………………………………………4
2.5 Constraints……………………………………………………..5
2.6 System Study…………………………………………………..5
2.7 Assumptions and Dependencies……………………………….5

3. Feasibility Study
3.1 Technical Feasibility…………………………………… …..6
3.2 Operational Feasibility……………………………………….7
3.3 Economic Feasibility………………………………………...7
3.4 Interfaces……………………………………………………..7
3.5 Hardware Requirements……………………………………...8
3.6 Software Requirements……………………………………....8
4. System Analysis
4.1 Software Requirement Specification(SRS)…………………10
4.2 Communication Interfaces………………………………..…11
4.3 Memory Constraints………………………………………...11
4.4 Operations…………………………………………………...11
4.5 Site Adaptation Requirements………………………………12
4.6 Functional Requirements……………………………………12
4.6.1 Performance Requirements…………………………12
4.6.2 Assumptions and Dependencies…………………….12
5. ER Diagram
5.1 Why we use ER diagram? ……………………………….......13

5.2 Components of ER diagram………………………………….13
5.3 ER Diagrams Symbols and Notations………………………..14
5.4 ER Diagram for Toll Tax Management System………….......16
6.Table of Contents
6.1 Table creation…………………………………………………17
6.2 Dumping Data for Table ‘contacthome’………………………17
6.3 Add Toll Gate………………………………………………….17
6.4 Feedback Messages……………………………………………18
6.5 Staff Dashboard………………………………………………..19
7. Project designing
7.1 Home Page……………………………………………………..20
7.2 Admin login……………………………………………………20
7.3 Dashboard………………………………………………………21
7.4 Admin Profile…………………………………………………..21
7.5 Add Stop………………………………………………………..22
7.6 Manage Staff……………………………………………………22
7.7 Staff login……………………………………………………….23
7.8 Staff profile……………………………………………………...23

7.8.1 Book Toll gate…………………………………………….24
7.8.2 Manage Toll gate………………………………………….24
8. Summary and Conclusion
8.1 Summary…………………………………………………………25
8.2 Conclusion……………………………………………………….25
9. References………………………………………………………………………26
Cricket Stadium Management System
Dept of CSE,RRCE 2020-2021



PREFACE
With the fast development of computer technology, the software projects are growing and
complexity. Software experts have recently sought to develop a more systematic and
formal approach in the design, development and implementation of their software. This
new approach has become necessary because the traditional methods of system
development often yielded software characterized by late diversity, costliness,
unreliability, and non-maintainability and non-use ability.
In this new age of computing everything has been computerized, so how can we become
isolate and untouched from this environment. That’s why keeping this thing in mind and
an opportunity or probably a creativity to do such a task different and unique from others,
we thought a way to develop this software.
Toll gate Automation and Vehicle Tracking is designed to automatically keep track of the
vehicle’s movement, record the time and the details like Owner’s name, date of registration,
vehicle model etc. This system is very useful for automatic vehicle tracking, time
management and for automation of Toll gate. This paper explains the implementation of Toll
Gate Automation which is a step towards improving the tracking monitoring of vehicles,
traveling in predetermined routes. In this system, a computerized system automatically
identifies an approaching vehicle and records the vehicle number and Time.
VISVESVARAYA TECHNOLOGICAL UNIVERSITY
“Jnana Sangama”, Belagavi - 590018
A DBMS MINI PROJECT REPORT ON
“TOLL TAX MANAGEMENT SYSTEM”
Submitted in the partial fulfilment of the requirement for the fifth semester of
BACHELOR OF ENGINEERING
In
COMPUTER SCIENCE & ENGINEERING
By
SHEETAL C(1RR21CS147)
Under the guidance of
Prof. Pushpalatha G
Assistant Professor
Dept. of CSE, RRCE
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

RAJARAJESWARI COLLEGE OF ENGINEERING
MYSORE ROAD, BANGALORE-560074
(An ISO 9001:2008 Certified Institute)
(2023-2024)
RAJARAJESWARI COLLEGE OF ENGINEERING
MYSORE ROAD, BANGALORE-560074
(An ISO 9001:2008 Certified Institute)
(Affiliated to Visvesvaraya Technological University, Belgaum)
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

CERTIFICATE
Certified that the mini project work entitled
“TOLL TAX MANAGEMENT SYSTEM”
carried out By
The student of “Rajarajeswari College of Engineering” in partial fulfillment for the fifth semester
of Bachelor of Engineering in Computer Science & Engineering of the Visvesvaraya
Technological University, Belagavi during the year 2023-2024. It is certified that all
corrections/suggestions indicated for Internal assessment have been incorporated in the report
deposited in the department library. The mini project report has been approved as it satisfies the
academic requirements in respect of mini project work prescribed for the fifth semester
…………………………... …………………………
Signature of Guide Signature of HOD
[Prof. Pushpalatha G] [Dr. Usha S]
Assistant Professor, Dept. Of CSE Prof. & HOD, Dept. of CSE
RRCE, Bangalore RRCE, Bangalore
External Viva-Voce
Name of the examiners Signature with date
1. 1.
2. ______________________ 2. ______________________
ACKNOWLEDGMENT
On successful completion of my project, I would like to place on record my sincere

thanks and gratitude to the concerned people, whose suggestions and words of
encouragement have been valuable.
I express my heartfelt gratitude to RajaRajeswari College of Engineering, for giving us the

opportunity to pursue a Degree of Computer Science Engineering and helping us to shape
our career. I take this opportunity to thank Dr.A.C. Shanmugam, Chairman,RRCE, and
Dr.R Balakrishna , Principal, RRCE for their support and encouragement to pursue this
project. I would like to thank Dr. Usha S, Professor and Head, Dept. of Computer
Science Engineering, for her support and encouragement.
I would like to thank our guide Prof. Pushpalatha G, Assistant Professor, Dept. of
Computer Science Engineering, who has been the source of inspiration throughout our
project work and has provided us with useful information at every stage of our project.
I am thankful to all the teaching and non-teaching staff of the Department of Computer
Science Engineering for their help in the successful completion of my project.
I would like to thank my parents and all my friends who gave me a constant source of
inspiration and supported me in development of this project.
Name & USN
i
Toll Tax Management System
Chapter 1 -INTRODUCTION
1.1 Project Overview

Toll Tax Management System is a web based application that can provide
all the information related to toll plazas and the passenger checks in and
pays the amount, then he/she will be provided by a receipt. With this receipt
he/she can leave the toll booth without waiting for any verification call.
1.2 Project Description

The advent of computer Technology has brought relief to repetitive tasks and has helped in
the better management and origination of data. Information management system can be
applied to any system that facilitates storage, management and retrieved of data and
information required for some particular application within a computer system. This makes it
easier for data to be handled or managed.
This project is based on the RDBMS technology. The main objective of this
project is to computerize the manual system & reduce the time consumption.
In other words we can say that our project has the following objectives:
➢ Make all the system computerized.

➢ Reduce time consumption.
➢ Reduce error scope.
➢ All system managements are automated.
➢ Centralized database management.
Here we are going to see some points regarding to purpose and scope behind
choosing this topic & what is the requirement of this type of the project in our
day to day life.
➢ Avoid the fuel loss.
➢ Saving of time in collecting toll.
➢ Avoid financial loss.
➢ To monitor the traffic
1
1.3. Definitions, Acronyms, and Abbreviations
SRS: System Requirement Specification

WWW: World Wide Web.
MySQL: is a RDBMS based on SQL which is used for adding, removing, and
modifying information in the database.
RDBMS: Relational Database Management System
HTML: Hypertext Markup Language
PHP: Hypertext Preprocessor
CSS: Cascading Style Sheet
HTTP: Hypertext Transfer Protocol
2
Chapter 2 -Problem Definition
2.1 Disadvantages
➢ High cost
➢ Privacy concerns
➢ Dependency on technology
➢ Resistance to change
➢ Equity issues
➢ Maintenance challenges
2.2. Proposed System:
The proposed toll tax management system aims to streamline toll collection operations and
enhance overall efficiency through the implementation of advanced technology and robust
management practices. Here are the key components of the proposed system:
➢ Electronic Toll Collection (ETC)

➢ Real-Time Monitoring and Analytics
➢ Multi-Channel Payment Options
➢ User-Friendly Interfaces:
Advantages:
➢ Efficient revenue collection
➢ Traffic management
➢ Transparency and accountability
➢ Data analysis
➢ Environmental impact
➢ Customer service
3
2.3. Product Functions

The website will allow access only to authorized users with specific roles (Administrator-
maintains the website, Company-Register the passengers, Passenger-Fills the details).
Following are the System Functions:
Customer role:
On the register form, customer should enter all their detail such as their name, Email,
password
and contact number.
Administration role
The system administrator must be able to: add, update and modify matches and view the
customer details.
2.4. User Characteristics
End Users
All specific knowledge or skills are required from the feeder.
➢ Educational level: Users should be comfortable with the English language.

➢ Skills: Users should have basic knowledge and should be comfortable
Administrator
Administrator must be capable to manage user rights.
This system will not take care of any virus problem, which might occur either on the Client or
the server system. Avoiding the use of pirated software and ensuring that floppies and other
removable media are scanned for viruses before use could minimize the possibility of viral
infection.
4
2.5. Constraints
The Information of all users, subjects and allocations must be stored in a database that is
accessible by every connected system. MySQL used for database.
➢ Users may access from any system connected to the online database.
➢ Users must have their correct usernames and passwords to enter into their
accounts.
2.6. System Study
System Study is a detailed study of the various operations performed by a system and their
relationships within and outside of the system. Here the key question is- what all problems
exist in the present system? What must be done to solve the problem? Analysis begins when a
user or manager begins a study of the program using existing system. System study can be
categorized into four parts.
⮚ System planning and initial investigation
⮚ Proposed System with objectives
2.7. Assumptions and Dependencies
The Software needs the following third party products-
➢ Adobe Dreamweaver for development of project.

➢ MYSQL for database connectivity.
Although basic password authentication and role based security mechanisms will be used to
protect OPMS from unauthorized access; functionality such as email notifications are
assumed to be sufficiently protected under the existing security policies applied by the
University network team. Redundant Database is setup as the role of backup Database
Server when primary database is failure.
5
Chapter 3 - Feasibility Study
Preliminary investigation examines project feasibility. The likelihood the system will be useful
to the organization. The main objective of the feasibility study is to test the Technical,
Operational and Economical feasibility for adding new modules and debugging old running
system. All system is feasible if they are unlimited resources and infinite time. There are
aspects in the feasibility study portion of the preliminary investigation:
➢ Technical Feasibility
➢ Operation Feasibility
➢ Economic Feasibility
3.1. Technical Feasibility
The technical issue usually raised during the feasibility stage of the investigation includes the
following:
➢ Does the necessary technology exist to do what is suggested?

➢ Does the proposed equipment have the technical capacity to hold the data
required to use the new system?
➢ Will the proposed system provide adequate response to inquiries, regardless of
the number or location of users?
➢ Can the system be upgraded if developed?
➢ Are there technical guarantees of accuracy, reliability, ease of access and data
security?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation

System’. The current system developed is technically feasible. It is a web based user
interface for audit workflow at NIC-CSD. Thus, it provides an easy access to the users.
The database’s purpose is to create, establish and maintain a workflow among various
entities to facilitate all concerned users in their various capacities or roles. Permission to the
users would be granted based on the roles specified. Therefore, it provides the technical
guarantee of accuracy, reliability and security.
6
3.2. Operational Feasibility
Proposed projects are beneficial only if they can be turned out into information system. That
will meet the organization’s operating requirements. Operational feasibility aspects of the
project are to be taken as an important part of the project implementation. Some of the
important issues raised are to test the operational feasibility of a project includes the
following:
➢ Is there sufficient support for the management from the users?

➢ Will the system be used and work properly if it is being developed and
implemented?
➢ Will there be any resistance from the user that will undermine the possible
application benefits?
This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the
management issues and user requirements have been taken into consideration. So, there is no
question of resistance from the users that can undermine the
possible application benefits.
3.3. Economic Feasibility
A system can be developed technically and that will be used if installed must still be a good
investment for the organization. In the economic feasibility, the development cost in creating
the system is evaluated against the ultimate benefit derived from the new systems.
Financial benefits must equal or exceed the costs.
3.4. Interfaces
In computing, an interface is a shared boundary across which three separate components of

computer system exchange information.
User interfaces
The application will have a user friendly and menu based interface.
7
3.5. Hardware Requirements:
1. Personal computer with at least

• Atleast 4GB of RAM.
• Atleast Hard disk (256GB, 512GB .etc.
• Atleast Processor 2.7GHZ.
2. Printer.
3.6. Software Requirements:

• Sublime , Notepad.
• Xampp server.
• Adobe Photoshop.
• Google chrome , Firefox , Internet Explorer.

• Bootstrap Framework.
• Microsoft word for project documentation.
• MYSQL.
• HTML.
• PHP.
Server side - An Apache Web server will accept all requests from the client. A development
database will be hosted locally (using MySQL); the production database is hosted centrally.
8
MY-SQL (BACKEND)
MySQL in July 2013, it was the world's second most widely used RDBMS, and the most
widely used open-source client server model RDBMS. It is named after cofounder Michael
Widenius's. The SQL abbreviation stands for Structured Query Language. The MySQL
development project has made its source code available under the terms of the GNU General
Public License, as well as under a variety of proprietary agreements
Apache
The Apache HTTP Server is web server software notable for playing a key role in the initial
growth of the World Wide Web. In 2009 it became the first web server software to surpass
the 100 million web site milestone. Apache is developed and maintained by an open
community of developers under the auspices of the Apache Software Foundation. Since April
1996 Apache has been the most popular HTTP server software in use.
9
Chapter 4-System Analysis
System Analysis is a detailed study of the various operations performed by a system and their
relationships within and outside of the system. Here the key question is- what all problems
exist in the present system? What must be done to solve the problem? Analysis begins when
a user or manager begins a study of the program using existing system.
4.1. Software Requirement Specification (SRS)

The software used in this application are:
• Sublime , Notepad.
• Xampp server.
• Adobe Photoshop.
• Google chrome , Firefox , Internet Explorer.

• Bootstrap Framework.
• Microsoft word for project documentation.
• MYSQL
• HTML.
• PHP.
Introduction
Purpose: The main purpose for preparing this document is to give a general insight into the
analysis and requirements of the existing system or situation and for determining the
operating characteristics of the system.
Scope: This Document plays a vital role in the development life cycle (SDLC) and it
describes the complete requirement of the system. It is meant for use by the developers and
will be the basic during testing phase. Any changes made to the requirements in the future
will have to go through formal change approval process.
10
Developer’s responsibilities overview:
The developer is responsible for:
➢ Developing the system, which meets the SRS and solving all the requirements of the
system
➢ Demonstrating the system and installing the system at client's location after the
acceptance testing is successful.
➢ Submitting the required user manual describing the system interfaces to work on it
and also the documents of the system.
➢ Maintaining the system for a period of one year after installation.
4.2. Communication Interfaces
The HTTP protocol will be used to facilitate communications between the client and server.
The system supports Google Chrome and Mozilla Firefox web browsers.
4.3. Memory Constraints
Minimum memory of 512MB is required to run the exe file without any lags. This
constraint does not possess an issue now a days as the minimum present RAM in a common
system is 1GB. At least 512 MB RAM and 5 MB space on hard disk will be required for
running the program.
4.4. Operations
The normal and special operations required by the user such as:
⮚ The various modes of operations in the user organization
⮚ Periods of interactive operations and periods of unattended operations
⮚ Data processing support functions
⮚ Backup and recovery operations
11
4.5. Site Adaptation Requirements

There should no site adaptation requirement since the Web Application Server was setup.
4.6. Functional Requirements
It deals with the functionalities required from the system which are as follows:
➢ This application is to facilitate the department in maintaining the

repositories of the report about the toll tax collected at a specific
time period.
➢ To provide details about contracts, contractors of Toll Tax
Department
To provide Toll Tax Rates of different vehicles.
4.6.1. Performance Requirements
This subsection specifies numerical requirements placed on the software or on the human
interaction with the software, as a whole Numerical requirements will include: 300
terminals will be supported at a time
4.6.2. Assumptions and Dependencies
The Software needs the following third party products-

➢ Adobe Dreamweaver for development of project.
➢ MYSQL for database connectivity.
Although basic password authentication and role based security mechanisms will be used to
protect OPMS from unauthorized access; functionality such as email notifications are
assumed to be sufficiently protected under the existing security policies applied by the
University network team. Redundant Database is setup as the role of backup Database
Server when primary database is failure.
12
Dept of CSE, RRCE 2023-24
Chapter 5 -ER Diagram
ER Diagram stands for Entity Relationship Diagram, also known as ERD is a diagram that
displays the relationship of entity sets stored in a database. In other words, ER diagrams help
to explain the logical structure of databases. ER diagrams are created based on three basic
concepts: entities, attributes and relationships.
ER Diagrams contain different symbols that use rectangles to represent entities, ovals to
define attributes and diamond shapes to represent relationships.
At first look, an ER diagram looks very similar to the flowchart. However, ER Diagram
includes many specialized symbols, and its meanings make this model unique. The
purpose of ER Diagram is to represent the entity framework infrastructure.
5.1 Why use ER Diagrams?

Here, are prime reasons for using the ER Diagram
⮚ Helps you to define terms related to entity relationship modeling
⮚ Provide a preview of how all your tables should connect, what fields are going to be on
each table
⮚ Helps to describe entities, attributes, relationships
⮚ ER diagrams are translatable into relational tables which allows you to build databases
quickly
⮚ ER diagrams can be used by database designers as a blueprint for implementing data in

specific software applications
⮚ The database designer gains a better understanding of the information to be contained in

the database with the help of ERP diagram
⮚ ERD Diagram allows you to communicate with the logical structure of the database users
13
5.2 Components of the ER Diagram
This model is based on three basic concepts:

⮚ Entities
⮚ Attributes
⮚ Relationships
5.3 ER Diagrams Symbols & Notations
Entity Relationship Diagram Symbols & Notations mainly contains three basic symbols
which are rectangle, oval and diamond to represent relationships between elements, entities
and attributes. There are some sub-elements which are based on main elements in ERD
Diagram. ER Diagram is a visual representation of data that describes how data is related to
each other using different ERD Symbols and Notations.
Following are the main components and its symbols in ER Diagrams:
⮚ Rectangles: This Entity Relationship Diagram symbol represents entity types
⮚ Ellipses : Symbol represent attributes
⮚ Diamonds: This symbol represents relationship types
⮚ Lines: It links attributes to entity types and entity types with other relationship types
⮚ Primary key: attributes are underlined
⮚ Double Ellipses: represent multi-valued attributes
14
15
5.4 ER Diagram for Toll Tax Management System
16
Chapter 6 – Table of Contents
6.1 Table Creation
CREATE TABLE `contacthome` (

ìd` int(10) NOT NULL,
`name` varchar(20) NOT NULL,
èmail` varchar(20) NOT NULL,
`subject` varchar(50) NOT NULL,
`message` varchar(200) NOT NULL,
`date` timestamp NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
6.2 Dumping data for table `contacthome`
INSERT INTO `contacthome` (ìd`, `name`, èmail`, `subject`, `message`, `date`) VALUES
(2, 'Navaneeth', 'admin@gmail.com', 'enquiry ', 'Hello sir, How can i get Monthly Pass.',
'202208-18 10:47:06'),
(3, 'Tejas', 'admin@gmail.com', 'enquiry ', 'hello sir,', '2022-08-18 11:03:53');
6.3 ADD TOLL GATE
include('includes/dbconnection.php'); if
(strlen($_SESSION['ttmsaid']==0)) {
header('location:logout.php');
} else{
if(isset($_POST['submit']))
{
$catname=$_POST['catname'];
$address=$_POST['tolladdress'];
$query=mysqli_query($con, "insert into tbltollgate(TollGateName,Address)

value('$catname','$address')");
if ($query) { echo '<script>alert("Toll Gate Details has been
added.")</script>'; echo "<script>window.location.href ='add-toll-
gate.php'</script>";
}
17
6.4 FEEDBACK MESSAGES
<!DOCTYPE HTML>
<html>
<head>
<title>Toll Tax Management System || View Feedback Messages</title> <script
type="application/x-javascript"> addEventListener("load", function() {
setTimeout(hideURLbar, 0); }, false); function hideURLbar(){ window.scrollTo(0,1); }
</script>

<link href="css/bootstrap.min.css" rel='stylesheet' type='text/css' />

<link href="css/style.css" rel='stylesheet' type='text/css' />
<link href="css/font-awesome.css" rel="stylesheet">

<script src="js/jquery.min.js"></script>

<link href='http://fonts.googleapis.com/css?family=Roboto:400,100,300,500,700,900'
rel='stylesheet' type='text/css'>


<script src="js/bootstrap.min.js"></script>
</head>
18
6.5 STAFF DASHBOARD
<html>
<head>
<title>Toll Tax Management System || Dashboard</title>
<script type="application/x-javascript"> addEventListener("load", function() {
setTimeout(hideURLbar, 0); }, false); function hideURLbar(){ window.scrollTo(0,1); } </script>

<link href="css/bootstrap.min.css" rel='stylesheet' type='text/css' />

<link href="css/style.css" rel='stylesheet' type='text/css' />

<link href="css/lines.css" rel='stylesheet' type='text/css' />
<link href="css/font-awesome.css" rel="stylesheet">

<script src="js/jquery.min.js"></script>

<link href='http://fonts.googleapis.com/css?family=Roboto:400,100,300,500,700,900'
rel='stylesheet' type='text/css'>

19
Chapter 7 – Project Designing
7.1 Home Page
7.2 Admin login
20
7.3 Dashboard
7.4 Admin profile
21
7.5 Add staff
7.6 Manage staff
22
7.7 Staff login
7.8 Staff profile
23
7.8.1 Book toll ticket
7.8.2 Manage toll ticket
24
Chapter 8-Summary and Conclusion
8.1 SUMMARY
According to our topic TOLL TAX MANAGEMENT SYSTEM, it involves designing and
implementing a database to manage toll tax collection and related operations efficiently.
Thus it includes:
- Efficient revenue collection
- Traffic management
- Improved accountability
- Enhanced security
- Data analysis and planning
- Customer service
- Environmental impact
- Revenue forecasting
8.2 CONCLUSION:
The project titled as Toll Tax Management System was deeply studied and
analyzed to design the code and implement. It was done under the guidance of
the experienced project guide. All the current requirements and possibilities
have been taken care during the project time. Toll Tax management system is
used for daily operations in any organization to maintain or access toll related
information for internal administration purposes.
25
Chapter 9 –References
1.Ramakrishnan R. & Gehrke J. (2011). Database management systems, Boston; McGraw-

Hill.
2.Database systems concepts. Estados Unidos: McGraw-Hill Companies, Inc.
3.For PHP
 https://www.w3schools.com/php/default.asp
 https://www.sitepoint.com/php/
 https://www.php.net/
4.For MySQL
 https://www.mysql.com/
 http://www.mysqltutorial.org
5.For XAMPP
 https://www.apachefriends.org/download.html
26

Screenshot Notes

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Screenshot Notes

Uploaded by

Document Information

Original Title

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

Screenshot Notes

Uploaded by

Copyright:

Available Formats

i

1.1 Project Overview……………………………………………....1

1.2 Project Description…………………………………………….1

1.3 Definitions, Acronyms, and Abbreviations……………………2

2.2 Proposed System .…………………………………………….3

2.3 Product Functions……………………………………………..4

2.4 User Characteristics……………………………………………4

2.6 System Study…………………………………………………..5

2.7 Assumptions and Dependencies……………………………….5

3.1 Technical Feasibility…………………………………… …..6

3.2 Operational Feasibility……………………………………….7

3.3 Economic Feasibility………………………………………...7

3.5 Hardware Requirements……………………………………...8

3.6 Software Requirements……………………………………....8

4.1 Software Requirement Specification(SRS)…………………10

4.2 Communication Interfaces………………………………..…11

4.3 Memory Constraints………………………………………...11

4.5 Site Adaptation Requirements………………………………12

4.6 Functional Requirements……………………………………12

4.6.1 Performance Requirements…………………………12

4.6.2 Assumptions and Dependencies…………………….12

5.1 Why we use ER diagram? ……………………………….......13

5.3 ER Diagrams Symbols and Notations………………………..14

5.4 ER Diagram for Toll Tax Management System………….......16

6.1 Table creation…………………………………………………17

6.2 Dumping Data for Table ‘contacthome’………………………17

6.3 Add Toll Gate………………………………………………….17

6.4 Feedback Messages……………………………………………18

6.5 Staff Dashboard………………………………………………..19

7.1 Home Page……………………………………………………..20

7.2 Admin login……………………………………………………20

7.4 Admin Profile…………………………………………………..21

7.5 Add Stop………………………………………………………..22

7.6 Manage Staff……………………………………………………22

7.7 Staff login……………………………………………………….23

7.8 Staff profile……………………………………………………...23

7.8.2 Manage Toll gate………………………………………….24

8. Summary and Conclusion

Dept of CSE,RRCE 2020-2021

Dept of CSE,RRCE 2020-2021

Dept of CSE,RRCE 2020-2021

“Jnana Sangama”, Belagavi - 590018

A DBMS MINI PROJECT REPORT ON

“TOLL TAX MANAGEMENT SYSTEM”

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

“TOLL TAX MANAGEMENT SYSTEM”

Signature of Guide Signature of HOD

[Prof. Pushpalatha G] [Dr. Usha S]

Assistant Professor, Dept. Of CSE Prof. & HOD, Dept. of CSE

RRCE, Bangalore RRCE, Bangalore

On successful completion of my project, I would like to place on record my sincere

I express my heartfelt gratitude to RajaRajeswari College of Engineering, for giving us the

Name & USN

1.1 Project Overview

1.2 Project Description

➢ Make all the system computerized.