Guidelines for the preparation of Synopsis Report USE COMPUTER SCIENCE AND ENGINEERING / INFORMATION TECHNOLOGY appropriately.

The students of CS use COMPUTER SCIENCE AND ENGINEERING and the students of IT use INFORMATION TECHNOLOGY at appropriate locations every where. Synopsis should contain certificates from the company (if live project), and yourself indicating that the work is original and is not submitted elsewhere. 1. One Copy of the Synopsis is submitted to the department. 2. Report must be Spiral Bound. 3. Size and font Complete Synopsis Report including pages and chart. (i) type of font: Times New Roman (ii) Chapter heading 14 points (iii) Heading 12 point capital and bold (iv) Sub heading 12 point capital (v) Text 12 point 4. Page Margin Top Margin 1 Bottom Margin 1 Left Margin 1 Right Margin 1 5. Line Spacing 1 line 6. Paragraph Spacing 1.5 line 7. All pages (except front page and certificates) shall be numbered at bottom with center alignment. 8. Only one side of the page will be written. 9. Each new chapter will start from a new page. 10. An appendix shall be added for technology used, functions implemented etc if required. 11. Students should clearly mention what kind of testing and how is done in the project. 12. Students should carefully read their synopsis reports to remove wrong spellings, grammatical mistakes, and repetition of words, Lines or paragraph in the text. They are advised not to repeat the same text again and again just to increase the size of the chapter in their report. However giving reference is allowed. 13. The lists of the chapters with subtopics are available below. Use The Chapters and their sub topics as per your projects requirements.

Table of Contents Index Chapter 1. Introduction 1 1. 1 Aims, Objectives , Vision Chapter 2.Project / Problem Selection Chapter 3.Project Monitoring System 3.1 Gantt Chart 3.2 PERT Chart Chapter 4. System Study 4.1 Existing System along with limitations/deficiencies 4.2 Proposed system along with intended objectives 4.3 Feasibility study 4.3.1 Operational 4.3.2 Technical 4.3.3 Economic Chapter 5. System Analysis 5.1 Requirement Specification 5.2 System flowcharts 5.3 DFDs/HIPOs/ERDs 5.4 Sources of data Chapter 6. Scope of the Project Bibliography & Web References

Page No

MAJOR REPORT ON ELECTRONIC TOLL COLLECTION SUBMITTED TO RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA (M.P.)

In partial fulfillment for the requirement of VIII Sem of BACHELOR OF ENGINEERING IN INFORMATION TECHNOLOGY YEAR 2012-13 SUBMITTED BY SHIVANI GUPTA (0905IT091052) GUIDED BY SMITA DANDOTIYA Asst.Professor Deptt. of IT ITM, Gwalior (M.P)

DEPARTMENT OF INFORMATION TECHENOLOGY

INSTITUTE OF TECHONOLOGY & MANAGAMENT GWALIOR-474001

INSTITUTE OF TECHONOLOGY & MANAGAMENT GWALIOR

DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE
This is to certify that Shivani Gupta(0905IT091052), students of Bachelor of Engineering (Information Techonology) VIII semester has developed a major report on Electronic Toll Collection under the guidance of Smita Dandotiya using Java Technology for the partial fulfillment of Bachelor of Engineering (Information Techonology) and submitted a satisfactory Synopsis of the project. This work has not been submitted in part or full to this or any other university for the award of any degree or diploma to the best of my knowledge. We wish their success in the future. Rajend Singh Kushwaha Head of Department CSE/IT External Examiner Smita Dandotiya Asst.Professor Deptt. of CSE/IT ITM,Gwalior(M.P.)

Candidate Declaration

We Shivani

Gupta (0905IT091052) students of Bachelor of Engineering

(Information Techonology) VIII semester, hereby declare that we have developed this synopsis on Electronic Toll Collection. This major report is developed by us under the guidance of Ms.Smita Dandotiya. using Java Technology. We submit this synopsis report for the partial fulfillment of the VII semester of Bachelor of Engineering (Information Techonology). This work has not been submitted in part or full to this or any other university for the award of any degree or diploma to the best of our knowledge.

Shivani Gupta(0905IT091052)

Acknowlegment
We take this golden opportunity to convey our inner felt gratitude and whole hearted thanks to our esteemed project guide Yogendra Rathore, Department of CSE & IT, for his keen interest, immense guidance, valuable suggestions, excellent supervision and constant encouragement at every stage of the project work. We extend our most sincere thanks to Dr. Rajendra Singh Kushwaha, Head of the Department, and CSE & IT for providing excellent academic atmosphere which made our project a reality.

ABSTRACT

Electronic toll collection (ETC), an adaptation of military identification friend or foe technology, aims to eliminate the delay on toll roads by collecting tolls electronically. ETC determines whether the cars passing are enrolled in the program, alerts enforcers for those that are not, and electronically debits the accounts of registered car owners without requiring them to stop. In 1959, Nobel Economics Prize winner William Vickrey was the first to propose a system of electronic tolling for the Washington Metropolitan Area. He proposed that each car would be equipped with a transponder. The transponders personalised signal would be picked up when the car passed through an intersection, and then relayed to a central computer which would calculate the charge according to the intersection and the time of day and add it to the cars bill Electronic toll collection has facilitated the concession to the private sector of the construction and operation of urban freeways, as well as made feasible the improvement and the practical implementation of road congestion pricing schemes in a limited number of urban areas to restrict auto travel in the most congested areas. In the 1960s and 1970s, free flow tolling was tested with fixed transponders at the undersides of the vehicles and readers, which were located under the surface of the highway. Norway has been the world's pioneer in the widespread implementation of this technology. ETC was first introduced in Bergen, in 1986, operating together with traditional tollbooths. In 1991, Trondheim introduced the world's first use of completely unaided full-speed electronic tolling. Norway now has 25 toll roads operating with electronic fee collection (EFC), as the Norwegian technology is called (see AutoPASS). In 1995, Portugal became the first country to apply a single, universal system to all tolls in the country, the Via Verde, which can also be used in parking lots and gas stations. The United States is another country with widespread use of ETC in several states, though many U.S. toll roads maintain the option of manual collection.

1:

LITERATURE SURVEY

1.1 ELECTRONIC TOLL COLLECTOR:

Figure 1.1: Electronic toll

Electronic toll is an inter-operate-ability system allowing cashless payment at toll booths on national highways. It increases revenue, curbing leakages and ensuring smooth travel across the country. The problem without Electronic toll system is that most people have to wait in the queue of slow moving vehicles of the toll booth. Other problems include delay in reaching the destination, time wasting, and cash exchange. The main objective of E-toll project is to collect funds to finance the construction and maintenance of road network. In addition E-toll facilitates the delivery of sophisticated services based on information that the systems able to collect. The services include various things, from fleet management of private companies to directing traffic, avoiding traffic congestion or informing drivers about traffic jams and road accidents ahead of time. The E-toll system helps to avoid wasting of time. It will prove effective in tracking of stolen vehicles and cash exchange. It also avoids the delay in reaching the destination. Currently this technology is used in countries like U.S.A, Canada, Argentina, Mexico and Chile. 3

CHAPTER 2 INTRODUCTION

AIM

Electronic toll collection (ETC), an adaptation of military "identification friend or foe" technology, aims to eliminate the delay on toll roads by collecting tolls electronically. ETC determines whether the cars passing are enrolled in the program, alerts enforcers for those that are not, and electronically debits the accounts of registered car owners without requiring them to stop. OBJECTIVE

The main objective of this project is collecting toll and reduce traffic and improve service. The RFID card will be given to the user which contains the digital code, which have to the corresponding details stored in the centralized database system which can be accessed in the relevant office as and when required. Radio-frequency Identification (RFID) is an automatic identification method, relying/storing and remotely retrieving data using called RFID tags (Transporters). An RFID tag is an object that can imbibe into a product, animal, or person for the purpose of identification using radio waves. Some tags can be read from several meters and also can be used beyond the line of sight of the reader. The model developed uses an active RFID technology and wireless communicator as it helps to improve data transfer between the tag and the host database over a long distance. The main objective of this module development is to implement an automated check in and checkout in Electronic Toll collection system. Electronic toll collection system (ETC) is one of the means that have been adopted by all developed countries to solve jam problem by parking charge and improve service quality. However the system can also be used in car alarms, warehouse inventory, security access control, personnel access & tracking without the need to swipe each item individually. VISION

Project vision encompasses enabling every rental vehicle residing within an electronic toll collection system with the ability to pay for tolls automatically, whether transponder or video toll based. 4

CHAPTER 3: PROJECT/PROBLEM SELECTION

The problem without Electronic toll system is that most people have to wait in the queue of slow moving vehicles of the toll booth. Other problems include delay in reaching the destination, time wasting, and cash exchange. With the use of Electronic Toll Collector (ETC) the throughput of the system can be increased three times. For that reason, ETC systems might represent a more feasible alternative than building additional toll lanes. One of the key factors for all the ETC projects is to calculate the benefits that it might produce before the actual implementation. There is a dearth of research done in integrating all the benefits for ETC. Previous studies show that the benefits for ETC are evaluated on an individual basis. In addition, since most of these projects are relatively new, the benefit analysis has been done with less accuracy. The main objective of E-toll project is to collect funds to finance the construction and maintenance of road network. In addition E-toll facilitates the delivery of sophisticated services based on information that the systems able to collect. The services include various things, from fleet management of private companies to directing traffic, avoiding traffic congestion or informing drivers about traffic jams and road accidents ahead of time. The E-toll system helps to avoid wasting of time. It will prove effective in tracking of stolen vehicles and cash exchange. It also avoids the delay in reaching the destination. By using Electronic toll system in toll booth we will get the following benefits Increases patron convenience and safety with nonstop payment Improves traffic flow Reduces patron commute time Reduces traffic congestion Lowers patron fuel use Reduces emissions which are a major cause of pollution Reduces need for new roads Reduces operating costs for toll authorities Provides proven reliability and unparalleled accuracy

CHAPTER 4: PROJECT MONITORING SYSTEM

4.1 GANTT CHART

Jan
Analysis Synopsis Development Design Testing Filing

Feb

Mar

Apr

4.2 USECASE DIAGRAM

Registration

Autogen

Transaction

Balance

CardDetails

Admin

CHAPTER 5 SYSTEM STUDY

5.1 EXISTING SYSTEM ALONG WITH LIMITATIONS/DEFICIENCIES Exiting system is limited to Undetected Incorrect Reads referring to the incorrect read of a tag that the registration hardware or software does not catch. This scenario constitutes either a free ride for the motorist, or an undeserved fine for failure to pay which can be a hefty price. Theft the tags are, in essence, electronic money and therefore there will be motivation to steal them. Specially-designed tags that are permanently affixed to the windshield have been created to deter anyone from trying to remove it without damaging the tag. A customers account can be subjected to hackers. Job loss- attendants will be replaced with electronic tolls. 5.2 PROPOSED SYSTEM ALONG WITH INTENDED OBJECTIVES User Friendly: We have tried to come up with the project which is as much user friendly as it can. The administrator will have no problem in running the project. Security: The Project determines whether the cars passing are enrolled in the program, alerts enforcers for those that are not, and electronically debits the accounts of registered car owners without requiring them to stop.. Uniqueness: In this Project RFID tag will be a prepaid tag which will be affixed in the upper central portion of the vehicle's windscreen. It will work as a prepaid toll account and there will be automatic toll deduction when the vehicle crosses a toll plaza. The unique number of the Tag fitted on the windscreen of the vehicle would be read by the 'readers' fitted in the dedicated "ETC" lanes of these plazas, and sent to the Central Clearing House.The user will get an instant SMS alert as well as email update. The Clearing House pools the money collected electronically and later distributes among toll plaza managements as per usage by vehicles. 5.3 FEASIBILITY STUDY The feasibility study is carried out to test if the proposed system worth being implemented. Given unlimited resources and infinite time, all projects are feasible. Hence it become booty necessary and prudent to evaluate the feasibility of the project at the earliest possible time in order to avoid unnecessary wasted of time, effort and professional embarrassment over an all - conceived system. Feasibility study is a test of 8

system proposed regarding its workability, impact on the organization ability to meet us need and effective use of resources. It is usually carried out by the small group of people who are familiar with the information system technique, understand the part of the business or organization that will be involved or affected by the project, and are skilled in the System Analysis and Design process. The purpose of feasibility study is not to solve the problem but to determine if the problem is worth solving. Feasibility usually includes the following aspects: 5.3.1 OPERATIONAL It is operationally feasible in its nature also, because it is developed in Java and Ms Access of which Java provides user-friendly environment due to its features. The System will provide them automatic reporting and checks on entries while storing as well as entering. So the front end has been made user friendly for Administrator. 5.3.2 TECHNICAL The Technical issues usually raised during the feasibility stage of the investigation include these: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? Can the system be expanded if developed? Are there technical guarantees of accuracy, reliability, ease of access and data security? Processor used in this project is Intel Core i3 CPU M370 @ 2.40GHz, 3.2GB RAM. System type- 64 bit operating system. Software like Java, Ms-Access, Text pad and operating system WINDOWS-7 Home Basic were already installed on the existing computer system. So no additional hardware and software were required to purchase and it was technically feasible. The aspects of our study included the following factors. 1. FRONT-END SELECTION: It must have servlet, swing and concepts of multithreading that assists employees that are not from IT background. Scalability and extensibility. Flexibility. Robustness. According to the organization requirement and the culture.

Must provide excellent reporting features with good printing support. 9

Platform independent. Easy to debug and maintain. Event driven programming facility. Front end must support some popular back end like SQL Server.

According to the above stated features we selected JDK as the front-end for developing our project. 2. BACK-END SELECTION: Ms-Access Multiple user support. Efficient data handling. Provide inherent features for security. Efficient data retrieval and maintenance. Stored procedures. Popularity. Operating System compatible. Easy to install. Various drivers must be available. Easy to implant with the Front-end.

According to above stated features we selected Ms-Access as the backend. The technical feasibility is frequently the most difficult area encountered at this stage. It is essential that the process of analysis and definition be conducted in parallel with an assessment to technical feasibility. It centers on the existing computer system (hardware, software etc.) and to what extent it can support the proposed system. The technical requirement for our proposed system is economic and it does not use any other additional Hardware and software.

5.3.2

ECONOMIC Economic feasibility is the study of both whether or not the technology can be afforded and whether it is cost-effective, meaning the benefits out weight the costs. The proposed system is economically feasible because the cost involved in purchasing the hardware and the software are within approachable. The personal cost like salaries of employees hired are also nominal, because working in this system need not required a highly qualified professional.. The less time involved also helped in its economical feasibility. 10

CHAPTER 6: SYSTEM ANALYSIS

6.1 REQUIREMENT SPECIFICATION

i.

Hardware Specification Processor : Pentium 4 or Later. Memory : 1 GB RAM. Hard disk : 160 GB. RFID(Radio frequency indentifier) Kit

ii.

Software Specification

Operating System : Windows XP/7/8. Front End DataBase : Java, Servlet, Swing. : Ms-Access.

11

6.2 FLOWCHART

START B

READ RTC

SUFFICIENT BALANCE? No

CONFIGURE KEYPAD

Yes Enter password to recharge card

Update the same to EEPROM for that CARD particular

Keep reading rfid reader

12 6.3 DFDS/HIPOS/ERDS Data Flow Diagram The Data flow Diagram shows the flow of data. It is generally made of symbols given below: (1) A square shows the Entity: (2) (3) (4) A Circle shows the Process: An open Ended Rectangle shows the data store: -An arrow shows the data flow:-

The DFD can be up to several levels. The 0 level DFD states the flow of data in the system as seen from the outward in each module. The first level DFD show more detail, about the single process of the 0 level DFD The second level DFD can show even more details and so on.

13

DFD 0

Registration

Registered user have transaction

Transaction n

Have

Generate Card No Have

Update Balance

Autogen

Card Details

Balance

14

DFD 1

Registration

Process to store data

Autogen

RFID Device

cid Tid
Registration Database
Cid
Process to Generate ID

Transaction

Process to store data

Transaction Database
Update Balance

Get ID when car Passes

Balance Database

Deduce Balance

CarDetails

15 Entity Relationship Diagram An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database. ER diagrams often use symbols to represent three different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes. Entity Relationship (ER) diagram: This diagramming technique is used to visually present a database schema or data model and was original proposed by Chen in the 1970s. There are many different data modeling notations; some are very similar to UML class diagrams (with the exception of operations). However, the notation the used here is slightly different, as proposed by Elmasri, et al. The database schema for this system is shown in figure. The table object has been left out of the diagram because the table management feature set had been dropped from the requirements before this stage of the design process. Some important database design decisions are as follows: _ To store the total price of an order with the order rather than calculating it on the fly when looking at past orders. This is because the price of menu items could change at any time, so the total price at the time of ordering must be stored so that the total price is not incorrectly calculated in future. _ Similar to the previous point, the order receipt is stored as a hard-copy and not regenerated when reviewing past orders because things such as the restaurant name or VAT percentage are subject to change. Receipts stored need to be exactly the same as the customer copy in case of dispute.

16 ER DIAGRAM

Cust-id

Cname V-type

Reg_No

Registration

Licenno

Cust-id

Tran-id

Have

Autogen

Have Add Balance Cust-id Rech_dat e Tran-id

Transaction

Balance

Cardno

Amount

Balance Cardno

Cust-id

17 MODEL USED ITERATIVE MODEL An iterative life cycle model does not attempt to start with a full specification of requirements. Instead, development begins by specifying and implementing just part of the software, which can then be reviewed in order to identify further requirements. This process is then repeated, producing a new version of the software for each cycle of the model. For example:

In the diagram above when we work iteratively we create rough product or product piece in one iteration, then review it and improve it in next iteration and so on until its finished. Diagram of Iterative model:

Advantages of Iterative model: In iterative model we can only create a high-level design of the application before we actually begin to build the product and define the design solution for the entire product. Later on we can design and built a skeleton version of that, and then evolved the design based on what had been built. In iterative model we are building and improving the product step by step. Hence we can track the defects at early stages. This avoids the downward flow of the defects. In iterative model we can get the reliable user feedback. When presenting sketches and blueprints of the product to users for their feedback, we are effectively asking them to imagine how the product will work. In iterative model less time is spent on documenting and more time is given for designing. Disadvantages of Iterative model: Each phase of an iteration is rigid with no overlaps. 18

Costly system architecture or design issues may arise because not all requirements are gathered up front for the entire lifecycle.

When to use iterative model: Requirements of the complete system are clearly defined and understood. When the project is big. Major requirements must be defined; however, some details can evolve with time.

TESTING USED WHITE BOX TESTING White box testing is used to test areas that cannot be reached from a black box level. White box testing (a.k.a. clear box testing, glass box testing or structural testing) uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. The tester chooses test case inputs to exercise paths through the code and determines the appropriate outputs. In electrical hardware testing, every node in a circuit may be probed and measured; an example is in-circuit testing (ICT). Since the tests are based on the actual implementation, if the implementation changes, the tests probably will need to change too. For example ICT needs updates if component values change, and needs modified/new fixture if the circuit changes. This adds financial resistance to the change process, thus buggy products may stay buggy. Automated optical inspection (AOI) offers similar component level correctness checking without the cost of ICT fixtures; however changes still require test updates. While white box testing is applicable at the unit, integration and system levels of the software testing process, it is typically applied to the unit. While it normally tests paths within a unit, it can also test paths between units during integration, and between subsystems during a system level test. Though this method of test design can uncover an overwhelming number of test cases, it might not detect unimplemented parts of the specification or missing requirements, but one can be sure that all paths through the test object are executed.

19

CHAPTER 8 SYSTEM DESIGN 8.1 SNAPSHOT

Admin Login

20

Registration

Customer Details

21

Customer Details Updation

Customer Details Deletion

22

Transaction Details

Transaction Updation

23

Transaction Deletion

24

CHAPTER 9 SCOPE OF PROJECT Some extensions that can be made to this research are as follows: 1. Though these are the major benefits, incorporation of other benefits like the reduction in incident sat the toll plaza due to the ETC implementation would give a more comprehensive benefit model.

2. Incorporate the value of the increased reliability due to the ETC system the reliability of the travel time is increased due to the ETC deployment and it has an impact on the value of travel time. The estimation of this factor would give better estimate of the travel time savings. 3. Study the effects of other delay models on the travel time and delay estimation Delay model used for this research was from the Highway Capacity Manual 2000. A model more specific to toll plaza would give better estimate for the waiting times at the manual and automatic lanes. 4. Develop a dynamic system for ETC conversion. In the current research, the number of ETC lanes and their time of implementation are decided based on the delays at the ETC lane and the value of the benefits. Thus an algorithm can be developed to decide upon the optimum number of ETC lanes as compared to the manual and automatic lanes and also take into account the lane type that needs to be converted in order to maximize the benefits and reduce the delays at the toll plaza.

Bibliography & Web References

1. Ariponnammal, S. and Natarajan, S. (1994) Transport Phonomena of Sm Sel X Asx, Pramana Journal of Physics Vol.42, No.1, pp.421-425. 2. 3. 4. 5 Barnard, R.W. and Kellogg, C. (1980) Applications of Convolution Operators to Problems in Univalent Function Theory, Michigan Mach, J., Vol.27, pp.8194. Shin, K.G. and Mckay, N.D. (1984) Open Loop Minimum Time Control of Mechanical Manipulations and its Applications, Proc.Amer.Contr.Conf., San Diego, CA, pp. 1231-1236. www.google.com .wikipedia 25

REFERENCES

1. Ariponnammal, S. and Natarajan, S. (1994) Transport Phonomena of Sm Sel X Asx, Pramana Journal of Physics Vol.42, No.1, pp.421-425. 2. Barnard, R.W. and Kellogg, C. (1980) Applications of Convolution Operators to Problems in Univalent Function Theory, Michigan Mach, J., Vol.27, pp.8194. Shin, K.G. and Mckay, N.D. (1984) Open Loop Minimum Time Control of Mechanical Manipulations and its Applications, Proc.Amer.Contr.Conf., San Diego, CA, pp. 1231-1236.

3.

Name Address and Email: 1.Nishigandha Khandait Thaipur Gwalior(M.P), nishi199100@gmail.com

26