Pet Shop Management System ER Diagram
The capstone project entitled Pet Shop Management System is a transaction processing system designed and developed in PHP, MySQL and Bootstrap. It is a multi-vendor platform that allows the different shop owners to post their products (pets, pet products and services as well). The system has the administrator and moderators that helps in the transactions and for customer service purposes.
You may visit and read the articles posted in relation to Pet Shop Management System
- Pet shop Management System Database Design
- Online Veterinary and Pet Shop Management Information System
This article will discuss the step by step process on how to prepare the entity relationship diagram or ERD of the project entitled Pet Shop Management System.
The first step in the development of the Pet Shop Management System is to prepare the ER diagram that will serve as the basis later on in the creation of the actual database.
We will create and explain the process of making the entity relationship diagram of Pet Shop Management System.
Let’s start from the symbols used in the ER Diagram.
Entity is represented by the rectangle shape. The entity will be our database table of Pet Shop Management System later on.
Attribute is represented by the oval shape. This will be the columns or fields of each table in the Pet Shop Management System.
Relationship is represented by diamond shape. This will determine the relationships among entities. This is usually in a form of primary key to foreign key connection.
We will follow the 3 basic rules in creating the ER Diagram.
- Identify all the entities.
- Identify the relationship between entities and
- Add meaningful attributes to our entities.
Step 1. In the Pet Shop Management System we have the following entities
- User
- User Group
- Pet
- Pet Category
- Pet Product
- Pet Product Category
- Order
- Order Detail
- Customer
- Vendor
- Payment
- Service
Our design of Pet Shop Management System consists of 12 entities; the specified entities will be our database tables in the design and implementation of Pet Shop Management database schema.
We will now draw the entities of the Pet Shop Management System specified above and it will be represented by a rectangle shape. The image below is the entities identified in the scope of the Pet Shop Management System.
Step 2. After we have specified our entities, it is time now to connect or establish a relationship among the entities.
- User of the system belongs to a specific user type or group that corresponds with their role and permissions. The user group includes the functions the user can access (1 to 1 relationship).
- The user (administrator, moderator) encodes, updates, manages and reviews the pet products posted by the vendors (1 to many relationship).
- The pet product belongs to a specific pet product category (1 to 1 relationship).
- The user (administrator, moderator) encodes, updates, manages and reviews the pet information posted by the vendors (1 to many relationship).
- The pet information belongs to a specific pet category (1 to 1 relationship).
- The user (administrator, moderator) encodes, updates, manages and reviews the vendor information (1 to many relationship).
- The user (administrator, moderator) encodes, updates, manages and reviews the services information posted by the vendor (1 to many relationship).
- The vendor can post pet and product information (1 to many relationship).
- Vendor can also post the services they offer (1 to many relationship).
- The customer selects an item and places their orders (1 to many relationship).
- An order consists of itemized detail stored in the order detail (1 to many relationship).
- The user processes the orders and payments as well (1 to many relationship).
Step 3. The last part of the ERD process is to add attributes to our entities.
User Entity has the following attributes:
- User ID – primary key represented with underline
- Username
- Password
- Fullname
- Avatar
- Contact
- User Category – foreign key
- Status
User Group Entity has the following attributes:
- User Group ID – primary key represented with underline
- Name
- Description
- Allow Add
- Allow Edit
- Allow Print
- Allow Export
- Allow Import
- Allow Delete
Pet Entity has the following attributes:
- Pet ID – primary key represented with underline
- Pet Description
- Pet Category ID – foreign key
- Vendor ID – foreign key
- Pet images
- Pet Status
- User ID – foreign key
Pet Category Entity has the following attributes:
- Pet Category ID – primary key represented with underline
- Pet Category Name
- User ID – foreign key
Pet Product Entity has the following attributes:
- Pet Product ID – primary key represented with underline
- Product Code
- Product name
- Product Detail
- Product Category ID – foreign key
- Quantity on hand
- Vendor Price
- Retail Price
- Discount
- Status
- Vendor ID – foreign key
- User ID – foreign key
Pet Product Category Entity has the following attributes:
- Pet Product Category ID – primary key represented with underline
- Category Name
- User ID – foreign key
Order Entity has the following attributes:
- ID – primary key represented with underline
- Reference No
- Customer ID – foreign key
- Order Date
- Order Status
- Expected Delivery Date
- Number of Items
- Total Amount
- User ID – foreign key
Order Detail Entity has the following attributes:
- Order Detail ID – primary key represented with underline
- Order ID – foreign key
- Pet Product ID – foreign key
- Quantity
- Quantity Price
- Status
- Remarks
- Vendor ID – foreign key
Customer Entity has the following attributes:
- Customer ID – primary key represented with underline
- Customer Code
- Customer Name
- Avatar
- Email Address
- Contact Number
- Complete Address
- Username
- Password
Vendor Entity has the following attributes:
- Company ID – primary key represented with underline
- Company Name
- Company Contact Person
- Company Email
- Company Contact Number
- Company Website
- Company Profile
- Vendor Username
- Vendor Password
- User ID – foreign key
Payment Entity has the following attributes:
- Payment ID – primary key represented with underline
- Reference No
- Payment For
- Amount Paid
- Remarks
- Payment Status
- Paid By
- User ID – foreign key
Service Entity has the following attributes:
- Service ID – primary key represented with underline
- Service Name
- Reference No
- Service Detail
- Service Fee
- Vendor ID – foreign key
- User ID – foreign key
Note: all attributes with underline represents the primary key of the entity or table.
The next step is to convert the plan designed on ER Diagram into the actual database, please search for the Pet Shop Management System article which was already posted.
Contact us on our facebook page for the softcopy of the Pet Shop Management System.
You may visit our facebook page for more information, inquiries and comments.
Hire our team to do the project.
