Database Design for Income Monitoring Management System
The Database Design for Income Monitoring Management System is a product of database design projects. This income monitoring system is developed to easily store information and monitor monthly income.
It shows the owner how to easily handle income without any difficulty as to manual monitoring. If he wants to know about how his monthly income sales and the product purchased, he can use and open it, so that he’ll know how his business works.
This database design for income monitoring system is a versatile business management software that seamlessly integrates all of your stock manager accounting and reporting processes in one day to use package.
It is also develop for customers and users satisfaction, then it is design to understand how your business works-and how to optimize your processes the advanced window based software is infinity adaptable.
It can be configured to suit your individual business needs. This system is enjoyable to use, you will never become wearisome.
FEATURES:
Database Design Example for Income Monitoring Management System Features
- Store Records (History) in which you can see the previous purchased product and the previous income.
- Easy and faster monitoring
- Easy and faster monitoring
- Organized information
- Accurate updates of information
Data Dictionaries
TABLE 1 USERS_TABLE
| FIELD NAME | DESCRIPTION | TYPE | LENGTH |
| USER_ID |
Id number of user | Int | 30 |
| USERNAME |
Sure name of the user | Varchar | 50 |
| PASSWORD | Password | Varchar | 50 |
| FIRSTNAME |
Name of the user | Varchar | 50 |
| LAST_NAME |
Sure name of the user | Varchar | 50 |
| GENDER |
Gender of the user | Varchar | 30 |
| CONTACT | Contact number | Varchar | 50 |
| ADDRESS |
Address of the user | Varchar | 50 |
| DATE | Date | Timestamp |
TABLE 2 TRANSACTION_TABLE
| FIELD NAME | DESCRIPTION | TYPE | LENGTH |
| USER_ID |
Id number of the user | Int | 30 |
| COSTUMER_ID |
Id number of the costumer | Int | 30 |
| PRODUCT_ID |
Id number of the product | Int | 30 |
| COSTUMER NAME |
Name of the costumer | Varchar | 30 |
| PRODUCT |
Name of the product | Varchar | 30 |
| PRICE | Price | Int | 11 |
| QUANTITY | Quantity | Int | 11 |
| TAX | Tax | Int | 11 |
| TOTAL_PRICE | Total price | Int | 11 |
| AMOUNT_TENDERED | Cash on hand | Int | 11 |
| CHANGE | Change | Int | 11 |
| NET | Net | Int | 11 |
| DATE | Date | Timestamp |
TABLE 3 CUSTOMER_TABLE
| FIELD NAME | DESCRIPTION | TYPE | LENGTH |
| COST_ID |
Id number of the costumer | Int | 30 |
| COST_NAME | Name of the costumer | Varchar | 50 |
| COST_NUMBER |
Contact number of the costumer | Varchar | 50 |
| COST_ADDRESS |
Address of the costumer | Varchar | 50 |
TABLE 4 INCOME_TABLE
| FIELD NAME | DESCRIPTION | TYPE | LENGTH |
| USER_ID | Users id | Int | 11 |
| PRODUCT_ID | Products id | Int | 11 |
| PRICE | Price | Int | 11 |
| QUATITY | Quantity | Int | 11 |
| TAX | Tax | Int | 11 |
| TOTAL_PRICE | Total price | Int | 11 |
| DATE | Date | Timestamp |
TABLE 5 PRODUCT_TABLE
| FIELD NAME | DESCRIPTION | TYPE | LENGTH |
| PRODUCT_ID | Products id | Int | 11 |
| PRODUCT_NAME |
Name of the product | Varchar | 50 |
| PRODUCT_PRICE |
Price of the product | Int | 11 |
ENTITY RELATIONSHIP DIAGRAM
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
- Database Design for High School Enrollment System
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 →