Contents:

Introduction……………………………………………………………03

ER Diagram…………………………………………………………...04

Relation Model………………………………………………………..06

Assumptions…………………………………………………………..07

A Sample Screens…………………………………………………....08

Database Design……………………………………………………..09

Required Changes…………………………………………………...10

Conclusion………………………………………...............................10

Reference…………………………………………………………......11
Introduction:

HC hobbies are giving military model packs to the general population and clients can
visit the store to see the different kinds of models and they can likewise want for the
locations of the multitude of models. HC hobbies currently need to modernize the
framework so the client can arrange the tactical model online by utilizing the framework.
This report is giving the necessary data that is needed to dissect to plan and carry out
any new framework in the association. The ER outline of this framework is made and
momentarily clarified in this report with the social model of the multitude of fields that
include primary, foreign and concatenated keys. One example screen is additionally
made that can be used to put in a request on the web and this report is likewise giving
the progressions that can be required in the data set or framework.
ER Diagram:

As the CS hobbies need to carry out the online framework for offering the support of
request online for the clients, this ER diagram is made that will assist with
understanding the essential necessities of the system and plan the new system will get
simpler as this chart is addressing the primary and foreign keys that can be utilized in
the framework database.

Figure 1 ER Diagram

This ER outline is addressing the connection between numerous classes and attributes,
in this graph six classes are utilized like framework, client, orders, installment,
shipments, and military model kits. The client class has one primary key name client id,
the system class has one primary key that is system id and it has four foreign keys that
are client id, model id, shipment id, and installment id. The order class has one primary
key that is order id and it has two foreign keys that are client id, and model id, different
characteristics request date, and model name. The installment class has one primary
key that is installment id and three foreign keys that are organization id, client id, and
shipment id with another attribute that is the sum. The shipment class has one primary
key that is shipment id and two foreign keys that are structure id and client id. This class
has different attributes, for example, shipment date, client name, and address. The
military class has one primary key that is model id and two different traits like model
name and model sort.

Final Logical Model:

Relation Model:
Table 1 System Class

Name Key Type

System_id Primary Key Int
Customer_id Foreign Key Int
Model_id Foreign Key Int
Shipment_id Foreign Key Int
Payment_id Foreign Key Int

Table 2 Customer Class

Name Key Type

Customer_id Primary Key Int
Customer_name - Varchar
Phone_no - Varchar
Address - Varchar
EmailID - Varchar

Table 3 Order Class

Name Key Type

Order_id Primary Key Int
Customer_id Foreign Key Int
Model_id Foreign Key Int
Order_date - Date
Model_name - Varchar

Table 4 Payment Class

Name Key Type

Payment_id Primary Key Int
Customer_id Foreign Key Int
Order_id Foreign Key Int
Shipment_id Foreign Key Int
Amount - Varchar

Table 5 Shipment Class

Name Key Type

 Shipment_id Primary Key Int
Customer_id Foreign Key Int
Order_id Foreign Key Int
Shipment_date - Date
Customer_name - Varchar
Address - Varchar

Table 6 Military Model Class

Name Key Type

Model_id Primary Key Int
Model_name - Varchar
Model_type - Varchar

Assumptions:

A few presumptions made to make the ER graph are –

1. The framework Class is made that stores all the data about clients, models,
installment, and shipment.

2. The client will sign in and logout from the framework to get the installment or account
data.

3. The client can get to the location of the relative multitude of models from this
framework after login in to arrange any model accessible on the system.

4. The client data will safely store in the data set.

A sample screens:
 Figure 2 Select and Order Screen

This screen is utilized by the clients to choose the model kind, model name, and amount
of the model in the wake of survey the locations of the relative multitude of models in
this system. The aggregate sum will be shown on the following screen.
 Figure 3 Order Form

This is the request structure screen that will show the chose model, amount, and
measure of the models and the client can pay by adding the card subtleties in this
structure. The card subtleties will be safely put away in the system with the goal that
clients can't need to add the card subtleties each an ideal opportunity to buy the models
from this framework.

Database Design:

The database design that is made and addressed in the ER figure will store all the data
aside from the card subtleties of the client. On the off chance that the card subtleties of
the client will be consequently saved in the system that can improve the robotization
include and the client can't need to add the card subtleties to make installment after
each buy. The card subtleties are needed to be put away in the framework with the goal
that the client can choose the saved card to make installment of the buy. The security of
client individual data is vital that is needed to get in the database. The information
encryption is additionally needed to be done in the data set with the goal that the client
information can be gotten in this framework and an unauthenticated client can't get to
the subtleties of the client. The login is needed to make any buy from this framework to
make the system safer.
Required Changes:

The progressions that can be executed inside ER chart after the making of the example
input screen are as per the following:

• The Class for Card subtleties (with the exception of CVV) can be carried out in ER
charts that are for a quick charging measure whenever utilized later on.

• The Class for Invoice Details of the buy can be included ER chart that is according to
things, the client purchases from the site.

• The Class for subtleties of past Purchase (History) can be executed inside ER graph
after the making of the Sample input screen.

• The Class for Wishlist can be executed In ER chart that assists clients with saving
things, they may purchase later on.

• The Class for Help and Support can be carried out in ER graph which will be utilized
by clients for their questions or any sort of issue while utilizing the site or any sort of buy
blunder (Refund, Return, and so on).

Conclusion:

This report has closed the framework plan for CS hobby which offers the tactical model
to the client. This report has given the ER chart that addresses every one of the
necessary classes and attributes that can be utilized to store the information in the data
set of this framework. The primary and foreign keys are additionally characterized in the
ER chart and the NF table is given in this report that gives the insight regarding each
class which incorporates characteristic name, type, and key. The example screen for
the client to arrange online is additionally made and addressed in this report after that a
few changes that are needed to be done in the ER outline and information base are
additionally clarified in the report.
Reference:

Ravi, S. Y., Jindal, R., & Anand, S. (2020). A Study on Comparison of UML and ER
Diagram.

Page, C., & Six, H. W. (2017). Software Engineering. Larsen and Keller Education.

Rolik, O., Amons, O., Ulianytska, K., & Kolesnik, V. (2020, January). Modernization of
the Second Normal Form and Boyce-Codd Normal Form for Relational Theory. In
International Conference on Computer Science, Engineering and Education
Applications (pp. 296-305). Springer, Cham.

Amin, M., Romney, G. W., Dey, P., & Sinha, B. (2019). Teaching relational database
normalization in an innovative way. Journal of Computing Sciences in Colleges, 35(2),
48-56.