Bike Service Center Management System UML Diagram

Posted By freeproject on March 18, 2018

Bike Service Center Management System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Bike Service Center Management System which shows the flows between the activity of Repair Bike, Delivery, Insurance, Payment, Bike. The main activity involved in this UML Activity Diagram of Bike Service Center Management System are as follows:

  • Repair Bike Activity
  • Delivery Activity
  • Insurance Activity
  • Payment Activity
  • Bike Activity

Features of the Activity UML diagram of Bike Service Center Management System

  • Admin User can search Repair Bike, view description of a selected Repair Bike, add Repair Bike, update Repair Bike and delete Repair Bike.
  • Its shows the activity flow of editing, adding and updating of Delivery
  • User will be able to search and generate report of Insurance, Payment, Bike
  • All objects such as ( Repair Bike, Delivery, Bike) are interlinked
  • Its shows the full description and flow of Repair Bike, Payment, Bike, Insurance, Delivery
Bike Service Center Management System Activity Diagram

Bike Service Center Management System Class Diagram

Posted By freeproject on August 2, 2017

Bike Service Center Management System Class Diagram describes the structure of a Bike Service Center Management System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Bike Service Center Management System are Bike, Booking, Repair Bike, Insurance, Customer, Payment.

Classes of Bike Service Center Management System Class Diagram:

  • Bike Class : Manage all the operations of Bike
  • Booking Class : Manage all the operations of Booking
  • Repair Bike Class : Manage all the operations of Repair Bike
  • Insurance Class : Manage all the operations of Insurance
  • Customer Class : Manage all the operations of Customer
  • Payment Class : Manage all the operations of Payment

Classes and their attributes of Bike Service Center Management System Class Diagram:

  • Bike Attributes : bike_id, bike_customer_id, bike_number, bike_company bike_type, bike_description
  • Booking Attributes : booking_id, booking_title, booking_type, booking_date, booking_description
  • Repair Bike Attributes : repair_bike_id, repair_bike_customer_id, repair_bike_number, repair_bike_bill, repair_bike_type, repair_bike_description
  • Insurance Attributes : insurance_id, insurance_bike_id, insurance_number, insurance_date, insurance_expiry, insurance_amount, insurance_type, insurance_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

Classes and their methods of Bike Service Center Management System Class Diagram:

  • Bike Methods : addBike(), editBike(), deleteBike(), updateBike(), saveBike(), searchBike()
  • Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
  • Repair Bike Methods : addRepair Bike(), editRepair Bike(), deleteRepair Bike(), updateRepair Bike(), saveRepair Bike(), searchRepair Bike()
  • Insurance Methods : addInsurance(), editInsurance(), deleteInsurance(), updateInsurance(), saveInsurance(), searchInsurance()
  • Customer Methods : addCustomer(), editCustomer(), deleteCustomer(), updateCustomer(), saveCustomer(), searchCustomer()
  • Payment Methods : addPayment(), editPayment(), deletePayment(), updatePayment(), savePayment(), searchPayment()

Class Diagram of Bike Service Center Management System :

Class Diagram Image: 
Bike Service Center Management System Class Diagram

Bike Service Center Management System Component Diagram

Posted By freeproject on February 8, 2018

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

Components of UML Component Diagram of Bike Service Center Management System:

  • Payment Component
  • Delivery Component
  • Repair Bike Component
  • Customer Component
  • Bike Component

Featues of Bike Service Center Management System Component Diagram:

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

Bike Service Center Management System Dataflow Diagram

Posted By namita on June 28, 2017
Bike Service Center Management System Data flow diagram is often used as a preliminary step to create an overview of the Bike without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Bike process. It contains all of the userflow and their entities such all the flow of Booking, Repair Bike, Insurance, Payment, Delivery, Branches Center, Customer. All of the below diagrams has been used for the visualization of data processing and structured design of the Bike process and working flow.

Zero Level Data flow Diagram(0 Level DFD) of Bike Service Center Management System :

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

High Level Entities and proccess flow of Bike Service Center Management System:

  • Managing all the Booking
  • Managing all the Repair Bike
  • Managing all the Insurance
  • Managing all the Payment
  • Managing all the Delivery
  • Managing all the Branches Center
  • Managing all the Customer
Zero Level Data flow Diagram(0 Level DFD) of Bike Service Center Management System

First Level Data flow Diagram(1st Level DFD) of Bike Service Center Management System :

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

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

  • Processing Booking records and generate report of all Booking
  • Processing Repair Bike records and generate report of all Repair Bike
  • Processing Insurance records and generate report of all Insurance
  • Processing Payment records and generate report of all Payment
  • Processing Delivery records and generate report of all Delivery
  • Processing Branches Center records and generate report of all Branches Center
  • Processing Customer records and generate report of all Customer
First Level Data flow Diagram(1st Level DFD) of Bike Service Center Management System

Second Level Data flow Diagram(2nd Level DFD) of Bike Service Center Management System :

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

Low level functionalities of Bike Service Center Management System

  • Admin logins to the system and manage all the functionalities of Bike Service Center Management System
  • Admin can add, edit, delete and view the records of Booking, Insurance, Delivery, Customer
  • Admin can manage all the details of Repair Bike, Payment, Branches Center
  • Admin can also generate reports of Booking, Repair Bike, Insurance, Payment, Delivery, Branches Center
  • Admin can search the details of Repair Bike, Delivery, Branches Center
  • Admin can apply different level of filters on report of Booking, Payment, Delivery
  • Admin can tracks the detailed information of Repair Bike, Insurance, Payment, , Delivery
Second Level Data flow Diagram(2nd Level DFD) of Bike Service Center Management System

Bike Service Center Management System ER Diagram

Posted By freeproject on July 17, 2017

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

Bike Service Center Management System entities and their attributes :

  • Bike Entity : Attributes of Bike are bike_id, bike_customer_id, bike_number, bike_company bike_type, bike_description
  • Booking Entity : Attributes of Booking are booking_id, booking_title, booking_type, booking_date, booking_description
  • Repair Bike Entity : Attributes of Repair Bike are repair_bike_id, repair_bike_customer_id, repair_bike_number, repair_bike_bill, repair_bike_type, repair_bike_description
  • Insurance Entity : Attributes of Insurance are insurance_id, insurance_bike_id, insurance_number, insurance_date, insurance_expiry, insurance_amount, insurance_type, insurance_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

Description of Bike Service Center Management System Database :

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

Bike Service Center Management System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Bike Service Center Management System which shows the interaction between the objects of Repair Bike, Booking, Branches center, Insurance, Payment. The instance of class objects involved in this UML Sequence Diagram of Bike Service Center Management System are as follows:

  • Repair Bike Object
  • Booking Object
  • Branches center Object
  • Insurance Object
  • Payment Object

This is the UML sequence diagram of Bike Service Center Management System which shows the interaction between the objects of Repair Bike, Booking, Branches center, Insurance, Payment. The instance of class objects involved in this UML Sequence Diagram of Bike Service Center Management System are as follows:

  • Repair Bike Object
  • Booking Object
  • Branches center Object
  • Insurance Object
  • Payment Object

Bike Service Center Management 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 Bike Service Center Management System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Bike Service Center Management System. The main actors of Bike Service Center Management System in this Use Case Diagram are: Super Admin, System User, Cashiers, Customers, who perform the different type of use cases such as Manage Bike, Manage Booking, Manage Repair Bike, Manage Insurance, Manage Customer, Manage Payment, Manage Delivery, Manage Branches center, Manage Users and Full Bike Service Center Management System Operations. Major elements of the UML use case diagram of Bike Service Center Management System are shown on the picture below.

The relationships between and among the actors and the use cases of Bike Service Center Management System:

  • Super Admin Entity : Use cases of Super Admin are Manage Bike, Manage Booking, Manage Repair Bike, Manage Insurance, Manage Customer, Manage Payment, Manage Delivery, Manage Branches center, Manage Users and Full Bike Service Center Management System Operations
  • System User Entity : Use cases of System User are Manage Bike, Manage Booking, Manage Repair Bike, Manage Insurance, Manage Customer, Manage Payment, Manage Delivery, Manage Branches center
  • Cashiers Entity : Use cases of Cashiers are Create Invoice, Parts Management, Manage Service Charges
  • Customers Entity : Use cases of Customers are View Services, View Parts, Make Payments

Use Case Diagram of Bike Service Center Management System :

 Bike Service Center Management System Use Case Diagram