Database Design Project for Tourist Inn Reservation System
This Database Design Project for Tourist Inn Reservation System is to reduce extensive paperwork in currently used system which is manual. It is a user-friendly.
Same with Complete Hotel Management System, the owner and manager of the tourist inn can access this system to monitor all guest entering at the inn through the reports file.
They can reserve a rooms, can book also and can add another day to stay in.
Database Design Project for ZJM Tourist Inn Reservation System
The System For Tourist Inn Reservation Database Design Project provides a place for some travellers or guest in that location and running a business well.
It will great help for the Zjm Tourist Inn Reservation System Database Design Project to have an easy task for hotel to have an easy transaction for the guest and less time to saving the information.
This Project is responsible for keeping accurate records about reserving rooms that encode in this system. The guest can secure of their information.
The Zjm Tourist Inn was started on August 2018 located at Rivera Street, Barangay 3, Kabankalan City (infront of Golden Key Trading). This Inn can manage well the guests. Have a good design rooms, well organize.
Features:
- Room Reservation
- Search rooms
- Check in and Check out
- Issue bills
Data Dictionaries
These tables below provide the entire database tables details such as Field Name, Descriptions, data types, character lengths.
Table 1: tbl_guest
| Field Name | Description | Type | Length |
| Guest_id | Guest ID | Int | 11 |
| First_name | Firstname | Varchar | 50 |
| Last_name | Lastname | Varchar | 50 |
| Address | Address | Varchar | 50 |
| Phone_number | Phone Number | Varchar | 50 |
| Email_address | Email Address | Varchar | 50 |
Table 2: tbl_reservation
| Field Name | Description | Type | Length |
| Reservation_id | Reservation ID | Int | 11 |
| Guest_id | Guest ID | Int | 11 |
| Room_type_id | Room Type ID | Int | 11 |
| Check_in | Check In | Varchar | 50 |
| Check_out | Check Out | Varchar | 50 |
| Reservation_status | Reservation Status | Int | 11 |
Table 3: tbl_booking
| Field Name | Description | Type | Length |
| Booking_id | Booking ID | Int | 11 |
| Room_Type_id | Room Type ID | Int | 11 |
| Guest_id | Guest ID | Int | 11 |
| Check_in_datetime | Check In of Date and Time | Varchar | 50 |
| Check_out_datetime | Check Out of Date and Time | Varchar | 50 |
Table 4: tbl_
room_type
| Field Name | Description | Type | Length |
| Room_type_id | Room Type ID | Int | 11 |
| Room_type | Room Type | Varchar | 50 |
Table 5: tbl_room
| Field Name | Description | Type | Length |
| Room_id | Room ID | Int | 11 |
| Room_number | Room Number | Int | 11 |
| Room_type_Id | Room Type ID | Varchar | 50 |
| Room_price | Room Price | Int | 11 |
| Room_status | Room Status | Int | 11 |
Table 6: tbl_payment
| Field Name | Description | Type | Length |
| Payment_id | Payment ID | Int | 11 |
| Guest_id | Guest ID | Int | 11 |
| Reservation_id | Reservation ID | Int | 11 |
| Add_On | Add On the extra features | Varchar | 50 |
| Room_price | Room Price | Int | 50 |
| Number_of_nights | Number of nights | Int | 11 |
| Total | Total Charges | Int | 11 |
| Payment_status | Payment status | Int | 11 |
Entity Relationship Diagram
Entity Relationship Diagram shows the entity relationships in each entity and their supposed functions in each relationship.
Conclusion
This System for Tourist Inn Reservation Database Design Project is to produce a solution to overcome the problems that arise nowadays because of using current manual system. Provide fast access for the customers and for the Inn.
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
- Database Design for Customer Management System
- Database Design Project for Inventory Management System
- Laundry Management System Database Design
Inquiries
If you have any questions or suggestions about Database Design Project for Tourist Inn Reservation System, please let me know by dropping your 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 →