Table of Content

1. Executive Summary 2

2. Motivation, Vision & Mission 3

2.1 Motivation 3

2.2 Vision 3

2.3 Mission 3

3. Project Summary 4

3.1Target Users 4

3.2 ER Diagram 5

3.3 System Flow Diagram 7

3.4 Advantages of the system 8

4. Project Implementation 3

5. Project Timeline 13

6. Conclusion 15

7. Limitations 16
 1. Executive Summary

The project focuses on developing a University Management System (UMS) to help

universities manage their operations more efficiently. The UMS will streamline processes
such as student enrollment, course management, and administrative tasks. By utilizing
advanced technology, the system aims to improve overall efficiency, enhance student
experience, and ensure better compliance with regulatory requirements. Through this project,
we aim to provide universities with a comprehensive and user-friendly solution to meet their
management needs effectively.

University Management System

2
 2. Motivation, Vision, Missions

2.1. Motivation

In Myanmar, schools are working harder to get students because education is

becoming more important. This makes it tough for universities to keep their students. Parents
also find it hard to choose the right university for their child. So, our team made something
called UMS (University Management System) to help. UMS makes it easy for universities to
talk to parents and share information about students.

2.2. Vision

Transforming education through seamless efficiency.

2.3. Missions

 To Enhance Educational Excellence: Ensuring universities provide top-tier

education.
 To Attract and Retain Students: Bringing in new students and ensuring their
satisfaction.
 To Enhance University Experience: Improving operational efficiency and user
experience.
 To Maximize UMS Utility: Ensuring widespread adoption and recognition of UMS
benefits.

3
 3. Project Summary

The University Management System (UMS) makes university life easier for
administrators, faculty, students, and staff. It helps manage tasks like admissions, course
scheduling, and student records. With the UMS, users can communicate, access resources,
and make decisions more efficiently, ultimately improving the overall university experience.

3.1 Target User

 Administrators: University administrators, such as deans, who oversee the overall

operation of the institution.
 Faculty and Instructors: Professors, lecturers, and teaching assistants who manage
courses, and assess student performance.
 Students: University students who use the system to register for courses, access
course, submit assignments, and view grades.
 Parents/Guardians: Parents or guardians of students who want to stay informed
about their child's academic progress, attendance, and university activities.
 Admissions Office: Staff responsible for managing admissions processes, including
processing applications, admitting students, and issuing student IDs.
 Financial Aid Office: People who help students with money for school, like
scholarships.
 Human Resources: HR staff who manage employee records, payroll for university
staff and faculty.
 Library Staff: Librarians and library assistants who manage the university's library
resources.

4
 3.2 ER Diagram

Fig(3.2.1) ER Diagram ( Financial Officer )

Fig(3.2.2) ER Diagram (Academic Officer)

5
Fig(3.2.3) ER Diagram ( Teacher )

Fig(3.2.4) ER Diagram ( Librarian)

3.3 System Flow Diagram

6
7
 Fig(3.3.1) System Flow Diagram

3.4 Advantages of the system

 Easy Access to Information: Students, faculty, and staff can quickly find important
information like schedules and grades.
 Better Communication: Everyone can easily talk to each other, helping teamwork
and understanding.
 Less Paperwork: The system handles tasks like admissions and registration, saving
time and reducing paperwork.
 Helps Students Learn: Students can access courses and talk to teachers easily,
making learning easier.
 Keeps Information Safe: It keeps personal information secure and stops
unauthorized people from accessing it.
 Helps Plan Resources: It helps universities know how many students are in classes
and how much staff they need.
 Keeps Parents Informed: Parents can see how their child is doing in university and
get updates about what's happening on campus.

8
 4. Project implementation
The website will be made using a tool called Codeigniter PHP framework with the help of
visual studio code editor and XAMPP. The mobile app will be created using Java with the
help of Android Studio.

Dashboard View: Admin

In the picture (Figure 4.1, 4.2, 4.3), you can see what the admin's dashboard and front page
on the website looks like. The admin can see all the students' information and do things like.

9
Fig (4.1) Front End Website
View

10
Fig (4.3) Login Page

11
Fig (4.5) Admin Panel View (II)

12
 Fig (4.6) Android Application View

Figure 4.6: Using the App

When users open the app, they have to log in with their username and password first. Then,
they can see their homework, attendance, timetable, announcements, and more.

 Homework: Teachers give assignments to students.

 Announcement: Teachers and schools share important messages.
 Quiz: Teachers make quizzes for students to answer in the app.
 To-Do List: Students can plan activities.
 Attendance: Teachers can send attendance reports to parents.
 Calendar: Students and parents can see important dates easily.
 Timetable: Students can check schedules.

13
  Chat: Users can also chat with each other.
 This makes it easy for students and parents to stay updated on school activities
and communicate with teachers.

5. Project Timeline

Info Task Name Duration Planned Planned Assigned

Start Date Finished
Date
1 Feasibility Study 10 Days 12/10/202 12/20/2023 Htet Zayar
3 Win,
Kyaw
Naing
2 Requirement 14 Days 12/17/202 12/31/2023 A Jay
Gathering 3 Kumar,
Naing Ye
Htut
3 Requirement 14 Days
Gantt Chart
1/1/2024 1/15/2024 Htet Zayar
Analysis 15-Dec 25-Dec 4-Jan 14-Jan 24-Jan 3-Feb Win,13-Feb
Kyaw23-Feb 4-Mar
Naing, ACoding Project
Feasibility Require- Require- Require- Database
Feasibility Study Study ment ment ment Val- Design and Unit
Jay Kumar, Imple-
Gathering Analysis idation Testing mentation
Naing Ye
Requirement Gathering Htut
4 Requirement Start 45270
10 Days 45277 45292 45306 45316
1/15/2024 1/25/2024 Htet Zayar 45328 45349
Date
Requirement Analysis
Validation Win, A Jay
Day 10 14 14 10 10
Kumar, 20 7
to
Requirement Validation
Com- Kyaw
plete Naing
Database Design
5 Database Design 10 Days 1/25/2024 1/5/2024 Naing Ye
Coding and Unit Testing Htut, Kyaw
Naing, A
Project Implementation Jay Kumar

6 Coding and Unit 20 Days 2/6/2024 2/26/2024 Htet Zayar

Testing Win, Kyaw
Naing, A
Jay Kumar,
Naing Ye
Htut
7 Project 7 Days 2/27/2024 3/5/2024 Htet Zayar
Implementation Win, Kyaw
Naing

14
 Htet Zeyar Win Kyaw Naing
UCSTGO- UCSTGO-3317

Fig (5.1) Gantt Chart

Naing Ye` Htut Ajay Kumar

UCSTGO-3083 UCSTGO-3326

6.Conclusions

We created a school management system that helps with various school activities. There are
two parts to our system: a Windows application and a web application. The Windows app
handles tasks like registering students offline, generating transcripts and report cards, and
creating timetables. The web app lets homeroom teachers record attendance and allows
students, teachers, and parents to view reports and student status.

For our timetable solution, we kept it simple. We use data structures to organize the
timetable. The scheduler looks at the subjects and teachers in the database. It figures out how
many classes each teacher has and makes sure they don't have too many. Then, it randomly
picks a day based on the number of lessons for that subject, finds a free time slot, and assigns
the lesson to that slot. It keeps doing this until all the teachers have their schedules filled.
Finally, it saves the timetable in the database.

7. Limitations

15
 Browser Issues: Some features might not work well on different web browsers like
Chrome, Firefox, or Safari. People using different browsers may have trouble using
the system smoothly.

 Needing Internet: You have to be connected to the internet to use the web
application. If the internet is slow or not available, it will be hard to use the system.

 Not Great on Phones: While the web app can work on phones, it might not look
good or be easy to use on small screens. People using smartphones might find it hard
to use the system comfortably.

 No Mobile Apps: There aren't special apps for phones like iPhone or Android. This
means people who prefer using apps or need to work offline won't have that option.

 Uses a Lot of Data: If you use the web app on your phone, it can eat up a lot of your
data. This might be a problem for people with limited or expensive data plans.

 Different Experiences on Different Devices: The way the system looks and works
might change depending on whether you're using a computer, tablet, or phone.
Switching between devices might confuse people because things look different each
time.

 To handle these issues, you could work on making the web app better for phones,
maybe creating apps for Android, and making sure it works well even when the
internet is slow.

16