Database Design Project For Monitoring Management System
This Feeds Supply Monitoring Management System Database Design Project with ERD, Tables is designed for Final Year Requirements DBMS Mini projects.
The Feeds Supply was founded year 2010. Due to Boar Services that the family owns they decided to add another business that is related to their first business.
This supply management System is made to lessen their manual work especially on making big transactions to customers.
This will secure all the data and information of customers as well as the transactions towards the client. If the item is unavailable the system will immediately notify the owner.
This will help them a lot in monitoring their products because it is more convenient than using manual writing for the transaction. This will also avoid mistakes in monitoring your products.
This will give you the exact number of products that are available and the products that were bought by your costumers.
Instead of computing everything through the calculator and encode the products that they bought by means of paper and ballpen this will you calculate and review each product.
Each item has its own respective price located at the bottom of the product. This will avoid using a lot of time to find the exact price of each product.
Past transactions can browse too. If you want to review something about your clients or the products they bought the system will automatically flash past transactions according to the data you want to take.
As per the products the supplier price will be shown in the system and also the market price. This will determined their profit. This will help them monitor their products as well as their profit.
Adding the transaction for supplier and the owner will be one of the features of this system.
Features:
- Monitor Products
- Monitor records of customer
- Monitor daily transactions
Data Dictionaries
TBL1:TBLCUSTOMER
| Field Name | Description | Type | Length |
| Customer_id | Customer ID number | int | 10 |
| Fname | First name of customer | varchar | 50 |
| Lname | Last name of customer | varchar | 50 |
| Address | Customer Address | varchar | 90 |
TBL2:TBLEMPLOYEE
| Field Name | Description | Type | Length |
| Employee_id | Employee ID number | int | 10 |
| Fname | Employee First Name | varchar | 50 |
| LName | Employee Last Name | varchar | 50 |
| Age | Age of Employee | int | 5 |
| Address | Address of Employee | varchar | 50 |
| Contact_number | Contact Number of Employee | varchar | 20 |
TBL3:TBLORDER
| Field Name | Description | Type | Length |
| Order_id | Order ID number | int | 10 |
| Product_id | Products ID number | int | 10 |
| Date_order | Date ordered of customer | varchar | 50 |
| Quantity | Customer suggested products | int | 10 |
| Price | Price of the products | int | 30 |
| Status | Available or not | varchar | 30 |
TBL4:TBLPRODUCTS
| Field Name | Description | Type | Length |
| Product_id | Product ID number | int | 10 |
| Product_name | Name of the product | varchar | 90 |
| Product_brand | Brand of Product | varchar | 90 |
| Quantity | Quantity of Product | varchar | 10 |
| Price | Price of the Product | varchar | 10 |
TBL4:TBLSUPPLIER
| Field Name | Description | Type | Length |
| Supplier_id | Supplier ID number | int | 10 |
| Product_id | Product ID number | int | 10 |
| First_Name | First Name of the Supplier | varchar | 90 |
| Last_name | Last name of supplier | varchar | 90 |
| Supplier_Address | Address of the Supplier | varchar | 90 |
| Contact_number | Contact number of the supplier | varchar | 30 |
| Received | Recieved date of Product | date |
Entity Relationship Diagram for Feeds Supply Monitoring Management System in Database design Project
Feeds Supply Monitoring Management System entity diagram show how the systems entity with and their function with each other.
Database Design Project For Monitoring Management System Document Here.
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
Official documentation
Working source code for this system
Download the actual implementation of this system in your preferred language. Each project includes source code, database, and setup instructions for BSIT capstone use.
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?
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 (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?
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. Aim for 1-2 diagrams that fully cover the system, not many partial ones.
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 →