Rice Milling Management System Database Design With Table...

Bolaloy’s Rice Milling Management System Database Design

The Bolaloy’s Rice Milling Management System Database Design is a database design system that makes the work of a cashier or a user easy.

This kind of system is having an attribute of what you called, saving the data where you entered the information of customer in the said system.

This system is also having automatic computing of the cost of a product or item.

The Rice Milling Management System is easy to use. Like for instance, the user will fill-up the form according to or based on the information and identification of the customer.

And it has a solution provided or guide for you to be not lost in the procedure. And talking to the quality of a system, the efficiency, learnability, and effectiveness are used in creating in this system.

Bolaloy’s Rice Milling Management System Background and Features

Background

Bolaloy’s Rice Milling Management System is installed in Brgy Rumirang Municipality of Isabela Negros occidental. The name of the System is derived from the last name of the owner.

Features

Manage customer
Save Personal information
Computing cost
Check remaining stocks

Data Dictionaries

These tables below provide the complete database tables details such as Field Name, Descriptions, data types, character lengths.

Table 1: tblStocks

Field Name	Description	Type	Length
Stocks_id	Stocks number	int	11
Co_id	Customer id	Int	11
Co_fName	Customer-first name	Varchar	50
Co_lName	Customer Last name	Varchar	50
Job_id	Job title	Varchar	50
Phone_no	Customer contact	Varchar	50
RiceCode	Rice_Code	Int	7
RiceVariety	Rice_Name	Varchar	50
SackQty	Rice_count	Int	11
Date_Stored	Date of when Stored	Date	10

Table 2: tblcustomer

Field Name	Description	Type	Length
Customer_id	Customer number	int	11
fname	Customer-first name	Varchar	50
lName	Customer last name	Varchar	50
Address	Customer address	Varchar	50
Job_id	Job title	Varchar	50
Contact_No.	Customer contact	Varchar	50

Table 3: tblemployee

Field Name	Description	Type	Length
emp_id	Stocks number	int	11
First_name	Customer-first name	Varchar	50
Last_name	Customer last name	Varchar	50
Email	Customer Email	Varchar	50
address	Address	Varchar	50
contact_no	Employee Contact no	Varchar	50
hire_date	Hire date	Date	11
Job_id	Job title	Varchar	50
Monthly_salary	employee salary	Int	11

Table 4: tblricehistory

Field Name	Description	Type	Length
Customer_id	Customer number	int	11
r_Code	Rice code	Varchar	50
r_Variety	Rice Variety	Varchar	50
r_qty	Rice quantity	Int	50
r_Price	Rice price	Int	50
r_Total	Rice total	Int	50
Amount	Amount	Int	11
Change	Change	Int	50
historyDate	History Date	Date	11

Table 5: tblRecords

Field Name	Description	Type	Length
Costumer_id	customer information	Int	7
cFname	Customer-first Name	Varchar	50
cLname	Customer last name	Varchar	50
Address	CustomerLocation	Varchar	50
Contact_no	Customer No.	Int	11
Rice_id	RiceInformation	Varchar	50
Rice_Code	Rice Code	Int	11
Variety	Rice Name	Varchar	50
Rice_Volume	Rice Quantity	Int	11
Price_per_sack	Rice Price Per Sack	Int	11
SubTotal	Overall total cost	int	11
storedDate	Date when Stored	Date	11

Entity Relationship Diagram

Bolaloy’s Rice Milling and Sales System Entity Relationship Diagram show the system entity relationships in each entity and their supposed functions in each link.

Figure 1. Bolaloy’s ER Diagram for Rice Milling Management System

The proposed Bolaloy’s Rice Milling Management System Entity Relationship Diagram are the entity of the proposed Bolaloy’s Rice Milling Management System Database Design, 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.

Download the full documentation of Rice Milling Management System Database Design PDF here. lastCommitBolaloy

For another free material on database design.

If you have any questions or suggestion, please feel free to contact us or you can leave a message below.

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 →

Bolaloy’s Rice Milling Management System Database Design

Bolaloy’s Rice Milling Management System Database Design