This article provides extensive architecture documentation for the online automotive showroom. The numerous modules in this framework are explained.

Structure of software package :

The various functional components used are:

Functional component 1: Login module

Functional component 2: Vehicle module

Functional component 3: Vehicle selection module

Functional component 4: Booking module

Functional component 5: Admin module

Functional component 6: Dealer module

Modular Decomposition of the System:

Login module:

Design assumptions: It is supposed to authenticate a computer until it enters the machine. The customer must have the proper username and password-authenticated. You have the correct account and password to re-login if your user is not valid.

Identification of module:

The module identified in this system:

• Get username
• Get password
• Login

Structure Chart showing the hierarchy of modules:

Vehicle module:

Design assumptions: The system module is used for inserting new cars, upgrading and removing vehicle information.

Identification of module:

The module identified in this system:

• Add vehicle
• update
• delete

Structure Chart showing the hierarchy of modules:

Vehicle Selection module:

Design assumptions: You have to choose the cars according to your name. In this range, the consumer will pick vehicles according to their model.

Identification of module:

In this method, the module identified:

• Search

Structure Chart showing the hierarchy of modules:

Booking module:

Design assumptions: Users can book their vehicles on this page by entering cart information. Upon reservation, users collect details on booked vehicles via e-mail.

Identification of module:

The module identified in this system:

• register
• submit
• edit

Structure Chart showing the hierarchy of modules:

Admin module:

Design assumptions: This website is completely approved by the administrator. The boss can add new car knowledge here, and his staff can add that.

Identification of module:

The module identified in this system:

• login
• add new dealer
• change password
• logout

Structure Chart showing a hierarchy of modules:

Dealer module:

Design assumptions: Dealers can manage client information and connect by mail with customers. If you lose your password dealer, your password will be reset.

Identification of module:

The module identified in this sytem:

• login
• add new customer
• change password
• logout

Structure Chart showing hierarchy of modules: