3. UML Diagrams - KavachInterns2020/Schoolmanagement_docs GitHub Wiki
School Management
Actors :
- Admin/HOD
- Students
- Staff
- Parents
Functionality Of Admin :
- Add/Manage staff
- Add/Manage students
- Add/Manage course
- Add/Manage subject
- Manage notification
- Manage leave status staff and students
- Manage timetable and Exams
- View Attendance
- Library, Transport
- View/Manage Feedback
- View results
Functionality Of Staff:
- Notifications for important events
- Apply for leave
- Take Attendance
- View Attendance
- Conduct quiz/contest
- Feedback
- View results
- Upload study materials
- Discussion forums
Functionality Of Students:
- Notifications for important events
- Apply for leave
- View Attendance
- Take part quiz/contest
- Feedback
- View results
- Contact teachers
- Discussion forums
- Library, Transport
Functionality Of Parents:
- Notifications for important events
- View Attendance
- Transport
- View results
- Contact teachers
Use Case Diagram :
The Use Case Diagram is a graphic depiction of the interactions among the elements of School Management System.
It represents the methodology used in system analysis to identify, clarify, and organize system requirements of School Management System. The main actors of School Management System are: Admin, Parents, Staff, Students, who perform the different type of use cases such as Manage Schools, Manage Students, Manage Classes, Manage Teachers, Manage Courses, Manage Registrations, Manage Users and Full School Management System Operations.
The relationships between and among the actors and the use cases of School Management System :
-
Admin Entity : Use cases of Admin are Manage Schools, Manage Students, Manage Classes, Manage Teachers, Manage Courses, Manage Registrations, Manage Staff and Full School Management System Operations.
-
Staff Entity : Use cases of Staff are Take Attendance, View status of the students, Conduct Exams/Quiz, Add Results, Upload study materials, Syllabus, access to discussion forums.
-
Student Entity : Use cases of Student are View Fees, Pay Fees, View Syllabus, View Timetable, Apply for leave, Transport and library system, access to discussion forums etc.
-
Parent Entity : Parents can keep track of their children even from remote places. They can view the status of their children, attendance and results. They also get notifications about the events and can contact teachers.
Flow Diagram :
School Management System Data flow diagram is used as a preliminary step to create an overview of the School.It consists of overall application data flow and processes of the School. It contains all of the userflow and their entities such all the flow of Students, Class, Teachers, Timetable, Fees, Attendance, Subjects.
High Level Entities and process flow of School Management System :
-
Managing all the Students
-
Managing all the Class
-
Managing all the Teachers
-
Managing all the Timetable
-
Managing all the Fees
-
Managing all the Attendance
-
Managing all the Subjects
Main entities and output :
-
Processing students records and generate report of all Students
-
Processing Class records and generate report
-
Processing Teachers/Students records and generate report of all Teachers/Students.
-
Processing Timetable records and generate report of Timetable
-
Processing Fees records and generate report of Fees
-
Processing Attendance records and generate report of Attendance
-
Processing Subjects records and generate report of all Subjects
Low level functionalities of School Management System :
-
Admin logins to the system and manage all the functionalities of School Management System
-
Admin can add, edit, delete and view the records of Students, Teachers, Fees, Subjects
-
Admin can manage all the details of Class, Timetable, Attendance
-
Admin can also generate reports of Students, Class, Teachers, Timetable, Fees, Attendance
-
Admin can search the details of Class, Fees, Attendance
-
Admin can apply different level of filters on report of Students, Timetable, Fees
-
Admin can tracks the detailed information of Class, Teachers, Timetable, Fees
Sequence diagram :
It which shows the interaction between the objects of Registration, Teacher, Course, Student, Classes. The instance of class objects involved in the Sequence Diagram of School Management System are as follows:
-
Registration Object
-
Teacher Object
-
Course Object
-
Student Object
-
Classes Object
Admin will be able to login in their account using their credentials. After login user can manage all the operations on Course, Registration, Teacher, Classes, Student. All the pages such as Teacher, Classes, Student are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a School Management System. The various objects in the Classes, Course, Registration, Teacher, and Student page—interact over the course of the sequence, and user will not be able to access this page without verifying their identity.
Students can login to their account and view all the assignments, study materials, attendance, results and time table. They can also update their information, apply leave, participate in contest/quiz, contact teachers. Access is provided to the discussion forums, library and transport system.
Staff can login to their account and upload the assignments, study materials, take and view attendance, status of students results and time table. They can also update their information, apply leave, conduct contest/quiz. Access is provided to the discussion forums so that they can help the students regarding the assignments.
Parents can login and monitor their children. They can view status/attendance of their children, results, contact teachers and information regarding transport facilities. They also get notifications about the events conducted at the school.
ER Diagram :
ER (Entity Relationship) Diagram represents the model of School Management System Entity. The entity-relationship diagram of School Management System shows all the visual instrument of database tables and the relations between Students, Teachers, Schools, Registrations, Parents etc. It used structure data and to define the relationships between structured data groups of School Management System functionalities. The main entities of the School Management System are Students, Classes, Staff, Parents, Courses and Registrations.
School Management System entities and their attributes :
-
Schools Entity : Attributes of Schools are school_id, school_name, school_type, school_description
-
Students Entity : Attributes of Students are student_id, student_college_id, student_name, student_mobile, student_email, student_username, student_password, student_address
-
Classes Entity : Attributes of Classes are class_id, class_student_id, class_name, class_room, class_type, class_description
-
Teachers Entity : Attributes of Teachers are teacher_id, teacher_college_id, teacher_name, teacher_mobile, teacher_email, teacher_username, teacher_password, teacher_address
-
Courses Entity : Attributes of Courses are course_id, course_student_id, course_registration, course_name, course_type, course_year, course_description
-
Registrations Entity : Attributes of Registrations are registration_id, registration_student_id, registration_course_id, registration_name, registration_type, registration_number, registration_date, registration_description
Description of School Management System Database :
The details of Schools is store into the Schools tables respective with all tables.Each entity ( Registrations, Classes, Courses, Students, Staff, Parents) contains primary key and unique keys. The entity Classes, Courses are bound with Staff and Student entities with foreign key. There is one-to-one and one-to-many relationships available between Courses, Staff, Registrations, Students. All the entities Schools, Courses, Classes, Registrations are normalized and duplicate records are reduced. We have implemented indexing on each tables of School Management System tables for fast query execution.