In our final project, my friend and I created a user-friendly Database Management Software for Wisdom Kindergarten. It streamlines student information management, including health records and outstanding balances, while enhancing administrative operations. The software facilitates smooth communication among users and simplifies kindergarten administration. Key features include tracking student details, managing guardian information, recording student progress, tracking health records, managing classrooms and subjects, and monitoring finances. Overall, our project aims to improve efficiency and decision-making in kindergarten management

1. 1
Group #8
Lakpa Yanzi Sherpa (1370468)
Keshab Luitel
CSCI 3423.50
Final Project Part 2 – Project Implementation
Name of the Kindergarten: Wisdom Kindergarten
This is the progress of the second phase. Other requirements can be added as we move on
where necessary.
Project goal:
This project involves creating a user-friendly Database Management Software for
Wisdom Kindergarten. The software streamlines the management of student
information, including health records and outstanding balances, while enhancing
administrative operations and decision-making. It efficiently handles data about
guardians, students, teachers, health records, finances, subjects, and classrooms,
enabling easy student tracking, health insights, financial planning, and progress
monitoring. The software also fosters smooth communication among users and
facilitates connections between guardians, teachers, and students, simplifying
kindergarten administration.
Database Description:
The database will store data related to 8 entities which include:
Student,Guardian,Teachers,HealthRecord,Finances, Progress.classroom and subject.
Benefits:
Store and keep track of student details like names,date of birth.
store and manage guardian details like names,phone numbers.

2. 2
Store and manage teacher information such as name,prefessional qualification.
Record student progress
Keep track of health records such as allergies of students.
Manage classrooms and subjects.
Manage finances by monitoring payment status and deadlines.
Data Model & Design:
ER DIRAGRAM
Below is the attachment of the relational schema based on the ER diagram, which is
above,

3. 3
Business rules:
1.Phone number maybe optional to teachers.
2.Each guardian can provide one or more phone contact.
3.Student can have an allergie to multiple items.
4.Each student makes specific payment.
5.Each payment has a status like overdue.
6.Each student has one progress record.
7.Each student has one health record.
8.Each student has one or more guardian.
9.Teachers can be linked to one or more students.
10.classroom can be linked to one or more students.
11.Subject can be linked to one or more students.
Data dictionary:

4. 4
Student Table:
Field Name Data Type Field Length Constraint
StudentID (PK) CHAR 2 NOT NULL
StudentFirstName VARCHAR 20 NOT NULL
StudentLastName VARCHAR 20 NOT NULL
StudentGender CHAR 1 NOT NULL
StudentContactNumber NUMERIC 10
StudentDateOfBirth DATE - NOT NULL
Guardian Table:
Field Name Data Type Field Length Constraint
GuardianID (PK) CHAR 3 NOT NULL
GuardianFirstName VARCHAR 20 NOT NULL
GuardianLastName VARCHAR 20 NOT NULL
GuardianPhone NUMERIC 10 NOT NULL
GuardianRelation VARCHAR 10 NOT NULL
GuardianAddress VARCHAR 40 NOT NULL
Teacher Table:
Field Name Data Type Field Length Constraint
TeacherID (PK) CHAR 3 NOT NULL
TeacherName VARCHAR 20 NOT NULL
TeacherSalary NUMERIC 6,0 NOT NULL
TeacherEmail VARCHAR 50
TeacherPhone NUMERIC 10
HealthRecord Table:
Field Name Data Type Field Length Constraint
PolicyNumber (PK) CHAR 5 NOT NULL
Immunized CHAR 1 NOT NULL
PolicyExpirationDate DATE - NOT NULL
StudentID (FK) CHAR 2 NOT NULL
Progress Table:
Field Name Data Type Field Length Constraint
ProgressID (PK) CHAR 3 NOT NULL
StudentGrade CHAR 1 NOT NULL
StudentStanding VARCHAR 15 NOT NULL
StudentID (FK) CHAR 2 NOT NULL
Finances Table:
Field Name Data Type Field Length Constraint

5. 5
FinanceID (PK) CHAR 3 NOT NULL
TuitionDueAmount NUMERIC 6,2 NOT NULL
TuitionDueDate DATE - NOT NULL
StudentID (FK) CHAR 2 NOT NULL
Subject Table:
Field Name Data Type Field Length Constraint
SubjectID (PK) CHAR 3 NOT NULL
SubjectName VARCHAR 20 NOT NULL
TeacherID (FK) CHAR 3 NOT NULL
Classroom Table:
Field Name Data Type Field Length Constraint
ClassroomID (PK) CHAR 3 NOT NULL
TeacherID (FK) CHAR 3 NOT NULL
StudentID (FK) CHAR 2 NOT NULL
Belongsto Table:
Field Name Data Type Field Length Constraint
BelongstoID (PK) CHAR 3 NOT NULL
GuardianID (FK) CHAR 3 NOT NULL
StudentID (FK) CHAR 2 NOT NULL
Implementation:
Creating the database for each table
student Table
The table stores student information, such as their unique ID (studentid), first and
last names, gender, optional contact number, and date of birth.

6. 6
guardian Table:
This table holds details about guardians. Each guardian has an ID (guardianid) along
with their names, phone number, relation to the student, and address.
teacher Table

7. 7
The teacher table contains information about teachers. Each teacher has an ID
(teacherid), name, salary, email, and phone number.
healthrecord Table
This table tracks health-related records. It includes a policy number (policynumber),
an indication of whether the student is immunized (immunized), policy expiration
date, and a reference to the student the record is linked to (studentid).

8. 8
progress Table
the progress table records academic progress. Each entry has a unique ID
(progressid), the student's grade, their standing, and it is linked to the respective
student which is studentid.
finances Table

9. 9
Finance is managed in this table. Entries have IDs (financeid), the amount of tuition
due (tuitiondueamount), the due date (tuitionduedate), and a reference to the
student (studentid).
subject Table
In the subject table each subject has an ID (subjectid), a name (subjectname), and is
associated with a teacher through a teacher ID reference (teacherid).

10. 10
classroom Table
In the classroom table each classroom has an ID (classroomid), is associated with a
teacher through a teacher ID reference (teacherid) and can have students linked via
their student IDs (studentid).
Belongsto Table
Establishes student-guardian relationships by connecting students and their
respective guardians, offering insights into family associations.

11. 11
b. Populating the data for the table.
The following collection of Screenshot code that populates the specific table with
data for 20 different data.
The attached screenshot displays the code employed to populate the 'student' table
with 20 distinct entries.
The attached screenshot displays the code employed to populate the 'guardian'
table with 20 distinct entries.

12. 12
The attached screenshot displays the code employed to populate the 'teacher' table
with 20 distinct entries.
The attached screenshot displays the code employed to populate the 'healthrecord'
table with 20 distinct entries.

13. 13
The attached screenshot displays the code employed to populate the 'progress' table
with 20 distinct entries.
The attached screenshot displays the code employed to populate the 'finances' table
with 20 distinct entries.

14. 14
The attached screenshot displays the code employed to populate the 'subject' table
with 20 distinct entries.
The attached screenshot displays the code employed to populate the 'classroom'
table with 20 distinct entries.

15. 15
The attached screenshot displays the code employed to populate the 'belongsto'
table with 20 distinct entries.

16. 16
III. Queries
In the Group database project below are the queries we executed together with an explanation
of what each does.
1.A simple select with ordering query.
This query retrieves firstname,lastname and date of birth column from the wisdom table and
orders them by firstname.In default they are arranged in descending order

17. 17
This query retrieves and displays essential details of guardians. It selects columns
including (guardianid, guardianfirstname, guardianlastname, guardianphone, and
guardianrelation )from the guardian table. The resulting output showcases these
specific attributes for each guardian.
2.A medium query
The query calculates number of students above the threshold by calculating rows in finances
table where tutionamount is greater than 5000.

18. 18
1. B
3.A Join and grouping with aggregate function query
The table uses a Left join with health table to retrieve the firstname,lastname and the
immunized related to ‘Y’and then groups the results in either by studentid,
firstname,lastname

19. 19
3.B
4.A subquery:

20. 20
The query uses a subquery to find student id where immunized include ‘Y’ AND then selects
there corresponding names.
5.Inner Join query
The query returns studentfirstname,studentlastname and tutuitionamount for all students.

21. 21
5. B.
The query returns studentfirstname,studentlastname,subjectname and teachername for all
students under a join on subjected on teacherid

22. 22
6.A View query
The query creates a view named StuGurdianview that retrieves first name ,last name and
tuitionamount for students who have made payments as recorded in the finances table.Uses
inner join to combine data from the two tables finances and student tables.

23. 23
7.A union query
The query combine information about guardian and students in a single result.it retrives first
and last name and recordA(student or guardian)for both student and guardian from their
respective tables.

24. 24
7.B
8.query with order by limit.
The query retrieves last 5 records from the teacher table.

25. 25
9.Query with multiple condition
The query selects all records from the teacher table where teachersalary LIKE%170000%
AND teacheremail LIKE’%example.com’