Dashboard

Use Case 1 - Account switch

Description

The MANAGER must be able to switch the account between the "Admin
Account" and the "Employee Account".

Actors

● MANAGER

● SYSTEM

Preconditions

The MANAGER sign in the “Dashboard (admin)”

Postconditions

The MANAGER switches Account to the “Dashboard (employee)” successfully.

Trigger

The MANAGER clicks the “Switch” button in the confirm popup.

Basic Flow

1. The ADMIN clicks on “switch to account” toggle on Top navigation.

2. The SYSTEM shows the confirmed popup.
3. The ADMIN clicks on the “Switch” button.
 4. The SYSTEM navigate the MANAGER to the “Dashboard (employee)”
5. [End of Use Case]

Alternate Flows

1. The ADMIN clicks on the “cancel" button.

A. The ADMIN clicks on the “cancel” button.
B. The SYSTEM takes the ADMIN back to “Dashboard (Admin)”. If any.
C. [End of Use case]
2. The MANAGER clicks the “Complete profile” button
A. The MANAGER clicks the “Complete profile” button
B. Refer to Module 3 “company profile"
C. [End of Use case]
3. The MANAGER clicks the “View all” button in “Companies” section
A. The MANAGER clicks the “View all” button
B. Refer to Module 3 “company profile”
C. [End of Use case]
4. The MANAGER clicks the “View Details” button in “Companies” section
A. The MANAGER clicks the “View Details” button
B. Refer to Module 3 “company profile”
C. [End of Use case]
5. The MANAGER clicks the “View all” button in “Latecomers today” section
A. The MANAGER clicks the “View all” button
B. Refer to Module 3 “company profile”
C. [End of Use case]
6. The MANAGER clicks the “View all” button in “Current time-off” section
A. The MANAGER clicks the “View all” button
B. Refer to Module 7 “time off”
C. [End of Use case]
7. The MANAGER clicks the “day” button in “Calendar” section
A. The MANAGER clicks the “day” button in “Calendar” section
B. Refer to Module 14 “calendar and meetings”
C. [End of Use case]
8. The MANAGER clicks the “arrow” button in “Calendar” section
 A. The MANAGER clicks the “arrow” button in “Calendar” section
B. The SYSTEM takes the “calendar” section moving to the previous or next month.
C. [End of Use case]
9. The MANAGER clicks the “notification” button
A. The MANAGER clicks the “notification” button
B. The SYSTEM takes the MANAGER to the Use case 3 “Notifications List”.
C. [End of Use case]
10. The MANAGER clicks the “user profile” button
A. The MANAGER clicks the “user profile” button
B. The SYSTEM shows dropdown menu
C. [End of Use case]
Exception Flows

1. Problem with Updating Database

A. Suppose the SYSTEM encounters an unexpected issue while attempting to switch to
account. In that case, the SYSTEM will display an error message to the MANAGER.
B. [End of Use Case]
Use case 2 - Notifications list

Description

The USER view all notification lists from Dashboard

Actors

● USER

● SYSTEM

Preconditions

The USER sign in the “Dashboard”.

Postconditions

The SYSTEM show Notifications list

Trigger

The USER clicks the “notification” button.

Basic Flow

1. The SYSTEM show notifications list

2. [End of Use Case]
Alternate Flows

1. The USER turns on “Do not disturb” mode.

A. The USER turns on “Do not disturb” mode.
B. The SYSTEM allows the USER to silence all incoming notifications on user’s device
C. [End of Use Case]
2. The USER turns off “Do not disturb” toggle
A. The USER turns off “Do not disturb” toggle
 B. The SYSTEM allows the USER to show all incoming notifications on the user's device.
C. [End of Use Case]
3. The USER clicks “Mark all as read” text
A. The USER clicks “Mark all as read” text
B. The SYSTEM marks all notifications as read.
C. [End of Use Case]

Use Case 3 - Shortcuts

Description

● The SYSTEM has an Admin dashboard where various details (shown the
table at the end of the document) will be displayed and from where
various system features can be accessed.
● The SYSTEM display the Admin's "Main Dashboard" as the home page
when sign in
Actors

● SYSTEM

● MANAGER

Preconditions

The MANAGER has previously registered the Account in the application.

Postconditions

The SYSTEM shows the “Dashboard (admin)”

Trigger
The MANAGER sign in

Basic Flow

1. The SYSTEM redirects the USER inside the app to the main admin’s
dashboard if the USER is the MANAGER.
A. The SYSTEM redirects the USER inside the app to the main
employee’s dashboard if the USER is the EMPLOYEE.
2. [End of Use Case]

Alternate Flows

1. The MANAGER clicks mini-side bar

A. The MANAGER clicks other tab on mini-side bar
B. The SYSTEM redirect the preferred screens
C. [End of Use Case]

Exception Flows

1. Problem with Updating Database

A. Suppose the SYSTEM encounters an unexpected issue while attempting to show
Shortcuts. In that case, the SYSTEM will display an error message to the ADMIN.
B. [End of Use Case]

Use Case 4 - Employee dashboard

Description
 ● The system shows the 'Main Dashboard' where various details (shown
the table at the end of the document) will be displayed and from which
various system features can be accessed.
● The system should display the employee's "main dashboard" as the
"home" page when sign in.
Actors

● SYSTEM

● EMPLOYEE

Preconditions

The EMPLOYEE has previously registered the Account in the application.

Postconditions

The SYSTEM shows the “Dashboard (employee)”

Trigger

The EMPLOYEE sign in

Basic Flow

None
Alternate Flows

1. The ADMIN clicks on the “disagree" button.

D. The ADMIN clicks on the “disagree” button.
E. The SYSTEM takes the ADMIN back to “Dashboard (Admin)”. If any.
F. [End of Use case]
2. The MANAGER clicks the “Complete profile” button
D. The MANAGER clicks the “Complete profile” button
E. Refer to Module
F. [End of Use case]
3. The MANAGER clicks the “View all” button in “Companies” section
D. The MANAGER clicks the “View all” button
E. The SYSTEM takes the MANAGER to the Use case 3 “Sign In”.
 F. [End of Use case]
4. The MANAGER clicks the “View Details” button in “Companies” section
D. The MANAGER clicks the “View Details” button
E. The SYSTEM takes the MANAGER to the Use case 3 “Sign In”.
F. [End of Use case]
5. The MANAGER clicks the “View all” button in “Latecomers today” section
D. The MANAGER clicks the “View all” button
E. The SYSTEM takes the MANAGER to the Use case 3 “Sign In”.
F. [End of Use case]
6. The MANAGER clicks the “View all” button in “Current time-off” section
D. The MANAGER clicks the “View all” button
E. The SYSTEM takes the MANAGER to the Use case 3 “Sign In”.
F. [End of Use case]
7. The MANAGER clicks the “day” button in “Calendar” section
D. The MANAGER clicks the “day” button in “Calendar” section
E. The SYSTEM shows employee’s tasks with specific time corresponding to day
F. [End of Use case]
8. The MANAGER clicks the “arrow” button in “Calendar” section
D. The MANAGER clicks the “arrow” button in “Calendar” section
E. The SYSTEM takes the “calendar” section moving to the previous or next month.
F. [End of Use case]
9. The MANAGER clicks the “notification” button
D. The MANAGER clicks the “notification” button
E. The SYSTEM takes the MANAGER to the Use case 3 “Dashboard”.
F. [End of Use case]
10. The MANAGER clicks the “user profile” button
D. The MANAGER clicks the “user profile” button
E. The SYSTEM shows dropdown menu
F. [End of Use case]
11. The MANAGER clicks mini-side bar
D. The MANAGER clicks other tab on mini-side bar
E. Refer to use case 3 “Dashboard”
F. [End of Use Case]
Exception Flows

1. Problem with Updating Database

A. Suppose the SYSTEM encounters an unexpected issue while attempting to show
“Dashboard (employee)”. In that case, the SYSTEM will display an error message to the
ADMIN.
B. [End of Use Case]

Use Case 5: Check in - Check out

Description

● The EMPLOYEE check in - check out

Actors

● SYSTEM

● EMPLOYEE

Preconditions

The EMPLOYEE has previously registered the Account in the application.

Postconditions

The SYSTEM shows the “Dashboard (admin)”

Trigger

The MANAGER click the “check in” button

Basic Flow