student score management software cmu se 100 wis course final project

Manage student information- The system will allow management of student information, including student number, name, date of birth, address, phone number, email and related information.-

ĐẠI HỌC DUY TÂN TRƯỜNG ĐÀO TẠO QUỐC TẾ

STUDENT SCORE MANAGEMENT SOFTWARE CMU – SE 100 WIS COURSE FINAL PROJECT

INSTRUCTOR: TRAN VAN DAI

SUBJECT: INTRODUCTION TO SOFTWARE ENGINEERING CLASS: CMU-TPM12

GROUP MEMBERS:

1 TRAN NGOC PHUC HUY - 29219021011

2 VO THI THAI NGOC - 29209024817

3 NGUYEN THAI HOANG HIEU - 29219030682

4 HUYNH PHAM LONG VI - 29219037425

5 NGUYEN NGOC YEN NHI - 29201144338

Table of contents

I Software Requirement Specification 3

1 Introduce 3

1.1 Purpose 3

1.2 Uses 3

1.3 Limit 3

2 General description n 3

3 Require function 3

3.1 Manage student information 3

3.2 Manage subject information 3

3.3 Classroom management 3

3.4 Faculty management 3

3.5 Score management 3

3.6 Enter and process scores 4

3.7 Checkpoint 4

3.8 Edit points 4

3.9 Print transcript 4

3.10 Create statistical reports 4

3.11 Create user account management 4

4 Non-functional requirements 4

4.1 Role-based authorization 4

4.2 Manage access rights 4

4.3 Information security 4

4.4 Keep an activity log 5

4.5 Manage user accounts and user interfaces 5

5 Requirements for integration, multi-language, multi-format 5

5.1 About integration 5

5.2 About multi-language and multi-format 5

6 Technical requirements 5

6.1 Technology 5

6.2 Efficiency 5

7 Y requires software 5

8 System requirements 5

9 Request data 5

10 Requires user interface 6

11 Requires maintenance and support 6

II Usecase Use Modeling 7

1 Use Case Diagram 7

2 Use Case Specification 8

2.1 Class manager 8

2.2 Point management 10

2.3 Statistic 13

2.4 Manage student information 14

2.5 Manage study records 16

2.6 Subject information management 17

2.7 Faculty management 20

2.8 Manage user accounts 22

III FunctionDiagram and Context Diagram 23

1 Function Diagram 23

2 Context Diagram 24

IV Class Diagram 25

1 Class Diagram 25

I Software Requirement Specification

1 Introduce

1.1 Purpose

-The purpose of this SRS (Software Requirements Specification) is to definefunctional and non-functional requirements for the student grade management system within the department The system helps manage and organize student score information

1.2 Uses

-The system will help improve the management process and create favorableconditions for monitoring and evaluating student learning outcomes.1.3 Limit

- Applicable to student score management system within CMU faculty The system will include functions and features to manage student score information, including entering scores, viewing scores, editing scores and printing transcripts

2 General description n

-The student score management system will include basic functions such as managing student information, entering scores, processing scores, creating score reports and providing an intuitive interface for users

3 Require function

3.1 Manage student information

- The system will allow management of student information, including student number, name, date of birth, address, phone number, email and related information

- The system will allow management of tuition information and registered courses

- Edit student information when necessary

- The system will provide the function of creating, modifying and deleting student information from the system when no longer needed

3.2 Manage subject information

- The system allows management and storage of information about subjects including subject code, subject name, number of credits and other information.3.3 Classroom management

- The system allows storage management to create new information about classes including class code, class name, lecturer, time, location, number of students and other information

- Edit class information when necessary

- Delete classes from the system when no longer needed

3.4 Faculty management

- The system allows management to store information about departments including department code, department name, department head and other information

3.5 Score management

- The system allows storage management to record information about students' scores in subjects including student code, subject code, test scores, attendance scores, homework scores and other information.

3.6 Enter and process scores

- The system will allow teachers to enter test scores, attendance scores, homework scores and other columns for students according to each subject

- The system will process scores and calculate the student's average score according to department regulations

- The system will check the validity of the input points and warn if there are data entry errors

- The system will provide the function of printing transcripts for each class

- The transcript will be printed in a standard format and contain full informationabout the student's scores

3.10 Create statistical reports

- Create reports on student lists, class lists, transcripts, etc

- Statistics on number of students, number of classes, average score, etc3.11 Create user account management

- Create and manage user accounts for teachers, administrators and students

- Assign access rights based on user roles

4 Non-functional requirements

4.1 Role-based authorization

- The system needs to support the definition of different roles such as teachers, administrators, students, etc

- The system will have an authentication and authorization mechanism for users

- The system should ensure that students' personal information and other transparent data are only accessed and edited by users with corresponding access rights

- Especially student score information and student personal information, the system will store information safely and securely

4.4 Keep an activity log

- The system needs to provide user account management functions, including creating, deleting, locking, and unlocking accounts depending on the needs and control of the administrator

4.5 Manage user accounts and user interfaces

- The user interface will be designed to be simple and easy to use

5 Requirements for integration, multi-language, multi-format

5.1 About integration

- Ability to integrate other systems such as learning management systems, financial systems, etc

5.2 About multi-language and multi-format

- The software needs to support many different languages and formats to suit users in many different countries and territories

- The system will store student information, subject information and score information, student tuition information and other related information.

- Data will be stored in a relational database and backed up periodically

10 Requires user interface

- The system needs to provide a friendly, easy-to-use user interface to manage student information and scores

11 Requires maintenance and support

- The system will be periodically maintained and supported to ensure stable andeffective operation

- The system will have user manuals and technical support for users

12 Request testing

- There needs to be a clear test plan to ensure the stability and reliability of the system

II Usecase Use Modeling

1 Use Case Diagram

Input and process scores

Add and infor

Dele

Subject information management

Dele

Add anin

Department management

Delete

2 Use Case Specification

2.1 Class manager

Use case name: Add and edit class information Actor: Teacher

Description: The system allows instructors to add and edit class information

Case in point: The instructor receives a request to add or edit class information

Steps to edit or add information:

1 Instructor logs into the system

2.Choose to edit or add class information

3.Select the layer to edit or add

4.Select the item to edit or add information

5.Update information

Step-by-step information:

1 Instructor ID, password.2

3 Class name, Class code

4 Edit or add class information

5.Confirmation

Enter: Information that needs to be corrected or added

Export: Update edited or added information

Prerequisite: There is a request to correct or add class information

Post-condition: Correct correction or add information

Assumption: There is a valid request to correct or add class information

Outstanding issue: Updating class information

1

Use case name: Delete class Actor: Teacher.

Description: The system allows instructors to delete classes

Scenario: The instructor receives a request to delete the class

Steps to delete a class:

1 Instructor logs into the system

2.Select the class to delete

3.Choose to delete class

4.Update information

Step-by-step information:

1 Instructor ID, password

2 Class name, Class code

3 Delete class.4.Confirmation

Enter: Information to delete

Export: Update new information

Prerequisite: There is a request to delete the class

Post-condition: Exact deletion of the requested class

Assumption: There is a valid request to delete the class

Outstanding issue: Updating class information

2.2 Point management

Use case name: Enter points Actor: Teacher

Description: System for lecturers to enter student scores

What happens: After the instructor gets the points

Implementation step

1 Instructor logs in

2.Select point entry

3.Select the section class

Enter: Student's score

Export: Update student scores

Prerequisite: Instructor has student points

Following conditions: Instructor logs in with personal account

Assumption: After the instructor grades

Outstanding issue: Update new scores for students

Use case name: Edit points Actor: Teacher

Description: The system allows administrators to edit student scores after logging in

In case: The administrator receives a request to correct the score

Implementation step

1 Instructor logs in

2 Select the item to edit points

3.Select the section class

4.Search for students

Enter: Information to be corrected

Export: Update edited information

Prerequisite: Grade correction required

Post-condition: Correct incorrect student scores

Assumption: There is a valid request to correct the student's score

Outstanding issue: Update new scores for students

Use case name: View points Actor: Student

Description: The system allows students to see their scores after logging in to the correct student account

Case in point: the student logs into the system and selects the item to view scores

Implementation step

1.Students log in to the school website

2.Select score view item

3 View overall or detailed scores

Step-by-step information

1 Student ID, password

Enter: Student's personal account

Export : Student's personal transcript

Prerequisites : Students are online on the school's website

Following conditions: Students log in to the correct personal account

Assumption: Students can access the website and have a valid account

Outstanding issue: Providing grades to students

2.3 Statistic

Use case name: Statistical report Actors: Teacher, Student,

Admin

Description: Displays student information, subjects, departments, transcripts

What happens: When creating a request to view statistics

Implementation step

1.Login agent

2.Select statistical report item

3.View statistical reports

4.Search for students

Enter: Personal account

Export: Statistical report

Prerequisite: Agent is online on the school's website

Post-condition: The agent logs in with a personal account

Assumption: After the end of the semester

Featured issue: Show full score report and essential information

2.4 Manage student information

Use case name: Add and edit student

information

Actors: Admin, teacher and student

Description: Allows adding and editing a student's information in the system

In case: Admin, lecturer and student log in to the system and select the option to add and edit student information

Implementation step

1.Admin, lecturers, and students log in to

the school website

2.Choose to add and edit student

Enter: Personal information to add and edit

Export : Personal information added and edited

Prerequisites : There is a request to add and edit information

Following conditions: Add and edit student information accurately when there are errors

Assumptions: There is a valid request to add and edit student information

Outstanding issue: Update new information for students

Use case name: Delete student Actor: Admin

Description: Allows deleting a student in the system

In case: Admin logs into the system and selects the delete student option

Implementation step

1.Admin logs in to the school website

2.Choose to delete student

3 Delete a student in the system

Step-by-step information

1 Admin ID, Password

2

3

Enter: Select the student to delete

Export : Notification confirming successful deletion and updating the student list display interface

Prerequisite : There is a request to delete the student

Post-condition: Remove student from the list

Assumptions: There is a valid request to delete the student

Outstanding issue: Update new information for student list

2.5 Manage study records

Use case name: Manage learning records Actor: Admin

Description: Displays student information, subjects, departments, transcripts

What happens: When creating a request to view statistics

Implementation step

1.Login agent

2.Select statistical report item

3.View statistical reports

4.Search for students

Enter: Personal account

Export: Statistical report

Prerequisite: Agent is online on the school's website

Post-condition: The agent logs in with a personal account

Assumption: After the end of the semester

Featured issue: Show full score report and essential information

2.6 Subject information management

Use case name: Add Subject information Actor: Admin

Description: Admin adds subject information

Case in point: After adding a new subject

Implementation step

1 Admin log in

2 Select the item to add Subject information

3.Select the section class

Enter: Admin information

Export: Update admin information

Prerequisite: Admin has Subject information for Teacher

Following conditions: When Admin logs into his account

Assumption: After adding new subjects

Outstanding issue: Update new Subject information for Teachers

Use case name: Edit Course information Actor: Admin

Description: The system allows Admin to edit Subject information

In case: Admin receives a request to edit Subject information

Implementation step

1 Admin log in

2 Select the item to edit Subject information

3.Select the section class

4.Search for admin

5 Edit Subject information

6.Update corrected information

Enter: Information to be corrected

Export: Update edited information

Prerequisite: There is a request to edit Course information

Following conditions: correct Subject information when there are errors

Assumption: there is a valid request to edit Subject information

Outstanding issue: updating new information for admin

Use case name: Delete Subject information Actor: Admin

Description: The system tells Admin to delete Subject information

In case: Admin receives a request to delete Subject information

Implementation step

1 Admin log in

2 Select the item to edit Subject information

3.Select the section class

4.Search for Admin

5 Delete Subject information

6.Update deleted information

6.Confirmation

Enter: Information to delete

Export: Update deleted information

Prerequisite: There is a request to delete Subject information

Following conditions: Delete correct Subject information when there is an error

Assumption: There is a valid request to delete Subject information

Outstanding issue: Update new information for admin