FUNCTIONAL REQUIREMENTS

High school student profiles and scores management

project

GROUP 3
9/4/2024
Content

s
1.0 INTRODUCTION.............................................................................................................1
1.1 Purpose.....................................................................................................................................................................1
2.0 business requirements overview.......................................................................................1

3.0 functional requirements and user impacts......................................................................1

3.1 Usability Requirements............................................................................................................................................1
3.2 Performance Requirements......................................................................................................................................2
3.3 Supportability Requirements....................................................................................................................................2
3.4 Security Requirements.............................................................................................................................................2
3.5 Interface Requirements.............................................................................................................................................2
3.6 Assumptions / Constraints........................................................................................................................................3
1.0 INTRODUCTION
1.1 Purpose

The purpose of the high school student records and grades management system is to collect, manage, and provide information about
students and their academic performance. This system will support the management of students' personal records, record and organize
various types of grades from assessment activities during the learning process, and provide comprehensive reports on the academic
performance of each student and class.

2.0 BUSINESS REQUIREMENTS OVERVIEW

-The system needs to be able to input personal information of students from the personal information form.

-It must support the recording of various types of grades (Oral, 15-minute, 1-hour) and the overall semester grade of students from the
grade sheet.

-It needs to have the function to automatically calculate the end-of-semester grade average.

-The system needs to provide functionality for homeroom teachers and the Principal's Office to input and review comments,
assessments of students, including academic results and learning attitudes.

-It should provide comprehensive reports on the academic performance of each student and class for the Principal's Office.

2.1 Assumptions and Constraints

-It is assumed that each student will provide accurate and complete personal information upon enrollment, and this information will be
securely stored and protected in the system.

-It is assumed that the grade input process will be performed by teachers each semester, and these grades will be accurately recorded
and not tampered with unlawfully.

-Security constraint: The system must ensure that students' personal information is securely protected and only users with appropriate
access rights can view this information.

-Availability and performance constraint: The system needs to be able to efficiently process large amounts of student data and grades
while ensuring quick access for users.

3.0 FUNCTIONAL REQUIREMENTS AND USER IMPACTS

3.1 Usability Requirements

-Ease of Learning: The system should be intuitive and easy to navigate, allowing users (administrators, teachers, and staff) to quickly
understand its functionalities without extensive training.

-Task Efficiency: Users should be able to efficiently manage student profiles, input grades, generate reports, and perform other tasks
related to student records and academic performance.
-Ease of Use: The interface should be user-friendly, with clear instructions and minimal complexity, ensuring smooth interaction for
all users regardless of their technical proficiency.

1
-Appearance: The system should have a clean and professional design, with organized layouts and visually appealing elements,
enhancing user experience and engagement.

3.2 Performance Requirements

-Reliability: The system should operate reliably without frequent crashes or errors, ensuring continuous availability for users to access
student information and perform necessary tasks.

-Speed: The system should have fast response times, allowing users to input data, retrieve information, and generate reports promptly,
enhancing productivity and efficiency.

-Safety: Data integrity and security measures should be in place to protect sensitive student information from unauthorized access,
ensuring compliance with privacy regulations.

-Precision: The system should accurately calculate and display student grades, ensuring precision in academic records and
performance evaluation.

-Scalability: The system should be able to handle a growing number of student records and user accounts without significant
performance degradation, accommodating the expanding needs of the school over time.

3.3 Supportability Requirements

-Training: Comprehensive training should be provided to users on how to effectively use the system, covering its features,
functionalities, and best practices for data management.

-Documentation: Clear and thorough documentation should be available, including user manuals, FAQs, and tutorials, to assist users
in troubleshooting issues and maximizing the system's capabilities.

-Staff: Adequate technical support staff should be available to assist users with any system-related queries or problems, ensuring
timely resolution of issues.

-Equipment and Facilities: The system should be compatible with standard hardware and software configurations commonly used in
educational institutions, minimizing the need for additional investments in infrastructure.

3.4 Security Requirements

-User ID and Authentication: The system should enforce strong user authentication mechanisms, such as usernames and passwords,
to prevent unauthorized access to student records and sensitive data.

-Privacy: Student information should be encrypted and stored securely, with access restricted to authorized personnel only, to
maintain confidentiality and comply with data protection regulations.

-Security Audits: Regular security audits should be conducted to identify and address any vulnerabilities or risks in the system,
ensuring continuous protection against potential security threats.

3.5 Interface Requirements

-Navigation: The interface should have intuitive navigation menus and pathways, allowing users to easily move between different
sections and functionalities within the system.

-Functionality: All essential features and functionalities, such as student profile management, grade input, and report generation,
should be easily accessible and logically organized within the interface.

-Location of Interface Elements: Important interface elements, such as buttons, forms, and menus, should be placed strategically for
optimal usability and visibility, reducing user effort in locating them.

2
-Display: The interface should have a responsive design that adapts to various screen sizes and devices, ensuring consistent user
experience across desktop computers, tablets, and mobile phones.

3.6 Assumptions / Constraints

-Functional Requirements: It is assumed that the system will meet all functional requirements outlined in the provided description,
including student profile management, grade tracking, and report generation.

-User Impacts: Constraints may include limited budget and resources for system development and maintenance, as well as potential
resistance to change from users accustomed to traditional paper-based record-keeping methods. Additionally, the system's usability
may be impacted by factors such as network connectivity and hardware compatibility.