Car Sharing System UML Diagram

Posted By freeproject on March 18, 2018

Car Sharing System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Car Sharing System which shows the flows between the activity of Memebership, Cra, Customer, Booking, Destination. The main activity involved in this UML Activity Diagram of Car Sharing System are as follows:

  • Memebership Activity
  • Cra Activity
  • Customer Activity
  • Booking Activity
  • Destination Activity

Features of the Activity UML diagram of Car Sharing System

  • Admin User can search Memebership, view description of a selected Memebership, add Memebership, update Memebership and delete Memebership.
  • Its shows the activity flow of editing, adding and updating of Cra
  • User will be able to search and generate report of Customer, Booking, Destination
  • All objects such as ( Memebership, Cra, Destination) are interlinked
  • Its shows the full description and flow of Memebership, Booking, Destination, Customer, Cra
Car Sharing System Activity Diagram

Car Sharing System Class Diagram

Posted By freeproject on August 2, 2017

Car Sharing System Class Diagram describes the structure of a Car Sharing System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Car Sharing System are Booking, Customer, Payment, Car History,, Insurance, Memebership.

Classes of Car Sharing System Class Diagram:

  • Booking Class : Manage all the operations of Booking
  • Customer Class : Manage all the operations of Customer
  • Payment Class : Manage all the operations of Payment
  • Car History, Class : Manage all the operations of Car History,
  • Insurance Class : Manage all the operations of Insurance
  • Memebership Class : Manage all the operations of Memebership

Classes and their attributes of Car Sharing System Class Diagram:

  • Booking Attributes : booking_id, booking_title, booking_type, booking_ticket, booking_date, booking_description
  • Customer Attributes : customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Payment Attributes : payment_id, payment_customer_id, payment_date, payment_bill, payment_type, payment_description
  • Car History, Attributes : car_history_id, car_history_customer_id, car_number, car_history_company car_history_type, car_history_description
  • Insurance Attributes : insurance_id, insurance_bike_id, insurance_number, insurance_date, insurance_expiry, insurance_amount, insurance_type, insurance_description
  • Memebership Attributes : membership_id, membership_customer_id, membership_name, membership_type, membership_description

Classes and their methods of Car Sharing System Class Diagram:

  • Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
  • Customer Methods : addCustomer(), editCustomer(), deleteCustomer(), updateCustomer(), saveCustomer(), searchCustomer()
  • Payment Methods : addPayment(), editPayment(), deletePayment(), updatePayment(), savePayment(), searchPayment()
  • Car History, Methods : addCar History,(), editCar History,(), deleteCar History,(), updateCar History,(), saveCar History,(), searchCar History,()
  • Insurance Methods : addInsurance(), editInsurance(), deleteInsurance(), updateInsurance(), saveInsurance(), searchInsurance()
  • Memebership Methods : addMemebership(), editMemebership(), deleteMemebership(), updateMemebership(), saveMemebership(), searchMemebership()

Class Diagram of Car Sharing System :

Class Diagram Image: 
Car Sharing System Class Diagram

Car Sharing System Component Diagram

Posted By freeproject on February 8, 2018

This is a Component diagram of Car Sharing System which shows components, provided and required interfaces, ports, and relationships between the Payment, Booking, Destination, Customer and Insurance. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Car Sharing System UML component diagram, describes the organization and wiring of the physical components in a system.

Components of UML Component Diagram of Car Sharing System:

  • Payment Component
  • Booking Component
  • Destination Component
  • Customer Component
  • Insurance Component

Featues of Car Sharing System Component Diagram:

  • You can show the models the components of Car Sharing System.
  • Model the database schema of Car Sharing System
  • Model the executables of an application of Car Sharing System
  • Model the system's source code of Car Sharing System
Component Diagram: 

Car Sharing System Dataflow Diagram

Posted By freeproject on April 14, 2017

Car Sharing System Data flow diagram is often used as a preliminary step to create an overview of the Car without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Car process. It contains all of the userflow and their entities such all the flow of Booking, Customer, Payment, Insurance, Car History, Memebership, Destination. All of the below diagrams has been used for the visualization of data processing and structured design of the Car process and working flow.


Zero Level Data flow Diagram(0 Level DFD) of Car Sharing System :

This is the Zero Level DFD of Car Sharing System, where we have eloborated the high level process of Car. It’s a basic overview of the whole Car Sharing System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Car History,Memebership and Destination showing the system as a single high-level process, with its relationship to external entities of Booking,Customer and Payment. It should be easily understood by a wide audience, including Booking,Payment and Car History In zero leve DFD of Car Sharing System, we have described the high level flow of the Car system.

High Level Entities and proccess flow of Car Sharing System:

  • Managing all the Booking
  • Managing all the Customer
  • Managing all the Payment
  • Managing all the Insurance
  • Managing all the Car History
  • Managing all the Memebership
  • Managing all the Destination
Zero Level DFD Car Sharing System

First Level Data flow Diagram(1st Level DFD) of Car Sharing System :

First Level DFD (1st Level) of Car Sharing 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 Car Sharing System system as a whole. It also identifies internal data stores of Destination, Memebership, Car History, Insurance, Payment that must be present in order for the Car system to do its job, and shows the flow of data between the various parts of Booking, Payment, Memebership, Destination, Car History 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 Car.

Main entities and output of First Level DFD (1st Level DFD):

  • Processing Booking records and generate report of all Booking
  • Processing Customer records and generate report of all Customer
  • Processing Payment records and generate report of all Payment
  • Processing Insurance records and generate report of all Insurance
  • Processing Car History records and generate report of all Car History
  • Processing Memebership records and generate report of all Memebership
  • Processing Destination records and generate report of all Destination
First Level DFD Car Sharing System

Second Level Data flow Diagram(2nd Level DFD) of Car Sharing System :

DFD Level 2 then goes one step deeper into parts of Level 1 of Car. It may require more functionalities of Car to reach the necessary level of detail about the Car functioning. First Level DFD (1st Level) of Car Sharing System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Destination, Memebership, Car History, Insurance, Payment, Customer, Booking.

Low level functionalities of Car Sharing System

  • Admin logins to the system and manage all the functionalities of Car Sharing System
  • Admin can add, edit, delete and view the records of Booking, Payment, Car History, Destination
  • Admin can manage all the details of Customer, Insurance, Memebership
  • Admin can also generate reports of Booking, Customer, Payment, Insurance, Car History, Memebership
  • Admin can search the details of Customer, Car History, Memebership
  • Admin can apply different level of filters on report of Booking, Insurance, Car History
  • Admin can tracks the detailed information of Customer, Payment, Insurance, , Car History
Second Level DFD Car Sharing System

Car Sharing System ER Diagram

Posted By freeproject on July 17, 2017

This ER (Entity Relationship) Diagram represents the model of Car Sharing System Entity. The entity-relationship diagram of Car Sharing System shows all the visual instrument of database tables and the relations between Customer, Car History,, Booking, Memebership etc. It used structure data and to define the relationships between structured data groups of Car Sharing System functionalities. The main entities of the Car Sharing System are Booking, Customer, Payment, Car History,, Insurance and Memebership.

Car Sharing System entities and their attributes :

  • Booking Entity : Attributes of Booking are booking_id, booking_title, booking_type, booking_ticket, booking_date, booking_description
  • Customer Entity : Attributes of Customer are customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Payment Entity : Attributes of Payment are payment_id, payment_customer_id, payment_date, payment_bill, payment_type, payment_description
  • Car History, Entity : Attributes of Car History, are car_history_id, car_history_customer_id, car_number, car_history_company car_history_type, car_history_description
  • Insurance Entity : Attributes of Insurance are insurance_id, insurance_bike_id, insurance_number, insurance_date, insurance_expiry, insurance_amount, insurance_type, insurance_description
  • Memebership Entity : Attributes of Memebership are membership_id, membership_customer_id, membership_name, membership_type, membership_description

Description of Car Sharing System Database :

  • The details of Booking is store into the Booking tables respective with all tables
  • Each entity (Memebership, Payment, Insurance, Customer, Booking) contains primary key and unique keys.
  • The entity Payment, Insurance has binded with Booking, Customer entities with foreign key
  • There is one-to-one and one-to-many relationships available between Insurance, Car History,, Memebership, Booking
  • All the entities Booking, Insurance, Payment, Memebership are normalized and reduce duplicacy of records
  • We have implemented indexing on each tables of Car Sharing System tables for fast query execution.
Car Sharing System ER Diagram

Car Sharing System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Car Sharing System which shows the interaction between the objects of Destination, Insurance, Payment, Customer, Booking. The instance of class objects involved in this UML Sequence Diagram of Car Sharing System are as follows:

  • Destination Object
  • Insurance Object
  • Payment Object
  • Customer Object
  • Booking Object

This is the UML sequence diagram of Car Sharing System which shows the interaction between the objects of Destination, Insurance, Payment, Customer, Booking. The instance of class objects involved in this UML Sequence Diagram of Car Sharing System are as follows:

  • Destination Object
  • Insurance Object
  • Payment Object
  • Customer Object
  • Booking Object

Car Sharing System Use Case Diagram

Posted By freeproject on July 24, 2017

This Use Case Diagram is a graphic depiction of the interactions among the elements of Car Sharing System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Car Sharing System. The main actors of Car Sharing System in this Use Case Diagram are: Super Admin, System User, Customer, Driver, who perform the different type of use cases such as Manage Booking, Manage Customer, Manage Payment, Manage Car History, Manage Insurance, Manage Memebership, Manage Destination, Manage Users and Full Car Sharing System Operations. Major elements of the UML use case diagram of Car Sharing System are shown on the picture below.

The relationships between and among the actors and the use cases of Car Sharing System:

  • Super Admin Entity : Use cases of Super Admin are Manage Booking, Manage Customer, Manage Payment, Manage Car History, Manage Insurance, Manage Memebership, Manage Destination, Manage Users and Full Car Sharing System Operations
  • System User Entity : Use cases of System User are Manage Booking, Manage Customer, Manage Payment, Manage Car History, Manage Insurance, Manage Memebership, Manage Destination
  • Customer Entity : Use cases of Customer are Request Sharing, View Sharing, Make Payment, View Payment History
  • Driver Entity : Use cases of Driver are Check Sharing Request, View Passengars, Manage Routes, Collect Payments

Use Case Diagram of Car Sharing System :

 Car Sharing System Use Case Diagram

Project Category