Database Design for High School Enrollment System
The Database Design for High School Enrollment System for Cauayan National High school. The school will become efficient and productive with the help of the proper administration.
One function of an administration is the registrar’s office where confidential works are being managed. The traditional way of banking data’s are manually formed which offers less productive and security in terms of storing records.
Now, the advancement of technology is being introduced to eliminate the old system. This is a computerized enrollment system created in Java application to assist the enrollment process of the students in Cauayan National High School to cater the freshmen, transferees, and the old students.
With this advance computer enrollment system, CNHS can perform the following functions: (1) lessen the working time, (2) serves as the information saving bank(database), (3) less effort but giving more productivity, (4) lastly, can manage a mass number of student applicants.
This program is estimated to last for a lifetime if maintained well and can be done within 2-3 months of development.
FEATURES:
- To handle a max registration of the student.
- To process registration in less time workload
- Manage user and employee
- Generate and Process user-Friendly Reports
You can check here the sample Online Student’s Management System in PHP with Full Source Code (2020).
DATABASE DICTIONARIES
These tables below provide the entire database table description and details such field names, descriptions, datatypes and character length.
Table 1: tblStudent
| Field Name | Description | Type | Length |
|
Stud_ID (PK) |
ID number of the Student | INT | 11 |
| First_name |
First name of the Student | Varchar | 50 |
| Middle_name |
Middle name of the Student | Varchar | 50 |
| Last_name |
Last name of the Student | Varchar | 50 |
| Age |
Age of the Student | INT | 11 |
| Gender | Sexuality | Varchar | 50 |
| Address |
Where the student live | Varchar | 50 |
| Birthday |
When did the student born | Varchar | 50 |
| Birth_place |
Where did the student born | Varchar | 50 |
| Status |
Student’s status | Varchar | 50 |
| Nationality |
Student’s nationality | Varchar | 50 |
| Religion |
Student’s religion | Varchar | 50 |
| Stud_phonenum |
For emergency purposes | Varchar | 50 |
Table 2: tblStud_details
| Field Name | Description | Type | Length |
|
Detail_ID (PK) |
Details ID for recognition | INT | 11 |
|
Stud_ID (FK) |
ID number of the Student | INT | 11 |
| Fathers_name |
Student Father’s name | Varchar | 50 |
| Occupation |
Father’s work | Varchar | 50 |
| Mothers_name |
Student mother’s name | Varchar | 50 |
| Occupation |
Mother’s work | Varchar | 50 |
| Guardians_name |
Other Family support | Varchar | 50 |
| Occupation |
Guardian’s occupation | Varchar | 50 |
| Parents_address |
Where the part of Family live | Varchar | 50 |
| Parents_phonenum |
For emergency purposes | Varchar | 50 |
Table 3: tblRequirements
| Field Name | Description | Type | Length |
|
Requirements_ID (PK) |
Requirements ID for recognition | INT | 11 |
|
Stud_ID (FK) |
ID number of the Student | INT | 11 |
| NSO |
Live of Birth | boolean | 5 |
| Baptismal |
Registration of Baptism | boolean | 5 |
|
Entrance Exam Result |
To know whether the student passed or failed | Varchar | 50 |
|
Certificate of Transfer |
Transfer Records | boolean | 5 |
Table 4: tblTransaction
| Field Name | Description | Type | Length |
|
Trans_ID (PK) |
Payment ID for recognition | INT | 11 |
|
Stud_ID (FK) |
ID number of the Student | INT | 11 |
|
Employee_ID (FK) |
ID number of the Employee | INT | 11 |
| Particular_payables |
Names of payables | Varchar | 50 |
| Amount_paid |
Number of money payment | Varchar | 50 |
| Balance |
Amount of payments remain | ||
| Payment_date |
Date paid | Varchar | 50 |
| Payment_time |
Time paid |
Table 5: tblSchool_year
| Field Name | Description | Type | Length |
|
Stud_ID (FK) |
ID of the Student | INT | 11 |
| Year |
School year | INT | 11 |
| Semester |
Semester per year | Varchar | 50 |
Table 6: tblEmployee
| Field Name | Description | Type | Length |
|
Employee_ID (PK) |
ID of the Student | INT | 11 |
| First_name |
Employees’ Firstname | Varchar | 50 |
| Middle_name |
Employees’ middle name | Varchar | 50 |
| Last_name |
Employees’ lastname | Varchar | 50 |
Entity Relationship Diagram
Figure 1: Proposed Cauayan National High School Enrollment System Entity Relationship Diagram shows the system entity relationships in each entity and their supposed functions in each relationship.
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
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.
- PHP: Car Driving School Management System in PHP with Source Code
- VB.NET: Registration & Resolution of DependencyService in Xamarin.Forms
- Java: University Management System Project in Java With Source Code
- Python: Django Online College Admission System with Source Code
- Django: Django Online College Admission System with Source Code
- Laravel: School Management System in Laravel With Source Code
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 →