VEHICLE MANAGEMENT SYSTEM
- 2. Introduction System to the web Scope and Objective Methodology Modules System Design Conclusion OVERVIEW
- 3. System To the Web
- 4. Vehicle Management System is proposed with the intention of upgrading the current stand-alone system to a web based or online system . Proposed to smoothen the management process of the vehicle in order to handle the registration and scrapping it. This stand alone concept to web based system, it helps staffs to store and manage data efficiently and in more organized manner. System also accept information about the accident report, So that none of the accident goes unattained. Introduction
- 6. To register and keep the information about all vehicles. To build up a system that provides and generates the summary Report from the database records in order to get the whole view about the vehicles amounts. Summarize the accidental records and responds for the further improvements. A web based tool where user can search for additional information of the vehicle. Scope & Objective of the Project
- 8. The approach depends on the formalized requirement and on both the general project plan. Different tool and method are used to complete the project . Various software’s, tool, and techniques are used for effective design and development of the system in efficient way. i. Selection ii. Activities iii. Tools used iv. Scheduling Methodology
- 9. A. Selection Problem occurred in the currently used manual and lengthy system inspired me to select such project title. B. Activities Planning of the Project, Scheduling, Analysis of the project, Designing and development of the project. C. Tool used Database: MySQL IDE: NETBEANS Platform: Windows D. Scheduling It is the tool that communicates what work needs to be performed or resources of the organization will perform the work and the timeframes in which that work needs to be performed.
- 10. Modules- Admin, Guest, Vehicles, Details
- 11. Introduction A Software requirements specification (SRS) is a comprehensive description of the intended purpose and environment for software under development. SRS defines how an application will interact with system hardware, other programs & human user in a wide variety of real world situations. i. Functional Requirement ii. Non-Functional requirement iii. Specifications of actors Requirement Specifications
- 12. 1. Functional Requirement Interface of the system, the services and feature of the system. User can check whether the system provides the services according to the requirement that they proposed. 2. Specification of actors Administrator An administrator is the one who preforms the back-end tasks like adding entries. Customers Customer is the person who has limited privileges.
- 13. Non-functional Requirement Usability User interface will be user friendly, So user can familiar to the system and easy to use. Reliability The system will be able to meet specified objectives as well as the expectations of the customers. Performance The system should provide the services in considerable time interval. Security The information provider by the user should be authentic which protect the system from external attack and spamming.
- 14. E-R Diagram
- 15. Introduction The Design phase focuses how to build the business needs that includes the process of system design, database and graphical user interface design. Project Significance This system facilitate the staff in keeping all the vehicle information. User can also get information about their vehicle tax payment details upon request or in subscription. System proposed to build up the complete vehicle database providing every solution. Systemdesign, and Implementation
- 16. System Overview
- 17. THE VEHICLE MANAGEMENT SYSTEM PROPOSED TO MAKE EASY PROCESS OF MANAGING VEHICLE WITH THE OBJECTIVE TO REPLACE THE CURRENT APPROACH. Conclusion