Database Design for Rice Delivery Sales and Inventory Management System
The Database Design for Rice Delivery Sales and Inventory Management System is a product of DBMS mini project.
This database design provides information about the customer; whoever uses the system can freely view the knowledge of the customer.
The network contains an inventory of the rice that is listed on its database. The system also manages the information and details of every rice listed and keeping track for the new delivery. It contains a functional database.
Tracking inventory as it is transported between locations. Receiving items into a warehouse or other area. Keeping track of product sales and inventory levels. Cutting down on product obsolescence and spoilage.
Features
The Rice Delivery Sales and Inventory Management System features
- Manage delivery
- Order Management
- Manage product
- Manage customer
Database Schema: Data Dictionaries
Table 1: customer
| FIELD NAMES | DESCRIPTION | TYPE | LENGTH |
| Customer_id | Customer id number | Int | 5 |
| Customer_fname | Customer first name | Varchar | 50 |
| Customer_lname | Customer last name | Varchar | 50 |
| Contact number | The contact number of customer | Varchar | 50 |
| address | Address of customer | Varchar | 50 |
Table 2: product
| FIELD NAMES | DESCRIPTION | TYPE | LENGTH |
| Rice_id | Rice id number | int | 5 |
| Rice_name | Name of the rice | varchar | 50 |
| price | Price of the rice | Double |
Table 3: transaction
| FIELD NAMES | DESCRIPTION | TYPE | LENGTH |
| Details_id | Details id number | Int | 5 |
| Rice_id | Rice id number | Int | 5 |
| Handler_name | Name of the handler | Varchar | 100 |
Table 4: type
| FIELD NAMES | DESCRIPTION | TYPE | LENGTH |
| Type_id | Type id number | int | 5 |
| Rice_age | Rice age number | Int | 5 |
| Rice_id | Rice id number | Int | 5 |
| class | Class name | Varchar | 50 |
Table 6: tbluser
| FIELD NAMES | DESCRIPTION | TYPE | LENGTH |
| User_id | The user id of the user | int | 5 |
| firstname | Firstname of user | Varchar | 50 |
| Lastname | Lastname of user | Varchar | 50 |
| username | Username of user | Varchar | 50 |
| Contact_number | The contact number of user | Varchar | 50 |
| address | Address of user | Varchar | 50 |
| password | Password of user | Varchar | 50 |
Entity Relationship Diagram
Based on Diagram, the Rice Delivery And Inventory Entity Relationship Diagram are entities of the database, represented as a table, are created and organized by providing connections within the database’s table with the idea of providing clear and decisive information to the user itself.
The proposed Database Design for Rice Delivery Sales and Inventory manage System ERD are the entity of the Rice Delivery Sales and Inventory management System database, which are presented by tables; the tables are made to meet the required specification of the system and provide much more specific details of each entity within the system.
This DBMS mini-project designed by ms. April May Gargarita.
If you have any questions or suggestion, please feel free to contact us or leave a comment below.
You can download here the inventory management systems pdf.
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.
- PHP: Stock Management System in PHP with Source Code
- VB.NET: Sales and Inventory Management System Project in VB.Net Source Code
- Java: Point Of Sale (POS) In Java With Source Code
- Python: Django Warehouse Management System with Source Code
- Django: Django Warehouse Management System with Source Code
- Laravel: [Complete] Sales and Inventory Management System in Laravel
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.
Joken E. Villanueva
Founder & Lead Developer at PIES IT Solution
Founder of PIES Information Technology Solutions, a software company building production-grade applications for institutions across the Philippines. Over 8 years of hands-on full-stack development experience, currently leading the development of ClinicAI, an AI-powered clinic management platform.
Expertise: PHP · MySQL · JavaScript · AI Integration · SaaS Architecture · VB.NET · Database Design · Capstone Documentation · Java
· View all posts by Joken E. Villanueva →