An e-commerce application that enables two types of users to use the digitized way for toll-tax bill pay settlements. Admin is a user who has authority to create and delete an operator and on the other hand users as operators keep track of vehicle details and generate bills.

1. DIGITAL TOLL TAX SYSTEM
Presented by
Amit Kumar Saha
Sumanta Mete
Subrata Mahata
Sudip Mondol
IT
DEPARTMENT
GOVT. COLLEGE OF ENGINEERING &TEXTILE
TECHNOLOGY,SERAMPORE

2. ACKNOWLEDGEMENT
In completing this project we have been fortunate to have help,
support and encouragement from many people. We would like to
thank them for their cooperation.
First, we would like to thank our mentor Mr. Mainak Basu Roy, for
guiding us through each and every step of the process with
knowledge and support.
Thank you for your advice, guidance and assistance.

3. CONTENTS
• Overview of the project
• Objectives
• Recommended Software requirements.
• Software interface
• Hardware Requirements
• Hardware interface
• Functional Requirements
• Non-Functional Requirements
• Data-Flow-Diagram.
• E-R Diagram.
• Database- Structure.
• Snapshots of project.
• Testing
• Future Scope.
• Conclusion
• References

4. OVERVIEW OF THE PROJECT
• A E-commerce application, a windowed app where users can enter
their required information and retrieve if needed.
• Depending on the context, it’s been names as ‘DIGITIZED TOLL-TAX’.
• User facilities
 A fresh user must sign up to create an account
 One has to log in using account information to access his working
domain and entry tax related details.
 Once entered details, can not be updated.
 Admin has the authorization to include operator.
 Admin has a unique authentication id and password.
 Operator can be deleted from database if needed.
 Once bill printed, can not be updated.
 Vehicle detail along with the location is mandatory.

5. OBJECTIVE
• Making the TOLL-TAX entry in DIGITIZED way and more effective.
• Better operator management through admin safely.
• Providing user the scope to easily handle a Pay-Bill generation through
simple GUI much quicker.
• To ensure the database details more safe through storing in form of
tables.

6. RECOMMENDED SOFTWARE REQUIREMENTS
Operating system : windows 7
Framework : AWT with SWT
Application software : Netbeans IDE 7.4 or higher
Programming language : java(swing)
Database : ORACLE
Technology : java
Web Server : NA

7. SOFTWARE INTERFACE
USER
• Windows 7 or above
• Swing Framework(SWT)
• ORACLE
• JDBC driver connectivity

8. HARDWARE REQUIREMENT
USER
• Intel Pentium IV or above
• 2 GB RAM or above
• 10 GB hard disk or above

9. HARDWARE INTERFACE
USER
• Intel Pentium IV or above
• 2 GB RAM
• 10 GB or above memory space

10. FUNCTIONAL REQUIREMENTS
• Creating Operator
 A new operator must have to sign up initially to get access to his
new working profile. Old users can log in directly with their user Id
and password. Admin has total control over operator details.
• Deleting Operator
 Admin can delete operator database if one is suspended or not
needed anymore.
• Entering Vehicle Details
 Operator has to make a TOLLTAX related detail about a type of
vehicle(2/3/4 wheeler).
• Generating of BILLs
 After entering all detail operator has to make a bill as a printable
format to make a hard copy of it.

11. NON-FUNCTIONAL REQUIREMENTS
• The system is an Windowed Frame Application.
• This is Browser Independent.
• This is Network independent.

12. DFD - CONTEXT DIAGRAM

13. DFD – LEVEL 1 OF ADMIN

14. DFD – LEVEL 1 OF OPERATOR

15. ENTITY RELATIONSHIP DIAGRAM

16. DATABASE STRUCTURE
USER TABLE

17. DATABASE STRUCTURE
CAR DETAIL TABLE

18. DATABASE STRUCTURE
BILL DETAILTABLE

19. SNAPSHOTS OF PROJECT
HERE ARE SOME SNAPSHOTS OF
DIGITIZED TOLL-TAX

20. WELCOME PAGE

21. ADMIN PAGE

22. ADMIN ACTION

23. CREATE OPERATOR

24. DELETE OPERATOR

25. OPERAOTOR LOGIN

26. OPERATOR ACTION

27. VEHICLE TYPE SELECTION

28. VEHICLE DETAIL

29. BILL GENERATOR

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

31. TEST CASES OF SafeDrop

32. TEST CASES OF SafeDrop

33. FUTURE SCOPE
The interaction procedure of user and the offline frame application can
be further more improved to make it interactive and user friendly .The
frame layout may be improved .we are trying to upgrade it into a
advanced DIGITIZED app as well as a e-TOLLTAX manager with network
interface so that more users can be attracted .We think more flexibility
and interactive features can make it more bigger.

34. CONCLUSION
After developing the application we have got a clear idea on java swing
app development, especially in AWT and Swing features, got a clear idea
on how a digitized database generation takes place. We have come to
know the pros & cons of java AWT with swing components, the scopes of it
and how it differs from other developed app techniques. I hope, in future,
the experience will help us in developing any Swing application in further
future in our career.

35. REFERENCES
LIST OF USEFUL WEBSITES
http://examples.oreilly.com/jswing2/code/
http://zetcode.com/tutorials/javaswingtutorial/basicswingcomponents/
https://en.wikipedia.org/wiki/Abstract_Window_Toolkit
https://en.wikipedia.org/wiki/Swing_(Java)