Description
Add to wishlist
1.1 Introduction
The main purpose of this project is to satisfy all lacking activities in existing system, save time and make traffic system more efficient and effective using better technologies. Smart Traffic System is Useful for traffic police and for the citizens. Traffic administrator can track activities of Police men and citizens. Citizens can get record about violation tickets.
STS User Guideline App for Citizen
https://play.google.com/store/apps/details?id=com.fleeksoft.sts.trafficguideline&hl=en
STS Client App for Traffic Police
https://play.google.com/store/apps/details?id=com.suh.itboy.stsclient&hl=en
Features
1.4 Main Modules
Basic modules of our project (STS) are as follows:-
- Records of traffic police members.
- Records of traffic violation tickets.
- Records of violators.
- Records of Traffic Accidents
- Communication between traffic police men and traffic administrator.
- Real-time reports to traffic administrator.
- Duty Scheduling
- Real-time Duty Monitoring
- Traffic news and updates.
- Payment on the spot
- Person and vehicle verification.
- Notification Management.
- Reports Management.
- Guidelines for Citizens
- Citizen Voilation Rdcord
- Citizen Vehical Record
- Route Alternate for Citizens
Problem in Existing System
We have traditional manual system of issuing traffic violation tickets. Police man issue traffic violates ticket manually and user got a receipt and brings it to bank for pay fine. It has become more critical for citizens to pay fine if there is no bank near. Existing system don’t have computerized record of traffic activities. There is no computerized record of violation tickets and user himself can’t see his violation records. Traffic administrator hasn’t perfect way to track location of traffic police men. Administrator and police man cannot directly communicate with one another.
Tools and Technologies
- HTML/CSS/POLYMER/JAVASCRIPT
- PHP/MYSQL
- PHPStorm / Dreamweaver/MYSQL Workbench
- XML/JSON
- Xampp
- Android Studio
- SDK/JDK
- Genymotion/Blue stack
- Adobe Photoshop
2.1.1 Functional Requirements
List of all functional requirements of proposed system are as follows.
2.1.1.1 Functional Requirements for Admin:
FR1: Admin can login into system.
FR2: Admin can insert, edit, delete and view client’s records.
FR3: Admin can view violation record of citizens.
FR4: Admin can add and search ticket.
FR5: Admin can view accident records.
FR6: Admin can view vehicle and violators records.
FR7: Admin can view, print and download real-time reports of records.
FR8: Admin can schedule and monitor client duties.
FR9: Admin can communicate with clients.
FR10:Admin can create news or updates.
2.1.1.2 Functional Requirements for Client:
FR11: Client can login to system
FR12: Client can view his profile.
FR13: Client can edit his profile.
FR14: Client can communicate with admin.
FR15: Client can add tickets.
FR16: Client can view violation record
FR17: Client can add news.
2.1.1.3 Functional Requirements for Citizen:
FR18: Citizen can view guideline.
FR19: Citizen can view his/her violation record.
FR20: Citizen can view his/her Vehicle Record.
FR21: Citizen can view alternative path.
