Database Design Project for PEPSI Monitoring Management System
This Database Design Project for PEPSI Monitoring Management System or PEPSI Distribution Monitoring Management System Database Design with ERD also takes the profit and expenses that they might also be written in a daily logbook and it is a hassle because you might come to an error that causes your own mistakes(Database Design for PEPSI Distribution Monitoring Management System with ERD and Tables).
Background
Pepsi Cola is a big company based in a different country that has assigned a person or branch owner to distribute their product in assigned area.
This kind of business needs a better system to use that can comply with their needs in an everyday transaction, monitoring and distribution of product to make easy for them to put the data of details in every transaction.
I made an effort to make this thing happen. I see the problem and the problem is until now the calculation of product sold is still manual and it takes more time to compute and put in the daily logbook of the product being distributed in a particular area assigned in every municipality or city.
Not only that, but I see the daily logbook of attendance of the employee of the said branch also still manual and the daily time record of the employees can be misplaced or can be broken because of human error.
That one is very important because they have a policy that no work no pay so if the logbook will misplace the payroll will be affected.
Added to this the human error can cost much money, to the business. I see the existing system in this branch that their system is only an inventory.
This management also needs to calculate the profit and expenses in every transaction.
Walk-in or distribution needs clear details in every transaction to prevent money loss and make this branch have a better income and away from debt(PEPSI Distribution Monitoring Management System Database Design with ERD ).
Pepsi distribution monitoring and management system often gives satisfaction to the user in terms of convenient time to calculate money of the branch , calculation payroll of employee, calculate profit and expenses of the branch , and the route of every vehicle in everyday distribution, added to this the easiest way to put data in a system through few typing in a text field, using Combobox to the other details of every transaction .
Database Design Project for PEPSI Monitoring Management System : FEATURES
- Monitored every transaction
- Safe to enter data
- Daily time record of the employee
- Money, profit and expenses calculation
Database Design Project for PEPSI Monitoring Management System : Data Dictionaries
These Database Design for PEPSI Distribution Monitoring Management System with ERD and Tables below provide the entire database tables details such as Field Name, Descriptions, data types, character lengths.
Table 1: tblclient
| Field Name | Description | Type | Length |
| Clnt_name | Name | varchar | 30 |
| Clnt_address | Adrress | varchar | 30 |
| Clnt_business | Business | varchar | 30 |
| Clnt_amount | Amount sold on product | Int | 11 |
| Clnt_date | Date of sales | varchar | 30 |
Table 2: tblemployee
| Field Name | Description | Type | Length |
| Empl_id | Employee ID Number | Int | 11 |
| Empl_Fname | First name | varchar | 30 |
| Empl_Lname | Last name | varchar | 30 |
| Empl_address | Adress | varchar | 30 |
| Empl_salary | Salary per week | Int | 11 |
Table 3: tblprodsold
| Field Name | Description | Type | Length |
| Pros_product | Kinds of product | varchar | 30 |
| Pros_amount | Amount of product sold | int | 11 |
| Pros_client | Name of client | varchar | 30 |
| Pros_date | Date of sales | varchar | 30 |
Table 4: tbldelivery
| Field Name | Description | Type | Length |
| Del_client | Client name | varchar | 30 |
| Del_business | Business | varchar | 30 |
| Del_address | adress | varchar | 30 |
| Del_amount | Amount sold on product | Int | 11 |
| Del_date | Date of delivery | varchar | 30 |
Table 5: tblproductinput
| Field name | Description | Type | length |
| Prdin_prodname | Product name | varchar | 30 |
| Prdin_quantity | Quantity of product | Int | 11 |
| Prdin_date | Date of input | varchar | 30 |
ER Diagram for Database Design Project for PEPSI Distribution Monitoring Management System
Pepsi Distribution, Monitoring And Management System Entity Relationship Diagram shows the system entity relationships in each entity and their supposed functions in each relationship.
Figure 1: Proposed Pepsi Distribution, Monitoring and, Management System
Figure 1 shows the proposed Pepsi Distribution, Monitoring And Management System Entity Relationship Diagram are the entity of the proposed Pepsi Distribution, Monitoring, And Management System database, which are presented by tables; the tables are made to meet the required specification of the system and provide a much more specific details of each entity within the system(Database Design for PEPSI Distribution Monitoring Management System with ERD and Tables).
For More Database Design Examples
- ER Diagram for Sales and Inventory System Database Design
- Ordering System Database Design with ERD
- ER Diagram for Water Refilling Station System Database Design
For Inquiry
If you have any question or suggestion about this Database Design Project for PEPSI Distribution Monitoring Management System. please contact or simply leave a comment 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
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 →
Really informative article post.Much thanks again.