Use Cases

for
EDUNEXT
Version 1.0 approved

Prepared by Group 4

Fpt University

13,January 2025

Revision History

Name Date Reason For Changes Version

Group 4 15/01 Edit UseCase Template V2.0
Huyennthe 21/01 Add more information V2.1
DatLTHE176015 19/01 Add context diagram V2.2

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Use Cases for <edunext> Page 1

I.OverView

1. User Requirements

■ 1.1 Actors

# Actor Description
1 Admin This person is the user account and system settings manager.
The person who will create, manage courses and grade and evaluate
2 Teacher
students
3 Student This person will answer questions in each slot, different courses.
Use Cases for <edunext> Page 2

2. UseCase Diagram
■ 2.1 : Diagram

■ 2.2 : Descriptions

■ Relationships:
● <<include>> indicates that one use case is a mandatory part of another.
○ For example, "Sign In" includes "Sign In with Email."
● <<extend>> indicates optional or conditional functionality.
Use Cases for <edunext> Page 3

○ For example, "Course Management" extends to managing assessments and

grading.

II.Use Case Template

1.UC-001 : Sign In

UC ID and Name: UC -001 : Sign In .

Summary : This use case describes the process of users logging into the EduNext
system using their email and password.
Dependency: None
Primary Actor: Users Secondary
Actors:
Preconditions: PRE-1 : The user must have a valid account registered in the EduNext
system.
Description of main 1. The user selects the option to open the login screen.
sequence : 2. The system displays the login screen .
3. The user enters their email and password .
4. The system authenticates email, password.
5. Email and password verified successfully, logs into the system.

Description of alternative Step 4:If Authentication fails, the system displays an error
sequence : message:"Invalid data. Please re -enter email or password."The user
can re-enter the email and password.
Nonfunctional The system should validate login attempts within 2 seconds.
requirements :
Postcondition: POST-1: The user successfully logs into the system.

Outstanding questions: What measures are in place to handle repeated failed login attempts
(e.g., account lockout)?
Use Cases for <edunext> Page 4

2.UC-002 : Add Question

UC ID and Name: UC -002 : Add Questions

Summary : This use case describes the process of a teacher adding a question for
a specific course to a slot.
Dependency: None
Primary Actor: Teacher Secondary
Actors:
Preconditions: PRE-1: The teacher must be signed into the EduNext system.
PRE-2: The teacher must have access to the course where questions
are being added.
Description of main 1. The teacher opens the course management interface.
sequence : 2. The teacher selects a slot in the course.
3. The teacher enters the question details and submits the request.
4. The system confirms the question is valid and response saves
the question to the system.
5. The question is successfully displayed on the EduNext system.

Description of alternative 4.0 Invalid Question Data:

sequence : ● If the question data entered by the teacher is invalid (e.g.,
missing required fields, incorrect format), the system displays an
error message and prompts the teacher to correct the input and
resubmit the form.

Nonfunctional
requirements : ● The system should validate question submissions within 3
seconds.
Postcondition: POST-1: The question is successfully added to the slot. .

Outstanding questions: Does the system support uploading illustrations of questions?

Use Cases for <edunext> Page 5

3.UC-003 : Edit Question

UC ID and Name: UC-003: Edit Question

Summary : This use case describes the process by which a teacher edits an
existing question in a specific course or slot.
Dependency: None
Primary Actor: Teacher Secondary
Actors:
Preconditions: PRE-1: The teacher must be signed into the EduNext system.
PRE-2: The teacher must have access to the course where the
question is located.
Description of main 1. After successfully logging in, teachers navigate to the course
sequence : management interface.
2. The teacher chooses a specific course and the question to edit.
3. The teacher clicks the "Edit Question" button.
4. The system displays the current details of the question.
5. The teacher modifies the question details as needed.
6. The teacher presses the submit button.
7. The system saves the changes and notifies that the update was
successful.

Description of alternative 4.0 Invalid Question Data:

sequence : ● If the question data entered by the teacher is invalid (e.g.,
missing required fields, incorrect format), the system displays an
error message and prompts the teacher to correct the input and
resubmit the form.

Nonfunctional The system should ensure changes are reflected within 3 seconds of
requirements : submission.
Postcondition: POST-1: The question is successfully updated and visible with the
modified details.
Outstanding questions: Should the system maintain a version history of question edits?
Use Cases for <edunext> Page 6

4.UC-004 : Delete Question

UC ID and Name: UC-004: Delete Questions

Summary : This use case describes the process by which a teacher deletes an
existing question from a specific course or slot.
Dependency: None
Primary Actor: Teacher Secondary
Actors:
Preconditions: PRE-1: The teacher must be signed into the EduNext system.
PRE-2: The question to be deleted must exist in the course.
Description of main 1. After successfully logging in, teachers navigate to the course
sequence : management interface.
2. The teacher chooses a specific course and the question to
delete.
3. The teacher clicks the "Delete Question" button.
4. The system prompts the teacher to confirm the deletion.
5. The teacher confirms the deletion.
6. The system removes the question and confirms that the deletion
was successful.
Description of alternative 4.0 Cancellation:
sequence : ● If the teacher cancels the deletion process, the system does not
remove the question and returns to the previous screen.

Nonfunctional ● A confirmation dialog should be displayed to prevent accidental

requirements : deletions.
● The system should confirm deletion actions within 2 seconds.
Postcondition: POST-1: The question is successfully deleted and no longer visible in
the course.
Outstanding questions: Should deleted questions be recoverable (e.g., via a recycle bin)?
Use Cases for <edunext> Page 7

5.UC-005 : Generate Report

UC-005: Generate Report

UC ID and Name:

This use case allows teachers to export class information including

Summary: student list and student scores to an excel file.

Include Course Management use case

Dependency:

Actor: Teacher Secondar

y Actors:

PRE1: Teacher has logged into the system with the authority to manage
Preconditions: tests and grades.
PRE2: Tests have been pre-created in the system (or tests can be
added) and are linked to specific classes.
PRE3: A list of students has been imported into the system.

1, The teacher selects their class for the semester and accesses the
Description of main Generate Report feature.
sequence: 2, The system shows the list of tests and classes the teacher manages.
3, The teacher selects a test to manage.
4, The system displays a list of students and test statuses.
6, The teacher performs operations:
7, Enter scores and comments.
Edit scores if needed.
Save data.
8, The system saves the scores and logs the operation.

STEP2: The system detects that the class has no students associated
Description of with it. Displays the message: "The student list is empty. Please check
alternative sequences: again."

STEP 7: If valid, scores are updated; otherwise, an error message is

displayed.
Use Cases for <edunext> Page 8

The teacher enters an invalid score (e.g., it exceeds the 0-10 limit).
The system displays the error message: "Invalid score entry. Please
enter a value between 0 and 10."

1, Only authorized users should access the report generation feature.

Nonfunctional
requirements:

POST1: The requested report is successfully generated and made

Postcondition: available for download or viewing.
POST2: In case of a failure, the user is informed of the error, and no
incomplete or corrupted report is stored or provided

N/A.
Outstanding
questions:

6.UC-006: Manage Assessment and Grading

UC-006: Manage Assessment and Grading

UC ID and Name:

This use case allows teachers to create tests and manipulate student
Summary: scores.

Include Course Management use case.

Dependency:

Teacher
Actor: Secondar
y Actors:

Preconditions: PRE1: Teacher has logged into the system with the authority to manage
tests and grades.

PRE2: Tests have been pre-created in the system (or tests can be
added) and are linked to specific classes.

PRE3: A list of students has been imported into the system.

Description of main 1, The teacher selects their class for the semester.
sequence:
2, The teacher accesses the "Manage Assessment and Grading"
feature.
Use Cases for <edunext> Page 9

3, The system displays the teacher's managed tests and classes.

4, The teacher selects a specific test.

5, The system displays the student list and the student test status.
Teachers can export the student list and scores at this step.

6, The teacher manages grading by:

- Entering or updating scores.
- Adding comments (if needed).
7, The system saves the scores and logs the operation.

Description of STEP5: The system detects that the class has no students associated
alternative sequences: with it. Displays the message: "The student list is empty. Please check
again."

STEP6: The teacher enters an invalid score (e.g., it exceeds the 0-100
limit). The system displays the error message: "Invalid score entry.
Please enter a value between 0 and 10."

STEP7: Saving valid data, with errors shown if validation fails.

Nonfunctional 1, All grade modifications must be traceable, including the original and
requirements: updated values, along with the user making the changes.

2, Changes to grades should be logged with a timestamp and teacher ID

for auditing.

Postcondition: POST-1: The score and comments have been successfully saved to the
system.

POST-2: The system logs all score changes for tracking.

Outstanding questions: N/A

Use Cases for <edunext> Page 10

7.UC-007: Support contact

UC ID and Name: UC-007: Support contact

Summary: This use case allows the user to send a problem that needs support.

Dependency: N/A.

Actor: User (Student, Secondary

teacher). Actors:

PRE1: The system has pre-configured support contact information

Preconditions:
PRE2: User has a problem that needs support, such as:
Technical problem (cannot access, system error).
Questions related to scores, tests.
Support about personal information or account.

Description of main 1, The user logs into the system Edunext.

sequence:
2, Users access the Support Contact feature.

3, The system select Send request option,

4, User enters information (name, phone, problem description) and

submits a support contact.

5, The system records user support requests.

6, Admin receives request and processes request

7, Admin responds to received requests.

8, The system records responses to received requests.

9, System displays feedback from Admin to the user.

Description of N/A
alternative sequences:

Nonfunctional 1, All support interactions (e.g., tickets, chats) must be logged, including
Use Cases for <edunext> Page 11

requirements: timestamps and assigned agents, for future review.

Postcondition: POST1: The user's support request has been recorded.

POST2: The system sends a response to confirm receipt of the request.

POST3: Support staff receives and processes the request according to

the process.

N/A.
Outstanding questions:

8.UC-008: Import Student

UC-008: Import student
UC ID and Name:

This use case allows the user to import students.

Summary:

Include Create course use case

Dependency:

Teacher,
Actor: administrator Secondary
Actors:

PRE1: The user must be logged into the system.

Preconditions: PRE2: The user must have the necessary permissions to import student
data.
PRE3: The file to be uploaded must adhere to the predefined template
format.

Description of main 1, Navigate to the "Import Student" feature.

sequence:
2, Download the file template if necessary.

3, Prepare the file with student data in the specified format.

Use Cases for <edunext> Page 12

4, Upload the file through the import interface.

5, Displays errors or warnings if any issues are found in the file.

6, Processes the valid file, imports student data, and updates the
database.

7, Displays a confirmation message with the import summary.

Description of STEP4: The user uploads a file in an unsupported format. The system
alternative sequences: displays an error and requests the correct file format.

STEP5: The file contains invalid or incomplete data (e.g., missing

required fields, incorrect data types). The system lists errors and
specifies rows needing correction.

STEP6: The system processes valid rows and skips rows with errors.
The system provides a detailed report highlighting successful imports
and failed rows.

Nonfunctional 1, Support simultaneous uploads by at least 20 users without

requirements: degradation.

Postcondition: POST1: All valid student records are added or updated in the database.

POST2: The user is notified of the successful import, including a

summary of processed, successful, and failed records.

POST3: The system logs the import operation, including the user’s ID,
timestamp, and the number of records processed.

N/A.
Outstanding questions:

9.UC-009: Send Notification

Use Cases for <edunext> Page 13

UC-009 : Send Notification

UC ID and Name:

The system sends notifications to users based on predefined events,

Summary: such as course updates, assignment deadlines, or system
announcements.
None
Dependency:

Notification None
Actor: System Secondar
y Actors:

PRE-1: The user is registered in the system.

Preconditions: PRE-2: The notification content is prepared.

1.0 The system detects a triggering event.

Description of main 2.0 The system retrieves the list of relevant recipients.
sequence: 3.0 The system prepares the notification content using event details and
templates.
4.0 The system sends the notification via the specified channels (e.g.,
email, SMS, in-app notification).
None
Description of
alternative sequences:

1.0 Notifications must be sent within 2 minutes of the triggering event.

Nonfunctional 2.0 Notification channels must be secure and comply with data
requirements: protection regulations.
3.0 Notifications must be delivered in the preferred language of the
recipient.
The notification is delivered to all intended recipients.
Postcondition:

None
Outstanding questions:
Use Cases for <edunext> Page 14

10.UC-010: Manager User

UC-010: Manage User

UC ID and Name:

This use case enables the administrator to manage user accounts by

Summary: adding new users, editing existing user details, or deleting users from the
system.
None
Dependency:

Administrator None
Actor: Secondary Actors:

PRE1: The administrator is logged into the system with necessary

Preconditions: permissions.
PRE2: The system has access to the user database.

Description of main 1, The administrator selects the "Manage User" option from the main
sequence: menu.

2, The system displays options to add, edit, or delete a user.

3, The administrator chooses one of the following actions:

● Add User: The system collects required details and adds a new
user to the database.
● Edit User: The system retrieves existing user details, allows
modifications, and updates the database.
● Delete User: The system removes the user account after
confirmation.

4, The system confirms the operation and logs the changes for auditing
purposes.

Description of None
alternative sequences:

Nonfunctional 1, The user management interface should be responsive and load within
requirements: 2 seconds.

2, All operations must comply with data security standards, including

secure authentication and auditing.
Use Cases for <edunext> Page 15

3, Audit logs must be generated for every action performed by the

administrator.

Postcondition: POST1: The user account is successfully added, edited, or deleted.

POST2: All changes are logged for auditing purposes.

None
Outstanding questions:

11.UC-011: Add User

UC-011: Add User

UC-ID and Name:

This use case enables the administrator to add new user accounts by
Summary: entering required details such as name, email, and role into the
system.
Include Manage User
Dependency:

Administrator
Actor: Secondary Actors:

PRE1: The administrator is logged into the system with necessary

Preconditions: permissions.
PRE2: The system has access to the user database.

1, The administrator selects the "Create User" option.

Description of main
sequence: 2, Admin Interaction sends a request to UserManager to create a new
user.

3, UserManager forwards the request to UserServices to create the

user.

4, UserServices creates the user and returns the created user

information to UserManager.

5, UserManager sends a request to AccountService to create a new

Use Cases for <edunext> Page 16

account for the user.

6, AccountService creates the account and returns the new account

details to UserManager.

7, UserManager sends a confirmation email request to

EmailServices.

8, EmailServices processes the request and returns a confirmation

that the email was sent.

9, UserManager confirms that the user was successfully created and

returns this response to Admin Interaction.

10, The system displays a success message to the administrator.

Description of None
alternative
sequences:

Nonfunctional 1, The system should validate and create the user account within 5
requirements: seconds.

2, User account data must be securely stored and comply with data
protection standards.

3, The interface for adding users must be user-friendly and

accessible.

Postcondition: POST1: A new user account is successfully created and added to the
system.

None
Outstanding
questions:
Use Cases for <edunext> Page 17

12.UC-012: Edit User

UC-012: Edit User

UC ID and Name:

This use case enables the administrator to modify the details of an

Summary: existing user account, such as name, email, or role, in the system.

Include Manage User

Dependency:

Administrator None
Actor: Secondary Actors:

PRE1: The administrator is logged into the system with the necessary
Preconditions: permissions.
PRE2: The system has access to the user database.

1, The administrator selects the "Edit User" option from the menu.
Description of main
sequence: 2, The system displays a list of users or provides a search function to
locate the specific user.

3, The administrator selects the user account to be edited.

4, The system retrieves and displays the current details of the

selected user.

5, The administrator updates the desired fields (e.g., name, email,

role) and submits the changes.

6, The system validates the updated information (e.g., ensuring the

email is unique).

7, Upon successful validation, the system saves the changes.

8, The system displays a confirmation message to the administrator

and logs the update action for auditing purposes.

Description of None
alternative
sequences:

Nonfunctional 1, The system should validate and save the updated details within 5
seconds.
Use Cases for <edunext> Page 18

requirements: 2, User account modifications must comply with data security and
integrity policies.

3, Audit logs must record the original and updated values of edited
fields.

Postcondition: POST1: The updated user details are successfully saved in the
system.

POST2: The update action is logged for auditing purposes.

None
Outstanding
questions:

13.UC-013: Delete User

UC-013: Delete User

UC ID and Name:

This use case enables the administrator to permanently delete a user account
Summary: from the system while ensuring the action is logged for auditing and critical
system integrity is maintained.
Include Manage User
Dependency:

Administrator None
Actor: Secondary Actors:

PRE1: The administrator is logged into the system with the necessary
Preconditions: permissions.
PRE2: The system has access to the user database.
1, The administrator selects the "Delete User" option.
Description of main
sequence: 2, The system displays a list of users or provides a search function to locate
Use Cases for <edunext> Page 19

the specific user.

3, The administrator selects the user account to be deleted.

4, The system displays a confirmation dialog, including a warning about

potential impacts.

5, The administrator confirms the deletion.

6, The system checks if the user is associated with critical records and
requires reassignment of related data if necessary.

7, Upon successful validation, the system deletes the user account and logs
the action.

8, The system displays a confirmation message to the administrator.

Description of None
alternative sequences:

Nonfunctional 1, The system should validate and complete the deletion process within 5
requirements: seconds.

2, Audit logs must include details of the deleted user account and the
administrator performing the action.

3, The system must maintain referential integrity for any associated data.

Postcondition: POST1: The user account is successfully deleted from the system.

POST2: The deletion action is logged for auditing purposes.

None
Outstanding questions:

14.UC-014: Manage System Setting

UC-014: Manage System Setting

UC ID and Name:

This use case enables the administrator to manage system-wide

Summary: configurations, such as updating system preferences, managing global
Use Cases for <edunext> Page 20

application settings, and performing maintenance tasks to ensure smooth

system operation.
None
Dependency:

Administrator None
Actor: Secondary Actors:

PRE1: The administrator is logged into the system with the necessary
Preconditions: permissions.
PRE2: The system is operational and accessible.
1, The administrator selects the "System Settings" option from the admin
Description of main dashboard.
sequence:
2, The system displays the available configuration categories (e.g., user
roles, notifications, application preferences).

3, The administrator selects a category to modify and updates the desired

settings.

4, The administrator saves the changes.

5, The system validates the input values and applies the changes.

6, The system confirms the successful application of changes.

7, All changes are logged for auditing and troubleshooting purposes.

Description of None
alternative sequences:

Nonfunctional 1, Changes should be applied and logged within 5 seconds.

requirements:
2, The system must provide intuitive and user-friendly interfaces for
configuration tasks.

3, Real-time feedback should be provided during the configuration process.

Postcondition: POST1: System settings are updated successfully.

POST2: All configuration changes are logged for auditing and

troubleshooting purposes.

None
Outstanding questions:
Use Cases for <edunext> Page 21

15.UC-015: View Q&A

UC-012: View Q&A

UC ID and Name:

This use case enables students to access the Q&A section, view
Summary: previously asked questions and their answers, search for specific
topics, and optionally submit new questions if relevant information is
unavailable.
1, The system must have a functional Q&A section with pre-existing
Dependency: content.

2, The student must be logged in to submit a new question.

Student None
Actor: Secondary Actors:

PRE1: The student is on the Q&A page or section.

Preconditions: PRE2: The system has pre-existing Q&A content available.

1, The student navigates to the Q&A section on the website.

Description of main
sequence: 2, The system displays a list of questions and their corresponding
answers.

3, The student uses the search or filter function to locate specific

topics of interest.

4, The system updates the displayed content based on the search or

filter criteria.

5, The student selects and views a question and its answer.

Description of 1, If the user cannot find relevant questions or answers, the system
alternative provides an option to submit a new question.
sequences:
2, If no questions exist for a given topic, the system displays a
message encouraging users to ask their question.

Nonfunctional 1, The system must display search results or filtered content within 3
requirements: seconds.
Use Cases for <edunext> Page 22

2, The Q&A section interface should be intuitive and responsive for all
device types.

3 All displayed content must comply with moderation policies to

ensure quality and relevance.

Postcondition: POST1: The student successfully views the desired Q&A content.

POST2: The student may optionally submit a new question, provided

they are logged in.

None
Outstanding
questions:

16.UC-016: Answer the question

UC ID and Name: UC -0016 : Answer the question

Summary : This use case describes the process for a user to answer a question
within the EduNext platform.
Dependency: Include View Detail Question use case.
Primary Actor: Student Secondary Teacher
Actors:
Preconditions: PRE-1: The student is logged into the EduNext system.
PRE-2: The user guide is available within the EduNext platform.
Description of main 1. The student accesses the question .
sequence : 2. The Edunext displays the question details to the student.
3. The student reviews the question and any provided instructions.
4. The student enters their answer into the designated field.
5. The student submits their answer through the Edunext
application.
6. The QuestionService records the student's answer.
7. The Edunext application displays a confirmation message to the
student, indicating successful submission.
Description of alternative 1.0 Time limit exceeded
sequence : ● If the student attempts to submit an answer after the allotted
time has expired, the system rejects the submission.
Nonfunctional 1.0 The interface for answering questions should be intuitive and easy
requirements : to use.
Use Cases for <edunext> Page 23

Postcondition: POST-1: The student's answer is successfully submitted and recorded

within the EduNext system.
POST-2: The answer is available for the teacher to review and
evaluate.
Outstanding questions: How will the system handle plagiarism detection?

17.UC-017: View User Guide

UC ID and Name: UC -0017 : View User Guide

Summary : This use case describes the process for a student to access and view
the EduNext user guide.
Dependency: None
Primary Actor: Student Secondary
Actors:
Preconditions: PRE-1: The student is logged into the EduNext system.
PRE-2: The user guide is available within the EduNext platform.
Description of main 1.0 The student logs into the EduNext system.
sequence : 2.0 The student navigates to the "Help" or "Support" section of the
platform.
3.0 The student selects the "User Guide" option.
4.0 The system displays the user guide content.
5.0 The system displays the user guide content.
Description of alternative 1.0 User guide not found
sequence : ● If the user guide is not available or cannot be accessed, the
system displays an error message or a message indicating that
the user guide is currently unavailable.
2.0 No internet connection
● If the user does not have an internet connection, the system
may display an error message or attempt to load a local copy of
the user guide.
Use Cases for <edunext> Page 24

Nonfunctional 1.0 The user guide should be easy to navigate, well-organized, and
requirements : clearly written.
2.0 The user guide should be readily available to all registered users
within the EduNext platform.

Postcondition: POST-1: The student has successfully accessed and viewed the
EduNext user guide.
Outstanding questions:

18.UC-018: Create courscourse

UC ID and Name: UC -0018 : Create courscourse

Summary : This use case describes the process by which an authorized user
creates a new course on the EduNext platform. The user provides
course details, and the system validates and stores the information for
future use.
Dependency: None
Primary Actor: Teacher Secondary
Actors:
Preconditions: PRE-1: The user is logged into the EduNext platform.
PRE-2: The user has the necessary permissions to create a course.
Description of main 1. The teacher navigates to the "Create Course" section in the
sequence : EduNext platform.

2. The system displays a form with fields for course details.

3. The teacher fills in the required fields and optionally uploads

additional materials.

4. The teacher submits the form.

5. The system validates the entered information.

6. If the information is valid, the system saves the course and

assigns it a unique course ID.

7. The system notifies the user that the course has been
successfully created.

8. The course is now available for students to enroll.

Description of alternative Step 1: Course creation fails
sequence : ● If the system encounters an error, it displays an error message.
● The user is prompted to try again later .
Use Cases for <edunext> Page 25

Step 6: Invalid or missing course details

● If the system detects invalid or missing information, it displays
an error message.
● The user corrects the errors and resubmits the form.
● The system repeats the validation process.

Nonfunctional 1.0 The course creation process should be intuitive and require no
requirements : more than 5 steps.

Postcondition: POST-1: The course is successfully created and stored in the EduNext
database.
POST-2: The user is notified of the successful creation .
Outstanding questions: What specific user roles and permissions will be supported?

19.UC-019: View Assignment

UC ID and Name: UC -0019 : View Assignment

Summary : This use case describes the process for a student to view an
assignment within the EduNext platform.
Dependency: UC0015 (Managing Users): A valid student account must exist.
Primary Actor: Student Secondary
Actors:
Preconditions: PRE-1: The student is logged into the EduNext system.
PRE-2: The assignment is available to the student.
Description of main 1.0 The student navigates to the course page.
sequence : 2.0 The student accesses the "Assignments" section.
3.0 The student selects the desired assignment.
4.0 The system displays the assignment details, including:
● Assignment title and description
● Due date and time
● Submission instructions

Description of alternative 1.0 Assignment not found

sequence : ● If the assignment cannot be found or is not accessible to the
student, the system displays an error message or indicates that
the assignment is not available.
2.0 No internet connection
● If the student does not have an internet connection, the system
may display an error message
Nonfunctional 1.0 The assignment details should be presented in a clear and concise
requirements : manner.
Use Cases for <edunext> Page 26

2.0 The system should load assignment details quickly and efficiently.

Postcondition: POST-1: The student has successfully viewed the details of the
selected assignment.
Outstanding questions:

20.UC-020: View Course

UC ID and Name: UC - 020 : View Courses

Summary : This use case describes the process of users viewing the list of
courses they are enrolled in on EduNext system by semester
Dependency: None
Primary Actor: Teacher, Student
Preconditions: PRE-1: The user must be logged into the EduNext system.
Description of main 1.0 The system displays a list of courses the user is enrolled in.
sequence :
Description of alternative ALT-1: If the user is not enrolled in any courses, the system displays a
sequence : message: "You are not currently enrolled in any courses."
Nonfunctional The system should validate login attempts within 2 seconds.
requirements :
Postcondition: POST-1: The user successfully views the list of courses they are
enrolled in.
Outstanding questions:

21.UC-021: View Course Detail

UC ID and Name: UC - 021: View Courses Detail

Summary : This use case describes the process of users viewing detailed
information about a specific course
Dependency: UC - 017(View Courses)
Primary Actor: Teacher, Student
Preconditions: PRE-1: The user must be logged into the EduNext system
PRE-2: The user must be enrolled at least 1 course in EduNext
system
Description of main 1.0 The user selects a course from the list.
sequence : - The system displays detailed information about the course,
including information of teacher, list of slots with title, times
and date for each slot

Description of alternative None

Use Cases for <edunext> Page 27

sequence :
Nonfunctional The system should display the content of a slot within 3 seconds.
requirements :
Postcondition: POST-1: The user successfully views detailed information about the
selected course
Outstanding questions:

22.UC-022: View Slot

UC ID and Name: UC - 022 : View Slot

Summary : This use case describes the process of teacher and student viewing
the slot detail of their enrolled courses.
Dependency: UC - 018 (View Course Detail)
Primary Actor: Teacher, Student
Preconditions: PRE-1: Teacher and student must be logged into the EduNext system
PRE-2: Teacher and student must select a course to view its slot list.
Description of main 1.0 The user navigates to the "View Slot" section of a slot
sequence : - The system displays the information for that slot, including
class name, dates, times, and questions, assignments for that
slot

Description of alternative ALT-1: If the slot has no content, the “View Slot” section is not display
sequence :
Nonfunctional The system should display the content of the selected slot within 3
requirements : seconds.
Postcondition: POST-1: The user successfully views the content of the selected slot

Outstanding questions:

23.UC-023: View List Of Question

UC ID and Name: UC - 023 : View List Of Questions

Summary : This use case describes the process of users viewing a list of
questions in a slot
Dependency: UC - 018 (View Course Detail)
Use Cases for <edunext> Page 28

Primary Actor: Teacher, Student

Preconditions: PRE-1: Teacher and student must be logged into the EduNext system
PRE-2: Teacher and student must select a course to view its slot list.
Description of main 1.0 Teacher and student select a slot from the list.
sequence : - The system displays the list of questions of that slot below the
title

Description of alternative ALT-1: If no questions are associated with the slot, the system
sequence : displays a message: "This slot has no content"
Nonfunctional The system should load and display the questions within 2 seconds.
requirements :
Postcondition: POST-1: The user successfully views the list of questions of the
selected slot.
Outstanding questions:

24.UC-024: View Detail Question

UC ID and Name: UC - 024 : View Detail Question

Summary : This use case describes the process of users viewing detailed
information about a specific question in a slot
Dependency: UC - 020 (View List of Questions)
Primary Actor: Teacher, Student
Preconditions: PRE-1: Teacher and student must be logged into the EduNext system
PRE-2: Teacher and student must select a slot to view its question list
Description of main 1.0 Teacher and student selects a question from the list.
sequence : - The system displays the detailed content of the question,
including times, the description, answers, and associated
comments.

Description of alternative None

sequence :
Nonfunctional The system should display the question details within 2 seconds.
requirements :
Postcondition: POST-1: The user successfully views detailed information about the
selected question.
Outstanding questions:
Use Cases for <edunext> Page 29

25.UC-025: Course Management

UC-025: Course Management

UC ID and Name:

Allows teachers to manage categories for a class.

Summary:

N/A.
Dependency:

Teacher
Actor: Secondar
y Actors:

Preconditions: PRE1: Teacher has logged into the system with the authority
to manage tests and grades.

PRE2: Teachers have been assigned a teaching schedule that

includes classes for the current semester.

Description of main 1, The teacher selects their class for the semester.
sequence:
2, The teacher accesses the "Course Management" feature.

3, The system displays sub-functions.

4, In the sub-function, users can choose the functions: add

question, delete, edit question, Generate Report and Manage
Assessment and Grading

Description of alternative STEP2: The system detects that the class has no students
sequences: associated with it. Displays the message: "The student list is
empty. Please check again.

Nonfunctional N/A
requirements:

Postcondition: POST-1: Teachers can successfully implement quizzes or

Use Cases for <edunext> Page 30

tests for their classes.

Outstanding questions:

26. UC-26: Create assignment

UC-026: Create Assignment

UC ID and Name:

Allows teachers create assignment for a specified slot

Summary:

Include View Slot use case

Dependency:

Teacher None
Actor: Secondary
Actors:

Preconditions: PRE1: Teacher has logged into the system with the authority
Use Cases for <edunext> Page 31

to manage tests and grades.

PRE2: Teachers have been assigned a teaching schedule that

includes classes for the current semester.

PRE3: The course must exist in the system with at least one
slot available.

Description of main 1. The teacher chooses a specific course and slot.

sequence: 2. The teacher clicks the "Create assignment" button.
3. The teacher enters the assignment details and
presses the submit button.
4. The system confirms that the submission was
successful.
5. The assignment is successfully displayed on the
EduNext system.

Description of alternative STEP3: If the question data entered by the teacher is invalid
sequences: (e.g., missing required fields, incorrect format), the system
displays an error message and prompts the teacher to correct
the input and resubmit the form.

Nonfunctional N/A
requirements:

Postcondition: POST-1: Teachers can successfully create and manage

assignments for this slot.

Outstanding questions:
Use Cases for <edunext> Page 32
Use Cases for <edunext> Page 33

III.Diagram
1.Context Diagram
Use Cases for <edunext> Page 34

2.Entity Class Diagram

3. System context diagram( Sua)

Use Cases for <edunext> Page 35

4.Deployment View(sua)

5.Dynamic View(s)
Use Cases for <edunext> Page 36

6.Structural View(s)
Use Cases for <edunext> Page 37

7.Integrated communication diagram

8.Communication Diagram

Add User (Lê Thành Đạt)

Use Cases for <edunext> Page 38

Sign In: (huyền )

UC-007: Support contact(Hiếu)

Use Cases for <edunext> Page 39

Answer the question (Nghĩa)

UC - 26 : Create Assignment (Huy)