Salon Management System Database Design Project
This is a sample of Salon Management System Database Design Project, It includes database schema design, Database tables and ERD for the management system for the salon.
Backgound
Salon Management System has a manual system that sometimes causes the customer to be annoyed or be bored because of the slow services.
Some customers just leave the salon because they don’t know if it’s already their turn or not also the salon doesn’t have a waiting area where people can sit and wait for their turns.
That is the reason for the proponent why they want to develop the salon management system. The system could lessen the bored and annoyed looks from the customers on the salon and also the system could help to improve the services of the said salon.
Salon Management System is focused on how to improve the system services of the salon. It is a stand-alone system that can be accessed by the admin which is the owner and the employees of the salon.
They need to have a computer to access the system. The admin can keep track of the inventory of products and add accounts of the incoming employees while the user will perform the queuing and the billing.
Salon Management System Database Design Features:
- Artist person skilled at a particular task
- Billing process of making out or sending the invoice
- Inventory complete listing of merchandise or stock
- Product article or substance that is manufactured or refined for sale
Entity Diagram of Salon Management System
Data Dictionaries
Table 1: tblcustomer
| Field Name | Description | Type | Length |
| Customer id | Customer ID number PK | Int | 11 |
| Customer name | Customer name | Varchar | 30 |
| Address | Customer address | Text | 30 |
| Contact number | Customer contact number | Int | 30 |
| Age | Customer age | Int | 30 |
| Payments | Customer payments | Int | 50 |
Table 2: tblemployee
| Field Name | Description | Type | Length |
| Employee id |
Employee id | Int | 11 |
| Employee name | Employee name | Varchar | 50 |
| Employee number | Employee number | Int | 12 |
| Address | Employee address | Text | 100 |
| salary | Employee salary | Int | 30 |
| Job title |
Employee job title | Varchar | 50 |
Table 3: tblservices
| Field Name | Description | Type | Length |
| Services id | Services id number | Int | 11 |
| Treatment | treatment name | varchar | 50 |
| quality | Quality number | varchar | 50 |
Table 4: tbltransaction
| Description | Type | Length | |
| Transaction id |
transaction id | Int | 50 |
| Customer id | Customer id | int | 50 |
| Customer name | Customer name | Varchar | 100 |
| Bill amount | Amount of bill | int | 30 |
Table
5:tblbills
| Field Name | Description | Type | Length |
|
Bill id |
bill id | Int | 11 |
|
Customer id |
Customer id | Int | 100 |
| Bill amount |
Bill amount | varchar | 30 |
| Price | Price | varchar | |
Conclusion
This Salon Management System Database Design Project is a requirement in the DBMS mini Project. if you want to develop your own Salon Management System, you can upgrade this database design to suit your requirements.
Related Articles you may Like
- ER Diagram for Sales and Inventory System Database Design
- Ordering System Database Design with ERD
- ER Diagram for Water Refilling Station System Database Design
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.
Adones Evangelista
Programmer & Technical Writer at PIES IT Solution
Adones Evangelista is a programmer and writer at PIES IT Solution, author of over 900 tutorials and error-fix guides at itsourcecode.com. Specializes in JavaScript, Django, Laravel, and Python error debugging covering ValueError, TypeError, AttributeError, ModuleNotFoundError, and RuntimeError, plus C/C++ and PHP capstone projects for BSIT students.
Expertise: JavaScript · Python · Django · Laravel · Error Debugging · C/C++
· View all posts by Adones Evangelista →