Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

School Information Management System Design for FPT University, Study Guides, Projects, Research of Design

The design of a relational database system for a school information management system (sims) aimed at fpt university. The system includes four interrelated tables for student, teacher, course, and exam management, with features for user registration, course enrollment, schedule management, and data updates. The system also integrates with other college systems and implements security measures to protect user data.

Typology: Study Guides, Projects, Research

2021/2022

Uploaded on 03/28/2024

shoyo-mizuki
shoyo-mizuki 🇻🇳

2 documents

1 / 27

Toggle sidebar

Related documents


Partial preview of the text

Download School Information Management System Design for FPT University and more Study Guides, Projects, Research Design in PDF only on Docsity! ASSIGNMENT 1 FRONT SHEET Qualification TEC Level 5 HND Diploma in Computing Unit number and title Unit 04: Database Design & Development Submission date 24/2/2024 Date Received 1st submission 24/2/2024 Re-submission Date 02/03/2024 Date Received 2nd submission 02/03/2024 Student Name Bui Huy Hoang Student ID BH01098 Class SE06304 Assessor name Nguyen Van Toan Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that making a false declaration is a form of malpractice. Student’s signature Hoang Grading grid P1 M1 D1 ❒ Summative Feedback: ❒ Resubmission Feedback: Grade: Assessor Signature: Date: Signature & Date: employing established design principles, such as entity-relationship modeling and normalization, the database will be structured to optimize performance, maintain data integrity, and support future scalability. 3. Interface and Output Designs: The design process also encompasses the creation of intuitive and user-friendly interfaces for the User Management System. This section will explore the visual and interactive components of the system, ensuring that users can easily navigate through different functionalities and perform tasks efficiently. Additionally, output designs will be crafted to present statistical reports in a clear and concise manner, providing valuable insights to FPT University managers. 4. Data Validations and Normalization: To ensure data accuracy and consistency, the design will incorporate robust data validation mechanisms. These validations will enforce data integrity rules, perform input sanitization, and validate user inputs against predefined criteria. Furthermore, data normalization techniques will be applied to eliminate redundancy and ensure efficient storage and retrieval of information. 5. Assessment of Design Effectiveness: In line with managerial expectations, this document will provide an assessment of the design's effectiveness in relation to user and system requirements. The report will evaluate how well the proposed design aligns with the stated objectives, addresses potential challenges, and offers solutions to enhance the overall functionality and usability of the User Management System. II. Body P1 Design a relational database system using appropriate design tools and techniques, containing at least four interrelated tables, with clear statements of user and system requirements. 1. Identify the system School Information Management System - SIMS. This system helps manage school activities, including: Student management: personal information, studies, class schedule, study results, etc. Teacher management: personal information, teaching schedule, attendance, etc. Classroom management: timetable, student list, etc. Manage exam schedule: exam schedule, exam room, proctor, etc. Manage test scores: enter scores, calculate results, etc. Financial management: tuition collection, payments, etc. Detailed analysis of the ingredients Based on the diagram, the system includes the following main components: 1.1. Data : Students: store personal information, studies, class schedules, study results, etc. student's. Teachers: store personal information, teaching schedules, attendance, etc. of teachers. Classroom: stores timetables, student lists, etc. of the classroom. Exam schedule: stores exam schedules, exam rooms, proctors, etc. Test scores: store test scores, calculate results, etc. Finance: stores information on tuition collection, payments, etc. 1.2. Processing : Data entry: import data into the system from different sources. Update data: update data when there are changes. Data processing: performing calculations, statistics, etc. on data. Export data: export data to reports, charts, etc. 1.3. User interface:  Schedule Creation: The system should provide tools for students to create their schedules based on the courses they need to take. It should allow students to select courses, specify preferred time slots, and handle any scheduling conflicts that may arise.  Course Enrollment: The system should allow students to enroll in the courses they have selected for their schedules. It should also enforce any prerequisites or restrictions for specific courses.  Faculty Availability: The system should allow faculty members to indicate their availability for teaching specific courses. This information can be used during the schedule creation process to ensure that courses are assigned to available faculty members.  Room Scheduling: The system should have the capability to manage and schedule classrooms or other facilities for conducting classes. It should consider factors such as room capacity, availability, and any specific requirements for certain courses.  Schedule Viewing: The system should provide an interface for students, faculty, and staff to view their schedules. It should display the courses, meeting times, locations, and any other relevant information.  Notifications and Reminders: The system should have the ability to send notifications and reminders to users regarding important dates, such as course registration deadlines, class cancellations, or changes to the schedule.  Reporting and Analytics: The system should generate reports and provide analytics related to course enrollment, schedule conflicts, room utilization, and other relevant data. This information can be useful for administrators in making informed decisions and optimizing the scheduling process.  Integration with Other Systems: The system should integrate with other college systems, such as the student information system or learning management system, to ensure data consistency and streamline processes like course updates or grade synchronization.  Accessibility: The system should be designed with accessibility in mind, ensuring that users with disabilities can effectively use the system. This may include features such as screen reader compatibility, keyboard navigation, and adequate color contrast.  Security: The system should implement appropriate security measures to protect user data and prevent unauthorized access. This may involve encryption of sensitive information, secure authentication protocols, and regular system audits. - The system should have strong user verification mechanisms to ensure that users such as students and teachers are identified and given access appropriate to their position in the system, including positions such as student, teacher, or administrator. Course management: Managers need to be able to perform a variety of tasks related to course management, including creating, editing, and deleting course information. This information may include important elements such as course title, description, teacher assignments, subject affiliation, and prerequisites. Class schedule management: Management staff should have the function of arranging class schedules for each semester. This includes the ability to allocate specific courses to time slots and classrooms, as well as mechanisms to resolve class schedule conflicts when they occur. Enrollment management: The system needs to support a smooth enrollment process for students, giving them the ability to explore available courses, access detailed information about each course, and enroll when needed . Meanwhile, administrators need tools to monitor course enrollment, including the ability to add or remove students from courses as needed. Teacher management: Managers need to have functions to manage information related to teachers in a comprehensive way. This includes tasks such as assigning teachers to specific courses, updating teacher profiles with relevant information, and tracking teaching assignments to ensure effective use of teacher resources. . Classroom management: Management staff need tools to effectively manage classroom resources in the facility. This includes tasks such as allocating appropriate classrooms to courses, monitoring classroom status, and facilitating room reservations for academic activities. Can communicate with students and colleagues through messaging systems or forums. Management: Can manage information of students, teachers, and staff including adding, editing, and deleting information. Ability to manage finances, including tuition collection, payment of expenses, and financial reporting. Can manage facilities, including classrooms, function rooms, teaching equipment, etc. Security can be managed, including access control and security monitoring. You can view statistical reports on learning, teaching, finance, etc. Parents: Can view your child's personal information, including name, date of birth, address, phone number, etc. You can view your child's class schedule, including time, location, and teacher name for each subject. You can view your child's test scores for each subject. You can pay your child's tuition online. You can contact your child's teacher through the messaging system or the forum. Staff: Can view their personal information, including name, date of birth, address, phone number, etc. Can view their work schedule. May perform assigned tasks such as data entry, library management, etc. Can communicate with colleagues via messaging system 4. Logical design Sal td SchedulelD Fenesicn tees Eerie} Tt BU aC See Perera ts Sees cne) aE ere] EES Tee Ter ay area jor-yor-Tat uta) 8) forte) Ot Craig forelTTET 10) Sue le erative) paella) Srl ur Figure 1: Lo; jolt fe) (oy) StudentiD fore) et1] 8) Bit lg StudentID The primary key ScheduleID in the Schedule table is used as a foreign key in the Course table. This ensures that each schedule is only relevant to a specific course. One-to-many relationship with the Classroom table: The primary key ScheduleID in the Schedule table is used as a foreign key in the Classroom table. This ensures that each class schedule only takes place in a specific classroom. Course table: One-to-many relationship with the Enrollment table: The primary key CourseID in the Course table is used as a foreign key in the Enrollment table. This ensures that each course can be enrolled by multiple students. Faculty table (Lecturers): One-to-many relationship with Course table: The primary key FacultyID in the Faculty table is used as a foreign key in the Course table. This ensures that each instructor can teach a variety of courses. 1.2. Many-to-many relationship: Enrollment table (Register): Many-to-many relationship with Course table: The Enrollment intermediate table is used to represent a many-to-many relationship between the Course table and the Student table. The Enrollment table has two foreign keys: CourseID and StudentID. This allows a student to register for many different courses and a course can be registered by many students. Student table: Many-to-many relationship with Enrollment table: Intermediate table `EnrollmentPhysical design 5. Physical design Semester ® SemesteriO Name StartDate EndDate Department @ DepartmentiD Name Figure 2: Physical Design ‘Schedule ® Scheduled CourselD) ClassroomID. SemesterID SartDateTime EndDateTime Course ® CourselD Title Description DepartmentID. FacultyID ClassroomiD Faculty @ FacultyiD Name Email Classroom ClassroomID Location Capacity Enrollment ¥ EnrollmentiD StudentID CourselD ® StudentiD Name Email SBTEC CREATE TABLE Student ( ‘StudentID INT PRIMARY KEY, Mame NVARCHAR (100) , Email NVARCHAR( 100) 100% + i Messages Comande completed succesefutiy, Compienion eine: 2026-02-26701;09:46.2927623407:00 Figure 7: Student table SICREATE TABLE Course ( CourseID INT PRIMARY KEY, Title NVARCHAR(100), Description NVARCHAR (MAX), DepartmentID INT, FacultyID INT, ClassroomID INT, -- Added ClassroomID column FOREIGN KEY (DepartmentID) REFERENCES Department (DepartmentID), FOREIGN KEY (FacultyID) REFERENCES Faculty (FacultyI0) , FOREIGN KEY (ClassroomID) REFERENCES Classroom(ClassroomID) -- Added foreign key constraint 0% i Messages Figure 8: Course table Figure 9: Enrollment table Figure 10 : Schedule table III. Conclusion This report analyzed the school management system diagram in detail, including data tables, relationships between tables, main functions of the system, and user roles. The school management system diagram described in the report represents a comprehensive and effective system for managing school activities. The system includes main functions such as information management, learning management, teaching management, financial management, etc. The system also supports a variety of user roles, including students, teachers, administrators, parents, and staff. IV. References Techniques to design the database. Microsoft Support. URL : https://support.microsoft.com/en-gb/office/database-design-basics-eb2159cf- 1e30-401a-8084-bd4f9c9ca1f5 ( Access for Microsoft 365 Access 2021 Access 2019 Access 2016 Access 2013 )
Docsity logo



Copyright © 2024 Ladybird Srl - Via Leonardo da Vinci 16, 10126, Torino, Italy - VAT 10816460017 - All rights reserved