Supply Management System Database Design with ERD (2026)

Supply Management System Database Design with ERD

This Supply Management System Database Design with ERD or Database Design for Supply Management System with ERD and Tables is programmed using Java for the fastest and convenient monitoring of JB Blocks and Supplies.

This system will help the owner to manage their products to avoid the unexpected problems.(ER Diagram for Product Supplies Management System)

JB BLOCKS AND SUPPLIES are owned by Jake Ann and Andrew Leyden. Their business is a hardware supplies, it consist of 7 employees to help them from their business.

JB BLOCKS AND SUPPLIES accepting payments like good as cash, instalment and cash on delivery it depends on what client’s availability.

JB Blocks and Supplies was build last June 25, 2018 by the Leyden couple with the help of their own family and it goes well and their celebrating their 1st anniversary on 25th of June 2019.

They offer household tools and located at Meñez Street Barangay 4 Himamaylan City Negros Occidental.(ER Diagram for Product Supplies Management System)

JB Blocks and Supplies have their own truck so that it’s not hard for them and to the customer to deliver the products, it’s free delivery for customers and sometimes they give discount to their solid buyers.

We all know that being new to the field of business and it’s not easy to run it without the help of computer.

This system will minimize the unexpected problems during their monitoring, this system contains the quantity of the products added and deducted everyday so that the owner can monitor the remaining supplies and how many has been sold, and how many profit they gain for each product. (ER Diagram for Product Supplies Management System)

This will get the personal information of the client every time they have transaction so that they can verify the identity of the clients including it’s Name, Location, Id number.

Also in this system includes the information of the employees and their hired dates, salary and employee Id so that the owner can monitor all employees on duty and to avoid a illegal transaction between employee and client or between both employee.(Database Design for Supply Management System with ERD and Tables)

Supply Management System Database Design with ERD : Features

Manage Customer
Stock Monitoring

Supply Management System Database Design with ERD : Data Dictionaries

TABLE 1 : TBLCUSTOMER

FIELD NAME	DESCRIPTION	TYPE	LENGHT
Customer_Id (PK)	Customer Id number	Int	11
First_name	Customer first name	Varchar	50
Last_name	Customer last name	Varchar	50
City_address	Customer city address	Varchar	50

TABLE 2 : TBLEMPLOYEE

FIELD NAME	DESCRIPTION	TYPE	LENGHT
Product_id	Product id number	Int	11
Product_name	Product name	Varchar	50
Quantity	Quantity	Int	11
Price	Price	Int	11

TABLE 3 : TBLPRODUCTS

FIELD NAME	DESCRIPTION	TYPE	LENGHT
Product_id	Product id number	Int	11
Product_name	Product name	Varchar	50
Quantity	Quantity	Int	11
Price	Price	Int	11

TABLE 4 : TBLSUPPLIER

FIELD NAME	DESCRIPTION	TYPE	LENGHT
Supplier_Id (PK)	Supplier Id number	Int	7
Supplier_name	Supplier name	Varchar	50
Supplier_address	Address of supplier	Varchar	50

TABLE 5 : TBLTRANSACTION

FIELD NAME	DESCRIPTION	TYPE	LENGHT
Transaction_Id	Transaction Id number	Int	11
Customer_Id (FK)	Customer Id number	Int	11
Employee_Id (FK)	Employee Id number	Int	11
Products_Id (FK)	Products Id number	Int	7
Supplier_Id (FK)	Supplier Id number	Int	7

Supply Management System Database Design with ERD : Entity Relationship Diagram

Database Design for JB BLOCKS & SUPPLIES Monitoring Management System

For More Database Design Examples

How to read an ER diagram

An entity-relationship (ER) diagram documents the database schema: entities (tables), attributes (columns), and relationships (foreign keys and cardinality).

Entity. Rectangle representing a table.
Attribute. Oval or field for each column.
Primary key. Underlined attribute name.
Foreign key. Attribute referencing another entity.
Relationship. Diamond or line connecting related entities.

Common capstone mistakes to avoid

Many-to-many without junction table.
Missing primary key.
Denormalized redundancy.
Ambiguous naming.

Where this diagram fits in Chapter 3

Section 3.3 (Database Design).
Include the CREATE TABLE SQL script alongside.
Reference from the class diagram.
Include a legend to explain the notation for panel members.

Official documentation

Frequently asked questions

What is a ER diagram used for in BSIT capstone?

An ER diagram shows the database schema: entities (tables), attributes (columns), and relationships (foreign keys, cardinality). It goes in Chapter 3 alongside the class diagram to communicate the data storage design.

What tool should I use to draw the ER diagram?

Free options: draw.io, Lucidchart free tier, PlantUML, StarUML 30-day trial, Visual Paradigm Community Edition. Paid options: Microsoft Visio, Lucidchart pro, Enterprise Architect. For BSIT capstones, draw.io is the most commonly used free tool.

How detailed does the ER diagram need to be for capstone defense?

Panel members expect the diagram to match the actual system implementation. Include every major class/use case/entity relevant to the system. Omit trivial helper classes. Every diagram element should have a clear justification.

Should I use black-and-white or colored diagrams?

Black-and-white is standard for capstone documentation to match the thesis format. Use color only if it improves clarity. Ensure text is readable at printed size (10pt minimum for labels).

Where does this diagram go in the capstone documentation?

Chapter 3 (System Design and Methodology) typically holds all UML diagrams. Introduce each diagram with a 1-paragraph description explaining what it shows and how to read it.

Frequently asked questions

What is a ER diagram used for in BSIT capstone?

What tool should I use to draw the ER diagram?

Free options: draw.io (browser-based, saves to Google Drive), Lucidchart free tier, PlantUML (text-based, version-controllable), StarUML (30-day trial then reduced feature set), Visual Paradigm Community Edition. Paid options: Microsoft Visio, Lucidchart pro, Enterprise Architect. For BSIT capstones, draw.io is the most commonly used free tool.

How detailed does the ER diagram need to be for capstone defense?

Should I use black-and-white or colored diagrams?

Black-and-white is standard for capstone documentation to match the thesis format. Use color only if it improves clarity (e.g., grouping subsystems). Ensure text is readable at printed size (10pt minimum for labels).

Where does this diagram go in the capstone documentation?

Chapter 3 (System Design and Methodology) typically holds all UML diagrams. Introduce each diagram with a 1-paragraph description explaining what it shows and how to read it. Reference specific elements in the surrounding text so panel members can follow the design rationale.

Mary Grace G. Patulada

Programmer & Technical Writer at PIES IT Solution

Mary Grace G. Patulada (pen name ‘Nym’) is a programmer and writer at PIES IT Solution with a BSIT background from Carlos Hilado Memorial State College, Binalbagan Campus. Authored 370+ UML diagram tutorials and capstone documentation guides at itsourcecode.com. Specializes in UML (class, use case, activity, sequence, component, deployment), DFD, and ER diagrams for BSIT capstone projects.

Expertise: UML Diagrams, DFD, ER Diagrams, Use Case Diagrams, Activity Diagrams, Capstone Documentation, PHP · View all posts by Mary Grace G. Patulada →

Supply Management System Database Design with ERD