ER Diagram Examples For Online Shopping Systems
ER Diagram Examples For Online Shopping Systems
Now that you understand what an ER diagram is. You might be thinking, how is it
related to Information systems? ER diagrams are handy in mapping out the functions
the software will perform and how it will link different entities together.
For example, if you are making an online shopping system, you might have to look at
the software from different perspectives. You need to consider the user interface, admin
interface, how the products will be identified and the whole billing process. An ERD
comes very handy here, where all entities are named and linked together to ensure the
software caters to them all.
Using an ER diagram, you can resolve many problems during the planning phase of the
information system rather than at the execution or testing phase. It allows you to map
all the information in a graphical manner that is easy to understand and interpret.
Moreover, an ERD helps identify all the data that needs to be stored in the database. By
linking entities, their attributes and their relationships, ERD helps determine all the
requirements of an information system during its initial phase.
Entity Relationship diagrams are very useful in creating an online shopping system. Here
are a few examples of taking inspiration from:
Example 1
This online shopping ERD maps out in detail all the critical entities, their attributes and
relationships. It gives the rough details of all the entities involved, from browsing to
payment. Creating an ERD for a shopping system can be beneficial to ensure that all the
important aspects are a part of your system.
https://www.edrawsoft.com/share-erd.html
How to Create an ERD for Online Shopping System
Now let’s follow a detailed strategy to help you build an online shopping system Step by
Step.
Step 1: Identify all the entity sets related to your database. The entity sets for an online
shopping system are:
First of all, you need to start with the Mobile Application or website. This shows that the
system is based on the software, and the main bridge between the customer and the
store is the website or application.
Step 2: Now, you need to assign attributes to each of these entities like those given
below:
Website/ Mobile Application
Customer
Attributes: Email, User ID, Password, Mobile Number, Customer ID, Country
Name, District, Address, Postal Code etc.
Admin
Product
Attributes: Product code, Product name, Product category, product price, product
availability.
Login/ Registration
Shopping Cart
Consider the rest of the entities like customers and products. The customers will need to
register and log in first in order to purchase items. They can select the products online
and put them in the shopping cart. The shopping cart will identify the product and its
price immediately. An admin needs to be on the other end, ensuring the transaction
goes smooth and there are no possible bugs. The admin can also offer support when
needed and add new products or remove any old ones.
Step 3: Identify the key attributes. The key attribute is one specific attribute that
uniquely identifies one entity from another in an entity set.
Product: Product ID
Customer: Customer ID
Admin: Admin ID
Website or Mobile App: Domain name
Shopping Cart: Product ID
Log in / Registration: Username
Step 4: Create an ER diagram. In order to create an information system, you will
need to map out the ER diagram first and then follow the steps using Java or
SQL. This is how you can easily create an Entity Relationship diagram by
identifying the entities and then connecting them to create a whole diagram.