- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Vehicle Management System Activity Diagram
This is the Activity UML diagram of Vehicle Management System which shows the flows between the activity of Customer, Vehicle Type, Vehicle, Driver, Booking. The main activity involved in this UML Activity Diagram of Vehicle Management System are as follows:
- Customer Activity
- Vehicle Type Activity
- Vehicle Activity
- Driver Activity
- Booking Activity
Features of the Activity UML diagram of Vehicle Management System
- Admin User can search Customer, view description of a selected Customer, add Customer, update Customer and delete Customer.
- Its shows the activity flow of editing, adding and updating of Vehicle Type
- User will be able to search and generate report of Vehicle, Driver, Booking
- All objects such as ( Customer, Vehicle Type, Booking) are interlinked
- Its shows the full description and flow of Customer, Driver, Booking, Vehicle, Vehicle Type
Login Activity Diagram of Vehicle Management System:
This is the Login Activity Diagram of Vehicle Management System, which shows the flows of Login Activity, where admin will be able to login using their username and password. After login user can manage all the operations on Vehicle, Customer, Vehicle Type, Booking, Driver. All the pages such as Vehicle Type, Booking, Driver are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Vehicle Management System. The various objects in the Booking, Vehicle, Customer, Vehicle Type, and Driver page—interact over the course of the Activity, and user will not be able to access this page without verifying their identity.
- Posted By: freeproject
- Comments: 0
Vehicle Management System Class Diagram
Vehicle Management System Class Diagram describes the structure of a Vehicle Management System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Vehicle Management System are Vehicle, Driver, Fuel, Vehicle History, Booking, Vehicle Type.
Classes of Vehicle Management System Class Diagram:
- Vehicle Class : Manage all the operations of Vehicle
- Driver Class : Manage all the operations of Driver
- Fuel Class : Manage all the operations of Fuel
- Vehicle History Class : Manage all the operations of Vehicle History
- Booking Class : Manage all the operations of Booking
- Vehicle Type Class : Manage all the operations of Vehicle Type
Classes and their attributes of Vehicle Management System Class Diagram:
- Vehicle Attributes : vehicle_id, vehicle_customer_id, vehicle_number, vehicle_type, vehicle_description
- Driver Attributes : driver_id, driver_name, driver_mobile, driver_email, driver_username, driver_password, driver_address
- Fuel Attributes : fuel_id, fuel_vehicle_id, fuel_name, fuel_expences, fuel_type, fuel_description
- Vehicle History Attributes : vehicle_history_id, vehicle_history_name, vehicle_history_type, vehicle_history_description
- Booking Attributes : booking_id, booking_vehicle_id, booking_title, booking_type, booking_date, booking_description
- Vehicle Type Attributes : vehicle_type_id, vehicle_type_customer_id, vehicle_type_number, vehicle_type_description
Classes and their methods of Vehicle Management System Class Diagram:
- Vehicle Methods : addVehicle(), editVehicle(), deleteVehicle(), updateVehicle(), saveVehicle(), searchVehicle()
- Driver Methods : addDriver(), editDriver(), deleteDriver(), updateDriver(), saveDriver(), searchDriver()
- Fuel Methods : addFuel(), editFuel(), deleteFuel(), updateFuel(), saveFuel(), searchFuel()
- Vehicle History Methods : addVehicle History(), editVehicle History(), deleteVehicle History(), updateVehicle History(), saveVehicle History(), searchVehicle History()
- Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
- Vehicle Type Methods : addVehicle Type(), editVehicle Type(), deleteVehicle Type(), updateVehicle Type(), saveVehicle Type(), searchVehicle Type()
Class Diagram of Vehicle Management System :
- Posted By: freeproject
- Comments: 0
Vehicle Management System Component Diagram
This is a Component diagram of Vehicle Management System which shows components, provided and required interfaces, ports, and relationships between the Vehicle Type, Driver, Customer, Booking and Vehicle. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Vehicle Management System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Vehicle Management System:
- Vehicle Type Component
- Driver Component
- Customer Component
- Booking Component
- Vehicle Component
Featues of Vehicle Management System Component Diagram:
- You can show the models the components of Vehicle Management System.
- Model the database schema of Vehicle Management System
- Model the executables of an application of Vehicle Management System
- Model the system's source code of Vehicle Management System
- Posted By: namita
- Comments: 0
Vehicle Management System Dataflow Diagram
Vehicle Management System Data flow diagram is often used as a preliminary step to create an overview of the Vehicle without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Vehicle process. It contains all of the userflow and their entities such all the flow of Vehicle, Driver, Oil, Vehicle History, Booking, Vehicle Type, Customer. All of the below diagrams has been used for the visualization of data processing and structured design of the Vehicle process and working flow.
Zero Level Data flow Diagram(0 Level DFD) of Vehicle Management System :
This is the Zero Level DFD of Vehicle Management System, where we have eloborated the high level process of Vehicle. It’s a basic overview of the whole Vehicle Management System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Booking,Vehicle Type and Customer showing the system as a single high-level process, with its relationship to external entities of Vehicle,Driver and Oil. It should be easily understood by a wide audience, including Vehicle,Oil and Booking In zero leve DFD of Vehicle Management System, we have described the high level flow of the Vehicle system.High Level Entities and proccess flow of Vehicle Management System:
- Managing all the Vehicle
- Managing all the Driver
- Managing all the Oil
- Managing all the Vehicle History
- Managing all the Booking
- Managing all the Vehicle Type
- Managing all the Customer
First Level Data flow Diagram(1st Level DFD) of Vehicle Management System :
First Level DFD (1st Level) of Vehicle Management System shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the Vehicle Management System system as a whole. It also identifies internal data stores of Customer, Vehicle Type, Booking, Vehicle History, Oil that must be present in order for the Vehicle system to do its job, and shows the flow of data between the various parts of Vehicle, Oil, Vehicle Type, Customer, Booking of the system. DFD Level 1 provides a more detailed breakout of pieces of the 1st level DFD. You will highlight the main functionalities of Vehicle.Main entities and output of First Level DFD (1st Level DFD):
- Processing Vehicle records and generate report of all Vehicle
- Processing Driver records and generate report of all Driver
- Processing Oil records and generate report of all Oil
- Processing Vehicle History records and generate report of all Vehicle History
- Processing Booking records and generate report of all Booking
- Processing Vehicle Type records and generate report of all Vehicle Type
- Processing Customer records and generate report of all Customer
Second Level Data flow Diagram(2nd Level DFD) of Vehicle Management System :
DFD Level 2 then goes one step deeper into parts of Level 1 of Vehicle. It may require more functionalities of Vehicle to reach the necessary level of detail about the Vehicle functioning. First Level DFD (1st Level) of Vehicle Management System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Customer, Vehicle Type, Booking, Vehicle History, Oil, Driver, Vehicle.Low level functionalities of Vehicle Management System
- Admin logins to the system and manage all the functionalities of Vehicle Management System
- Admin can add, edit, delete and view the records of Vehicle, Oil, Booking, Customer
- Admin can manage all the details of Driver, Vehicle History, Vehicle Type
- Admin can also generate reports of Vehicle, Driver, Oil, Vehicle History, Booking, Vehicle Type
- Admin can search the details of Driver, Booking, Vehicle Type
- Admin can apply different level of filters on report of Vehicle, Vehicle History, Booking
- Admin can tracks the detailed information of Driver, Oil, Vehicle History, , Booking
- Posted By: freeproject
- Comments: 0
Vehicle Management System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Vehicle Management System Entity. The entity-relationship diagram of Vehicle Management System shows all the visual instrument of database tables and the relations between Driver, Vehicle History, Vehicle, Vehicle Type etc. It used structure data and to define the relationships between structured data groups of Vehicle Management System functionalities. The main entities of the Vehicle Management System are Vehicle, Driver, Fuel, Vehicle History, Booking and Vehicle Type.
Vehicle Management System entities and their attributes :
- Vehicle Entity : Attributes of Vehicle are vehicle_id, vehicle_customer_id, vehicle_number, vehicle_type, vehicle_description
- Driver Entity : Attributes of Driver are driver_id, driver_name, driver_mobile, driver_email, driver_username, driver_password, driver_address
- Fuel Entity : Attributes of Fuel are fuel_id, fuel_vehicle_id, fuel_name, fuel_expences, fuel_type, fuel_description
- Vehicle History Entity : Attributes of Vehicle History are vehicle_history_id, vehicle_history_name, vehicle_history_type, vehicle_history_description
- Booking Entity : Attributes of Booking are booking_id, booking_vehicle_id, booking_title, booking_type, booking_date, booking_description
- Vehicle Type Entity : Attributes of Vehicle Type are vehicle_type_id, vehicle_type_customer_id, vehicle_type_number, vehicle_type_description
Description of Vehicle Management System Database :
- The details of Vehicle is store into the Vehicle tables respective with all tables
- Each entity ( Vehicle Type, Fuel, Booking, Driver, Vehicle) contains primary key and unique keys.
- The entity Fuel, Booking has binded with Vehicle, Driver entities with foreign key
- There is one-to-one and one-to-many relationships available between Booking, Vehicle History, Vehicle Type, Vehicle
- All the entities Vehicle, Booking, Fuel, Vehicle Type are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Vehicle Management System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Vehicle Management System Sequence Diagram
This is the UML sequence diagram of Vehicle Management System which shows the interaction between the objects of Booking, Customer, Vehicle Type, Driver, Vehicle. The instance of class objects involved in this UML Sequence Diagram of Vehicle Management System are as follows:
- Booking Object
- Customer Object
- Vehicle Type Object
- Driver Object
- Vehicle Object
Login Sequence Diagram of Vehicle Management System:
This is the Login Sequence Diagram of Vehicle Management System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Vehicle Type, Booking, Customer, Vehicle, Driver. All the pages such as Customer, Vehicle, Driver are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Vehicle Management System. The various objects in the Vehicle, Vehicle Type, Booking, Customer, and Driver page—interact over the course of the sequence, and user will not be able to access this page without verifying their identity.
This is the UML sequence diagram of Vehicle Management System which shows the interaction between the objects of Booking, Customer, Vehicle Type, Driver, Vehicle. The instance of class objects involved in this UML Sequence Diagram of Vehicle Management System are as follows:
- Booking Object
- Customer Object
- Vehicle Type Object
- Driver Object
- Vehicle Object
- Posted By: freeproject
- Comments: 0
Vehicle Management System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Vehicle Management System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Vehicle Management System. The main actors of Vehicle Management System in this Use Case Diagram are: Super Admin, System User, Dealer, Customer, who perform the different type of use cases such as Manage Vehicle, Manage Driver, Manage Oil, Manage Vehicle History, Manage Booking, Manage Vehicle Type, Manage Customer, Manage Users and Full Vehicle Management System Operations. Major elements of the UML use case diagram of Vehicle Management System are shown on the picture below.
The relationships between and among the actors and the use cases of Vehicle Management System:
- Super Admin Entity : Use cases of Super Admin are Manage Vehicle, Manage Driver, Manage Oil, Manage Vehicle History, Manage Booking, Manage Vehicle Type, Manage Customer, Manage Users and Full Vehicle Management System Operations
- System User Entity : Use cases of System User are Manage Vehicle, Manage Driver, Manage Oil, Manage Vehicle History, Manage Booking, Manage Vehicle Type, Manage Customer
- Dealer Entity : Use cases of Dealer are Add Vehicle, Create Booking, Create Quotations, Collect Payment
- Customer Entity : Use cases of Customer are Book Vehicle, View Invoices, Make Payment
Use Case Diagram of Vehicle Management System :
