0% found this document useful (0 votes)
10 views10 pages

UC Specification

Uploaded by

minhnnhe160942
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views10 pages

UC Specification

Uploaded by

minhnnhe160942
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Use Case ID UC01 Use Case Name View All User

Author MinhNN Version 1.0 Date 1/6/2024


Actor Admin
Description The function allows an admin to view all registered users in the
system, including their details such as username, email, and account
status.
Precondition PRE-01: The admin must be logged in.
PRE-02: The system must have at least one user registered.
Trigger
TRG-01: Admin selects the "View Users" option from the admin
dashboard.

Post-Condition
POS-01: The system displays a list of all registered users.

Main flows
Step Actor Action
1 Admin Clicks on the “View All User” option from the admin dashboard
2 LMS Displays the "All Users" screen with a list of all registered users,
including their usernames, emails, and account statuses.
3 admin Can view the details of each user and perform actions such as edit
user details, deactivate account, etc. (if these functionalities are
provided on the same screen).

Alternative flows

AT1 At step 2 in the main flows, if there is an internal error in the system,
Sub Actor Action
step
2.1 LMS Display "Error" page with message "Internal System Error, please
contact with administrator"

Business Rules

# Rule Description
BR-01
Only admin users can access the "View All Users"
functionality.
BR-02 The user details displayed must not include sensitive information such as
passwords.
UC02 Use Case Name
Use Case ID View User Details

Author MinhNN Version 1.0 Date 1/6/2024


Actor Admin
Description The function allows an admin to view the detailed information of a
selected user in the system, including username, email, account
status, and additional details such as registration date, last login, and
role.
Precondition PRE-01: The admin must be logged in
PRE-02: The system must have at least one user registered.
Trigger
TRG-01: Admin selects a user from the "View All Users" list to view
their details.

Post-Condition
POS-01: The system displays the detailed information of the selected
user.

Main flows
Step Actor Action
1 Admin Clicks on the desired user from the "View All Users" list.
2 LMS Displays the "User Details" screen with detailed information of the
selected user, including username, email, account status, registration
date, last login, and role.

Alternative flows

AT1 At step 2 in the main flows, if there is an internal error in the system,
Sub Actor Action
step
2.1 LMS Display "Error" page with message "Internal System Error, please
contact with administrator"

Business Rules

# Rule Description
BR-01
Only admin users can access the "View User Details"
functionality.
BR-02 The user details displayed must not include sensitive information such as
passwords.
UC03 Use Case Name
Use Case ID Set Role for User

Author MinhNN Version 1.0 Date 1/6/2024


Actor Admin
Description The function allows an admin to set or change the role of a user in the
system, assigning roles such as Tenant, HomeOwner, or Admin.
Precondition PRE-01: The admin must be logged in
PRE-02: The system must have at least one user registered.
Trigger
TRG-01: Admin selects the "Set Role" option for a specific user from
the user management interface.

Post-Condition
POS-01: The system updates the role of the selected user and
confirms the change to the admin

Main flows
Step Actor Action
1 Admin Selects a user from the user management interface.
2 LMS Displays the "Set Role" screen with current role information and
available roles to assign.
3 Admin Selects the desired role from the available options and confirms the
change.
4 LMS Updates the user's role in the system and displays a confirmation
message to the admin.

Alternative flows

AT1 At step 2 in the main flows, if there is an internal error in the system,
Sub Actor Action
step
2.1 LMS Display "Error" page with message "Internal System Error, please
contact with administrator"
Business Rules

# Rule Description
BR-01
Only admin users can access the "Set Role" functionality.

BR-02 The roles available for assignment must be predefined and consistent with the
system's role management policies.

UC04 Use Case Name


Use Case ID Update user
Author MinhNN Version 1.0 Date 1/6/2024
Actor Admin
Description The function allows an admin to update the details of a registered user
in the system, including their username, email, and account status.
Precondition PRE-01: The admin must be logged in
PRE-02: The system must have at least one user registered.
Trigger
TRG-01: Admin selects the "Update User" option for a specific user
from the user management interface.

Post-Condition
POS-01: The system updates the details of the selected user and
confirms the change to the admin

Main flows
Step Actor Action
1 Admin Selects a user from the user management interface.
2 LMS Displays the "Update User" screen with current user information.
3 Admin Updates the user information (e.g., username, email, account status)
and confirms the changes.
4 LMS Updates the user's information in the system and displays a
confirmation message to the admin.

Alternative flows

AT1 At step 2 in the main flows, if there is an internal error in the system,
Sub Actor Action
step
2.1 LMS Display "Error" page with message "Internal System Error, please
contact with administrator"
Business Rules

# Rule Description
BR-01
Only admin users can access the "Update User"
functionality.

BR-02 The updated user information must comply with the system's data validation
rules.

UC05 Use Case Name


Use Case ID Block user

Author MinhNN Version 1.0 Date 1/6/2024


Actor Admin
Description The function allows an admin to block a user in the system, preventing
them from logging in and accessing any functionalities.
Precondition PRE-01: The admin must be logged in
PRE-02: The system must have at least one user registered.
Trigger
TRG-01: Admin selects the "Block User" option for a specific user from
the user management interface.

Post-Condition
POS-01:The system blocks the selected user and confirms the change
to the admin.

Main flows
Step Actor Action
1 Admin Selects a user from the user management interface.
2 LMS Displays the "Block User" confirmation screen with user details.
3 Admin Confirms the blocking action.
4 LMS Blocks the user's account in the system and displays a confirmation
message to the admin.

Alternative flows

AT1 At step 2 in the main flows, if there is an internal error in the system,
Sub Actor Action
step
2.1 LMS Display "Error" page with message "Internal System Error, please
contact with administrator"

Business Rules

# Rule Description
BR-01
Only admin users can access the "Block User"
functionality.

BR-02 The blocked user must not be able to log in or access any part of the system.

UC06 Use Case Name


Use Case ID View Post

Author MinhNN Version 1.0 Date 1/6/2024


Actor Admin
Description The function allows an admin or a user to view the details of a post,
including its content, author information, and any associated metadata
such as the date of posting and number of views or comments.
Precondition PRE-01: The actor must be logged in.
PRE-02: The system must have at least one post created.
Trigger
TRG-01: The actor selects a post from the post listing page.

Post-Condition
POS-01: The system displays the details of the selected post.

Main flows
Step Actor Action
1 Admin Selects a post from the post listing page.
2 LMS Displays the "View Post" screen with detailed information of the
selected post, including title, content, author information, date of
posting, and number of views/comments

Alternative flows

AT1 At step 2 in the main flows, if there is an internal error in the system,
Sub Actor Action
step
2.1 LMS Display "Error" page with message "Internal System Error, please
contact with administrator"

Business Rules

# Rule Description
BR-01
Only registered users can view the details of a post.

BR-02 The post details displayed must include all relevant information without exposing
any sensitive data.

UC07 Use Case Name


Use Case ID Approve Post

Author MinhNN Version 1.0 Date 1/6/2024


Actor Admin
Description The function allows an admin to approve a post, making it visible to all
users on the platform.
Precondition PRE-01: The admin must be logged in.
PRE-02: The post must be pending approval.
Trigger
TRG-01: Admin selects the "Approve Post" option for a specific post
from the post management interface.

Post-Condition
POS-01: The system updates the post status to approved and makes it
visible to all users.

Main flows
Step Actor Action
1 Admin Selects a post from the post management interface.
2 LMS Displays the "Approve Post" confirmation screen with post details.
3 Admin
Confirms the approval action.
4 LMS Updates the post status to approved and displays a confirmation
message to the admin.

Alternative flows

AT1 At step 2 in the main flows, if there is an internal error in the system,
Sub Actor Action
step
2.1 LMS Display "Error" page with message "Internal System Error, please
contact with administrator"

Business Rules

# Rule Description
BR-01
Only admin users can approve posts.

BR-02 Approved posts must be visible to all users.

UC08 Use Case Name


Use Case ID Reject Post

Author MinhNN Version 1.0 Date 1/6/2024


Actor Admin
Description The function allows an admin to reject a post, preventing it from being
visible to all users on the platform.
Precondition PRE-01: The admin must be logged in.
PRE-02: The post must be pending approval.
Trigger
TRG-01: Admin selects the "Reject Post" option for a specific post from
the post management interface.
Post-Condition
POS-01: The system updates the post status to rejected and notifies
the post author.

Main flows
Step Actor Action
1 Admin Selects a post from the post management interface.
2 LMS Displays the "Reject Post" confirmation screen with post details.
3 Admin
Confirms the rejection action and optionally provides a reason for
rejection.
4 LMS Updates the post status to rejected, notifies the post author, and
displays a confirmation message to the admin.

Alternative flows

AT1 At step 2 in the main flows, if there is an internal error in the system,
Sub Actor Action
step
2.1 LMS Display "Error" page with message "Internal System Error, please
contact with administrator"

Business Rules

# Rule Description
BR-01
Only admin users can reject posts.

BR-02 The post author must be notified of the rejection and the reason, if provided.

UC09 Use Case Name


Use Case ID Edit Post

Author MinhNN Version 1.0 Date 1/6/2024


Actor Admin
Description The function allows an admin or the post author to edit the content of
an existing post.
Precondition PRE-01: The actor must be logged in.
PRE-02: The post must exist in the system.
Trigger
TRG-01: The actor selects the "Edit Post" option for a specific post
from the post management interface.

Post-Condition
POS-01: The system updates the post status to rejected and notifies
the post author.

Main flows
Step Actor Action
1 Admin Selects a post from the post management interface.
2 LMS Displays the "Edit Post" screen with current post details.
3 Admin Edits the post information (e.g., title, content) and confirms the
changes.
4 LMS Updates the post with the new content and displays a confirmation
message to the actor.

Alternative flows

AT1 At step 2 in the main flows, if there is an internal error in the system,
Sub Actor Action
step
2.1 LMS Display "Error" page with message "Internal System Error, please
contact with administrator"

Business Rules

# Rule Description
BR-01
Only admin users or post authors can edit posts.

BR-02 The updated post content must comply with the system's content guidelines.

UC10 Use Case Name


Use Case ID Delete Post

Author MinhNN Version 1.0 Date 1/6/2024


Actor Admin
Description The function allows an admin or the post author to delete an existing
post from the system.
Precondition PRE-01: The actor must be logged in.
PRE-02: The post must exist in the system.
Trigger
TRG-01: The actor selects the "Delete Post" option for a specific post
from the post management interface.

Post-Condition
POS-01: The system removes the post and confirms the deletion to the
actor.

Main flows
Step Actor Action
1 Admin Selects a post from the post management interface.
2 LMS Displays the "Delete Post" confirmation screen with post details.
3 Admin Confirms the deletion action.
4 LMS Deletes the post from the system and displays a confirmation message
to the actor.

Alternative flows

AT1 At step 2 in the main flows, if there is an internal error in the system,
Sub Actor Action
step
2.1 LMS Display "Error" page with message "Internal System Error, please
contact with administrator"

Business Rules

# Rule Description
BR-01
Only admin users or post authors can delete posts.

BR-02 Once deleted, the post cannot be recovered.

You might also like