Automobiles Store and Service Management System UML Diagram

Posted By freeproject on March 18, 2018

Automobiles Store and Service Management System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Automobiles Store and Service Management System which shows the flows between the activity of Services, Delivery, Store, Automobiles, Payment. The main activity involved in this UML Activity Diagram of Automobiles Store and Service Management System are as follows:

  • Services Activity
  • Delivery Activity
  • Store Activity
  • Automobiles Activity
  • Payment Activity

Features of the Activity UML diagram of Automobiles Store and Service Management System

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

Automobiles Store and Service Management System Class Diagram

Posted By freeproject on August 2, 2017

Automobiles Store and Service Management System Class Diagram describes the structure of a Automobiles Store and Service Management System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Automobiles Store and Service Management System are Automobiles, Store, Customer, Services, Charges, Delivery.

Classes of Automobiles Store and Service Management System Class Diagram:

  • Automobiles Class : Manage all the operations of Automobiles
  • Store Class : Manage all the operations of Store
  • Customer Class : Manage all the operations of Customer
  • Services Class : Manage all the operations of Services
  • Charges Class : Manage all the operations of Charges
  • Delivery Class : Manage all the operations of Delivery

Classes and their attributes of Automobiles Store and Service Management System Class Diagram:

  • Automobiles Attributes : automobiles_id, automobiles_customer_id, automobile_number, automobile_type, automobile_description
  • Store Attributes : store_id, store_type, store_title, store_description
  • Customer Attributes : customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Services Attributes : service_id, service_vehicle_id, service_charge, service_type, service_description
  • Charges Attributes : charge_id, charge_service_id, charge_amount, charge_total, charge_type, charge_description
  • Delivery Attributes : delivery_id, delivery_customer_id, delivery_address, delivery_type, delivery_by, delivery_date, delivery_description

Classes and their methods of Automobiles Store and Service Management System Class Diagram:

  • Automobiles Methods : addAutomobiles(), editAutomobiles(), deleteAutomobiles(), updateAutomobiles(), saveAutomobiles(), searchAutomobiles()
  • Store Methods : addStore(), editStore(), deleteStore(), updateStore(), saveStore(), searchStore()
  • Customer Methods : addCustomer(), editCustomer(), deleteCustomer(), updateCustomer(), saveCustomer(), searchCustomer()
  • Services Methods : addServices(), editServices(), deleteServices(), updateServices(), saveServices(), searchServices()
  • Charges Methods : addCharges(), editCharges(), deleteCharges(), updateCharges(), saveCharges(), searchCharges()
  • Delivery Methods : addDelivery(), editDelivery(), deleteDelivery(), updateDelivery(), saveDelivery(), searchDelivery()

Class Diagram of Automobiles Store and Service Management System :

Class Diagram Image: 
Automobiles Store and Service Management System Class Diagram

Automobiles Store and Service Management System Component Diagram

Posted By freeproject on February 8, 2018

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

Components of UML Component Diagram of Automobiles Store and Service Management System:

  • Delivery Component
  • Charges Component
  • Services Component
  • Customers Component
  • Payment Component

Featues of Automobiles Store and Service Management System Component Diagram:

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

Automobile Stores and Services Management System Dataflow Diagram

Posted By namita on June 28, 2017

Automobile Stores and Services Management System Data flow diagram is often used as a preliminary step to create an overview of the Automobile without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Automobile process. It contains all of the userflow and their entities such all the flow of Automobiles, Booking, Customers, Services, Charges, Delivery, Payment. All of the below diagrams has been used for the visualization of data processing and structured design of the Automobile process and working flow.


Zero Level Data flow Diagram(0 Level DFD) of Automobile Stores and Services Management System :

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

High Level Entities and proccess flow of Automobile Stores and Services Management System :

  • Managing all the Automobiles
  • Managing all the Booking
  • Managing all the Customers
  • Managing all the Services
  • Managing all the Charges
  • Managing all the Delivery
  • Managing all the Payment
Zero Level Data flow Diagram(0 Level DFD) of Automobile Stores and Services Management System

First Level Data flow Diagram(1st Level DFD) of Automobile Stores and Services Management System :

First Level DFD (1st Level) of Automobile Stores and Services 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 Automobile Stores and Services system as a whole. It also identifies internal data stores of Payment, Delivery, Charges, Services, Customers that must be present in order for the Automobile system to do its job, and shows the flow of data between the various parts of Automobiles, Customers, Delivery, Payment, Charges 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 Automobile.

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

  • Processing Automobiles records and generate report of all Automobiles
  • Processing Booking records and generate report of all Booking
  • Processing Customers records and generate report of all Customers
  • Processing Services records and generate report of all Services
  • Processing Charges records and generate report of all Charges
  • Processing Delivery records and generate report of all Delivery
  • Processing Payment records and generate report of all Payment
First Level Data flow Diagram(1st Level DFD) of Automobile Stores and Services Management System

Second Level Data flow Diagram(2nd Level DFD) of Automobile Stores and Services Management System :

DFD Level 2 then goes one step deeper into parts of Level 1 of Automobile. It may require more functionalities of Automobile to reach the necessary level of detail about the Automobile functioning. First Level DFD (1st Level) of Automobile Stores and Services shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Payment, Delivery, Charges, Services, Customers, Booking, Automobiles.

Low level functionalities of Automobile Stores and Services Management System

  • Admin logins to the system and manage all the functionalities of Automobile Stores and Services Management System
  • Admin can add, edit, delete and view the records of Automobiles, Customers, Charges, Payment
  • Admin can manage all the details of Booking, Services, Delivery
  • Admin can also generate reports of Automobiles, Booking, Customers, Services, Charges, Delivery
  • Admin can search the details of Booking, Charges, Delivery
  • Admin can apply different level of filters on report of Automobiles, Services, Charges
  • Admin can tracks the detailed information of Booking, Customers, Services, , Charges
Second Level Data flow Diagram(2nd Level DFD) of Automobile Stores and Services Management System

Automobiles Store and Service Management System ER Diagram

Posted By freeproject on July 17, 2017

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

Automobiles Store and Service Management System entities and their attributes :

  • Automobiles Entity : Attributes of Automobiles are automobiles_id, automobiles_customer_id, automobile_number, automobile_type, automobile_description
  • Store Entity : Attributes of Store are store_id, store_type, store_title, store_description
  • Customer Entity : Attributes of Customer are customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Services Entity : Attributes of Services are service_id, service_vehicle_id, service_charge, service_type, service_description
  • Charges Entity : Attributes of Charges are charge_id, charge_service_id, charge_amount, charge_total, charge_type, charge_description
  • Delivery Entity : Attributes of Delivery are delivery_id, delivery_customer_id, delivery_address, delivery_type, delivery_by, delivery_date, delivery_description

Description of Automobiles Store and Service Management System Database :

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

Automobiles Store and Service Management System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Automobiles Store and Service Management System which shows the interaction between the objects of Services, Charges, Customers, Store, Delivery. The instance of class objects involved in this UML Sequence Diagram of Automobiles Store and Service Management System are as follows:

  • Services Object
  • Charges Object
  • Customers Object
  • Store Object
  • Delivery Object

This is the UML sequence diagram of Automobiles Store and Service Management System which shows the interaction between the objects of Services, Charges, Customers, Store, Delivery. The instance of class objects involved in this UML Sequence Diagram of Automobiles Store and Service Management System are as follows:

  • Services Object
  • Charges Object
  • Customers Object
  • Store Object
  • Delivery Object

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

The relationships between and among the actors and the use cases of Automobiles Store and Service Management System:

  • Super Admin Entity : Use cases of Super Admin are Manage Automobiles, Manage Store, Manage Customers, Manage Services, Manage Charges, Manage Delivery, Manage Payment, Manage Users and Full Automobiles Store and Service Management System Operations
  • System User Entity : Use cases of System User are Manage Automobiles, Manage Store, Manage Customers, Manage Services, Manage Charges, Manage Delivery, Manage Payment
  • Mechanic Entity : Use cases of Mechanic are Manage Serviice Request, Manage Part Requests, Manage Automobiles Issues
  • Customers Entity : Use cases of Customers are View Service Request, View Invoices, Make Payments

Use Case Diagram of Automobiles Store and Service Management System :

 Automobiles Store and Service Management System Use Case Diagram

Project Category