Project 1
The software database design is referred to as the E–Commerce Website ER Diagram. This ER Diagram is a graphical representation of the relationships between all of the system’s entities. The ER Diagram is used to create and troubleshoot the relational database of the System. It’s excellent when used with a DFD (Data Flow Diagram), which is in charge of data transportation.
Importance of ER Diagram for E-commerce Website
The importance of an ER Diagram for an e-commerce website is that it aids in the modeling of data storage and databases. It serves as the foundation for the project’s database construction. This entity relationship diagram (ERD) can also help define the data types that will be stored, as well as their qualities and characteristics.
In addition to that, the ER Diagram also describes how an entity interacts with other entities. All other real-world projects are presented with ER Diagrams (database designs).
- E-Commerce Websites : The major element of this system is the e-commerce website process, which keeps the essential facts of every transaction done by clients in its database.
- Customer Management : This function is extremely vital to the system because it collects all of the important information from the clients. These details were utilized to keep track of their transactions and other key system details.
- Manage Reports : The selling admin can handle the information on customers and products, as well as the status of their orders and transaction details.
- Manage Customer Transactions : This system is in charge of consumer transactions, such as placing orders or reserving items. This will also be used by the administrator to keep track of the transactions that take place in the system.
- Transaction and Reports Management :Customers’ purchases, as well as their personal information and timetables, will be saved in this feature.
These tables below provide the complete database tables details such as Field Name, Descriptions, data types, character lengths.
E-commerce Website Database Tables
These tables below provide the complete database tables details such as Field Name, Descriptions, data types, character lengths.
Table Name: tbl_Customer
| Field | Description | Type | Length |
| customer_ID (PK) | Customer ID | Int | 11 |
| name | Customer Name | Varchar | 255 |
| contact_add | Contact Address | Int | 11 |
| address | Address | Text |
Table Name: tbl_Products
| Field | Description | Type | Length |
| product_ID (PK) | Product ID | Int | 11 |
| category_ID (FK) | Category ID | Int | 11 |
| product_name | Product Name | Varchar | 225 |
Table Name: tbl_Categories
| Field | Description | Type | Length |
| category_ID (PK) | Category ID | Int | 11 |
| category_name | Category Name | Varchar | 30 |
| category_type | Category Type | Varchar | 30 |
Table Name:tbl_ Seller
| Field | Description | Type | Length |
| seller_ID (PK) | Seller ID | Int | 11 |
| product_ID (FK) | Product ID | Int | 11 |
| name | Name | Varchar | 30 |
Table Name: tbl_Shopping Order
| Field | Description | Type | Length |
| order_ID (PK) | Order ID | Int | 11 |
| customer_ID (FK) | Customer ID | Int | 11 |
| date | Date of Order | Date |
Table Name: tbl_Payment
| Field | Description | Type | Length |
| payment_ID (PK) | Payment ID | Int | 11 |
| category_ID (FK) | Category ID | Int | 11 |
| date | Date of Payment | Date |
Table Name: tbl_Deliveries
| Field | Description | Type | Length |
| delivery_ID (PK) | Delivery ID | Int | 11 |
| customer_ID (FK) | Customer ID | Int | 11 |
| date | Date odf Delivery | Date |
Table Name:tbl_ Transaction Reports
| Field | Description | Type | Length |
| report_ID | Report ID | Int | 11 |
| customer_ID (FK) | Customer ID | Int | 11 |
| order_ID (FK) | Order ID | Int | 11 |
| Product_ID (FK) | Product ID | Int | 11 |
| payment_ID (FK) | Payment ID | Int | 11 |
Example of Good E-Commerce Database Design
Databases are crucial for storing, organizing, and retrieving data. They are also necessary for the development of an e-commerce system. E-commerce relies on a well-structured database to power it and to manage all of the system’s interactions.
The following features are included in a solid e-commerce database design:
The database table structure is minimal but provides all of the essential functions without affecting the user experience.
High performance: Database queries run swiftly to allow real-time customer interactions and a seamless shopping experience. As a result, the database you choose should have good indexing and performance optimization features.
High availability and scalability: A good database design ensures high availability with automatic snapshots and allows for automatic scaling to meet future platform growth as well as unexpected traffic spikes.
A solid e-commerce database architecture includes three important pieces based on these characteristics:
The scope of the database relates to the database’s intended functionality. The database’s core table structure, linkages, and indexes are all dependent on the e-commerce platform’s functionality.
Type of database: Depending on the requirements and underlying data structure, the type can range from a relational database to a NoSQL database or a hybrid solution.
Infrastructure for databases: Your database can be controlled or left unmanaged. The former entails creating your own database service, whereas the latter entails using Amazon RDS or Amazon DynamoDB.
ER Diagram Symbols
In this image below, you will see the different ER Diagram Symbols.
Entity Relationship Diagram for E-Commerce Website
ER Diagram of E-Commerce Website shows the system entity relationships in each entity and their supposed functions in each relationship.
This section will show you the ER Diagram for E-Commerce Website. In the image below you see the actual relationship of all entity. In creating this activity diagram we used lucidchart.
The database design shown with tables in the Entity Relationship diagram for E-commerce Website is shown in the image above. The tables are designed to suit the system’s requirements and to provide considerably more detailed information about each entity within the system.
The purpose of this ER Diagram is to thoroughly comprehend both the E-commerce Website and the table relationships in the project database design. You can also get a PDF copy of the conversation if you want to use it as a reference for your project.
ER Diagram for E-commerce Website [PDF]
The ER Diagram for E-commerce Website [PDF] provides the information explaining the concepts of project database. You can use this knowledge into your capstone project. You can also utilize it directly or adapt its content to meet the needs of your project.
The PDF File of ER Diagram for E-commerce Website is provided for you to have your own reference. Through this PDF file, you can modify the diagram or use the diagram into your project. This Entity Relationship Diagram for E-Commerce was given for free. You may have the ER diagram for e commerce website PDF by clicking the button below.
How to build ER Diagram for E-commerce Website
Time needed: 5 minutes.
Steps in building the ER Diagram for E-commerce Website with Cardinality Ratio.
- Step 1: Familiarize the ER Diagram (Entity Relationship Diagram) Symbols and Cardinality
Entity Relationship Diagram – shows the structure of data types in a project. It uses symbols to clarify its parts and relationships. Their symbols and applications must be familiarized before you build the ER Diagram.
ER Diagram Symbols:
• Fields : Fields are the parts of a table that define the entity’s characteristics. In the database that the ERD models, attributes are commonly thought of as rows.
• Keys : is a technique to categorize data qualities. It is used to organize ER diagrams and assist users in modeling their databases to ensure that they are efficient. This is also used to connect different tables in a database.
– Primary Key : identifies a single entity instance which means a unique attribute or set of attributes.
– Foreign Key : is produced when data attributes has one to many relationship with other entities.
ER Diagram Cardinalities:
The styling of a line and its termination demonstrate cardinality and ordinality.
The greatest number of times an instance of one thing can be related to instances of another entity is referred to as cardinality.
While Ordinality refers to the fewest number of times a single entity instance can be linked to another. - Step 2: Determine the targeted users
After the symbol familiarization, you’ll need to determine your targeted users. Your targeted users will be the ones to use your project.
Your project is E-commerce Website then your users would be the admin, book borrowers and librarian. You may ask the users of the common activities that they do when doing task in website. These information will help you in proceeding with the next step. - Step 3: Analyze the entities and their included attributes
Analyzation is very important in creating ER diagram. It will help you understand the work of the diagram and avoid the unwanted errors.
The gathered information from the users are very useful in creating the diagram. You will evaluate the data and pick the useful ones.
From this, you will see the possible data that will enter and exit the system. But only include the useful data related to website management. Then you’re ready for the next step. - Step 4: Plot the Entity Relationship Diagram
To plot the ERD you will need the entities, their attributes, and relationships. You will base the data structure from the evaluated information to have the exact Entity Relationship Diagram.
– To design the ER Diagram, you will list first all of the entities related to E-commerce Website.
– Then you will place the attributes included under them. This will help you create the ER Diagram Fields.
– Do not forget the keys of the attributes. The keys will generate the potential relationships between entities.
– Finally, you have your ER Diagram Completed.
Conclusion:
To summarize, we have discussed about the ER diagram for E-Commerce Website, and above we have the system database tables and their relationships.