- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Car Sales System Activity Diagram
This is the Activity UML diagram of Car Sales System which shows the flows between the activity of Sales, Models, Customer, , Inventory. The main activity involved in this UML Activity Diagram of Car Sales System are as follows:
- Sales Activity
- Models Activity
- Customer Activity
- Activity
- Inventory Activity
Features of the Activity UML diagram of Car Sales System
- Admin User can search Sales, view description of a selected Sales, add Sales, update Sales and delete Sales.
- Its shows the activity flow of editing, adding and updating of Models
- User will be able to search and generate report of Customer, , Inventory
- All objects such as ( Sales, Models, Inventory) are interlinked
- Its shows the full description and flow of Sales, , Inventory, Customer, Models
Login Activity Diagram of Car Sales System:
This is the Login Activity Diagram of Car Sales 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 Customer, Sales, Models, Inventory, . All the pages such as Models, Inventory, are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Car Sales System. The various objects in the Inventory, Customer, Sales, Models, and 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
Car Sales System Class Diagram
Car Sales System Class Diagram describes the structure of a Car Sales System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Car Sales System are Cars, Car Models, Car Owners, Inventory, Customer, Booking.
Classes of Car Sales System Class Diagram:
- Cars Class : Manage all the operations of Cars
- Car Models Class : Manage all the operations of Car Models
- Car Owners Class : Manage all the operations of Car Owners
- Inventory Class : Manage all the operations of Inventory
- Customer Class : Manage all the operations of Customer
- Booking Class : Manage all the operations of Booking
Classes and their attributes of Car Sales System Class Diagram:
- Cars Attributes : car_id, car_driver_id, car_customer_id, car_number, car_company car_type, car_description
- Car Models Attributes : car_model_id, car_model_number, car_model_year, car_model_name, car_model_type, car_model_description
- Car Owners Attributes : car owner_id, car owner_name, car owner_mobile, car owner_email, car owner_username, car owner_password, car owner_address
- Inventory Attributes : inventory_id, inventory_items, inventory_number, inventory_type, inventory_description
- Customer Attributes : customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
- Booking Attributes : booking_id, booking_title, booking_type, booking_ticket, booking_date, booking_description
Classes and their methods of Car Sales System Class Diagram:
- Cars Methods : addCars(), editCars(), deleteCars(), updateCars(), saveCars(), searchCars()
- Car Models Methods : addCar Models(), editCar Models(), deleteCar Models(), updateCar Models(), saveCar Models(), searchCar Models()
- Car Owners Methods : addCar Owners(), editCar Owners(), deleteCar Owners(), updateCar Owners(), saveCar Owners(), searchCar Owners()
- Inventory Methods : addInventory(), editInventory(), deleteInventory(), updateInventory(), saveInventory(), searchInventory()
- Customer Methods : addCustomer(), editCustomer(), deleteCustomer(), updateCustomer(), saveCustomer(), searchCustomer()
- Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
Class Diagram of Car Sales System :
- Posted By: freeproject
- Comments: 0
Car Sales System Component Diagram
This is a Component diagram of Car Sales System which shows components, provided and required interfaces, ports, and relationships between the Cars, Inventory, Sales, and Models. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Car Sales System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Car Sales System:
- Cars Component
- Inventory Component
- Sales Component
- Component
- Models Component
Featues of Car Sales System Component Diagram:
- You can show the models the components of Car Sales System.
- Model the database schema of Car Sales System
- Model the executables of an application of Car Sales System
- Model the system's source code of Car Sales System
- Posted By: namita
- Comments: 0
Car Sales System Dataflow Diagram
Zero Level Data flow Diagram(0 Level DFD) of Car Sales System :
This is the Zero Level DFD of Car Sales System, where we have eloborated the high level process of Car. It’s a basic overview of the whole Car Sales System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Inventory,Customer and Login showing the system as a single high-level process, with its relationship to external entities of Cars,Car Models and Sales. It should be easily understood by a wide audience, including Cars,Sales and Inventory In zero leve DFD of Car Sales System, we have described the high level flow of the Car system.High Level Entities and proccess flow of Car Sales System:
- Managing all the Cars
- Managing all the Car Models
- Managing all the Sales
- Managing all the Car Owner
- Managing all the Inventory
- Managing all the Customer
- Managing all the Login
First Level Data flow Diagram(1st Level DFD) of Car Sales System :
First Level DFD (1st Level) of Car Sales 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 Sales System system as a whole. It also identifies internal data stores of Login, Customer, Inventory, Car Owner, Sales 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 Cars, Sales, Customer, Login, Inventory 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 Cars records and generate report of all Cars
- Processing Car Models records and generate report of all Car Models
- Processing Sales records and generate report of all Sales
- Processing Car Owner records and generate report of all Car Owner
- Processing Inventory records and generate report of all Inventory
- Processing Customer records and generate report of all Customer
- Processing Login records and generate report of all Login
Second Level Data flow Diagram(2nd Level DFD) of Car Sales 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 Sales System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Login, Customer, Inventory, Car Owner, Sales, Car Models, Cars.Low level functionalities of Car Sales System
- Admin logins to the system and manage all the functionalities of Car Sales System
- Admin can add, edit, delete and view the records of Cars, Sales, Inventory, Login
- Admin can manage all the details of Car Models, Car Owner, Customer
- Admin can also generate reports of Cars, Car Models, Sales, Car Owner, Inventory, Customer
- Admin can search the details of Car Models, Inventory, Customer
- Admin can apply different level of filters on report of Cars, Car Owner, Inventory
- Admin can tracks the detailed information of Car Models, Sales, Car Owner, , Inventory
- Posted By: freeproject
- Comments: 0
Car Sales System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Car Sales System Entity. The entity-relationship diagram of Car Sales System shows all the visual instrument of database tables and the relations between Car Models, Inventory, Cars, Booking etc. It used structure data and to define the relationships between structured data groups of Car Sales System functionalities. The main entities of the Car Sales System are Cars, Car Models, Car Owners, Inventory, Customer and Booking.
Car Sales System entities and their attributes :
- Cars Entity : Attributes of Cars are car_id, car_driver_id, car_customer_id, car_number, car_company car_type, car_description
- Car Models Entity : Attributes of Car Models are car_model_id, car_model_number, car_model_year, car_model_name, car_model_type, car_model_description
- Car Owners Entity : Attributes of Car Owners are car owner_id, car owner_name, car owner_mobile, car owner_email, car owner_username, car owner_password, car owner_address
- Inventory Entity : Attributes of Inventory are inventory_id, inventory_items, inventory_number, inventory_type, inventory_description
- Customer Entity : Attributes of Customer are customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
- Booking Entity : Attributes of Booking are booking_id, booking_title, booking_type, booking_ticket, booking_date, booking_description
Description of Car Sales System Database :
- The details of Cars is store into the Cars tables respective with all tables
- Each entity (Booking, Car Owners, Customer, Car Models, Cars) contains primary key and unique keys.
- The entity Car Owners, Customer has binded with Cars, Car Models entities with foreign key
- There is one-to-one and one-to-many relationships available between Customer, Inventory, Booking, Cars
- All the entities Cars, Customer, Car Owners, Booking are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Car Sales System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Car Sales System Sequence Diagram
This is the UML sequence diagram of Car Sales System which shows the interaction between the objects of Models, Sales, Inventory, Customer, . The instance of class objects involved in this UML Sequence Diagram of Car Sales System are as follows:
- Models Object
- Sales Object
- Inventory Object
- Customer Object
- Object
Login Sequence Diagram of Car Sales System:
This is the Login Sequence Diagram of Car Sales System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Inventory, Models, Sales, , Customer. All the pages such as Sales, , Customer are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Car Sales System. The various objects in the , Inventory, Models, Sales, and Customer 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 Car Sales System which shows the interaction between the objects of Models, Sales, Inventory, Customer, . The instance of class objects involved in this UML Sequence Diagram of Car Sales System are as follows:
- Models Object
- Sales Object
- Inventory Object
- Customer Object
- Object
- Posted By: freeproject
- Comments: 0
Car Sales System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Car Sales System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Car Sales System. The main actors of Car Sales System in this Use Case Diagram are: Super Admin, System User, Customer, Agent, who perform the different type of use cases such as Manage Cars, Manage Car Models, Manage Sales, Manage Car Owners, Manage Inventory, Manage Customer, Manage Users and Full Car Sales System Operations. Major elements of the UML use case diagram of Car Sales System are shown on the picture below.
The relationships between and among the actors and the use cases of Car Sales System:
- Super Admin Entity : Use cases of Super Admin are Manage Cars, Manage Car Models, Manage Sales, Manage Car Owners, Manage Inventory, Manage Customer, Manage Users and Full Car Sales System Operations
- System User Entity : Use cases of System User are Manage Cars, Manage Car Models, Manage Sales, Manage Car Owners, Manage Inventory, Manage Customer
- Customer Entity : Use cases of Customer are View Cars, Request Quotation, Make Payment
- Agent Entity : Use cases of Agent are Add Cars, Create Quotation, View Requests, Create Invoice
Use Case Diagram of Car Sales System :
