Vechile dealership management
#1

[attachment=3310]

The vehicle dealership management system is an intranet based web application that is being designed for the constancies control of the activities that take place within the dealerâ„¢s organization. The major applications concentration is to cross check the referential information related to the automobile that were sold at their branch level outlets. The system concentrates on the core issues of multiple branches implementation, with the multiple brands and sub brand implementation of the vehicles along with their color and features availability. The system at any time can help the sales personnel or the internal administration with the specific information, what they need. The system specifically instructs the basic administration with core requirement of information standards, as part of their organizational standards. The system also helps the sales personnel in cross checking the generic standards that substitution exists upon a particular automobile model and the specific sub branch.
The project has been planned to be having the view of distributed architecture, with centralized storage of the database. The application for the storage of date has been planned with constructs of Oracle 9i and all the user interfaces have been designed using the HTML and JSP application. The Java Database Connectivity (JDBC) has been exploited for the database interactive standards. The Bean components have been implemented for proper reusability and authenticity. The standards of security and date portative mechanism have been given a big choice for proper usage. The application takes care of different modules and their associated reports which re produced as per the applicable strategies and standards that are put forwarded by the administrative staff.

Manual Process
Phase I











Phase II













Why the new system?

1. The system at any point of time can provide the list of all the dealers and their branches details.
2. The system can provide the brand and sub brand details with in the click of a mouse.
3. The system provide the different features that a vehicle can have by a simple query
4. The system can execute the information of sales that have been conducted, disclosing all the features a vehicle can have with a simple click.i9
5. The sy06stem can execute the purchases that have been conducted for which brands at which time.
6. The system can provide the information related to the inventory record of the vehicles that is getting managed at the industry level.
7. The system with proper integration can serve the middle and high-level management, for statistical comparison upon the business process.

Number of Modules
The system after analysis has been found to have the following modules.
a) Vehicle manufacturers information module: This module specifically provides the overall information related to each manufacturer and the brands what he produces. The module has proper integration towards the brands and sub brands that are manufactured by the manufacturers. It also specifies the features what each branch as stated by the manufacturer.
b) Dealer information module: This module maintains the information specific to all the dealers and their branches and the vehicle brands they deal with. The module integrates itself to project the dealer wise inventory and the register for which this dealer is associated as incharge. The module also specifies the association with manufacturers.
c) Employer information master: The module maintains the information of all the employees who exist under the dealership management. The sales people who execute upon this system for the sales activity are maintained as database over here. It specifies the instructional existence of employees with respect to their departments and designations.
d) Sales Module: The module maintains the information related to the total sales that are executed upon the system by the sales people as part of their marketing activity. The total atomic information related to the sales is maintained here along with the technical and non-technical information that becomes more important for future reference.
e) Purchase module: This module provides the information related to the purchases that are executed by the dealers, with respect to the demand, from the customers. The module provides information related to which purchase has been executed at what time with respect to which brand. The technical details of a particular brand are also registered here when the vehicle is purchased.
Required Hardware
Pentium IV processes architecture
1. 128 MB RAM.
2. 20 MB Hard Disk Space
3. Ethernet card with an Internet or Internet zero.
Required Software
1. Windows 2000 XP operating system.
2. Internet explorer 5.0 or Netscape navigation
3. Oracle 9i.
4. TCP/IP Protocol Suite.
5. Windows Based JUM.
Reply

Important Note..!

If you are not satisfied with above reply ,..Please

ASK HERE

So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page
Popular Searches: abstract for automatic guided vechile, vechile aerodynamics ppt, how to get santoor soap dealership, vechile detection in no parking area using rf and magnetic sensor, vechile detection in no parking area using rf, automatic vechile locator full report in wikipedia, ford dealership austin,

[-]
Quick Reply
Message
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Forum Jump: