Computer Science Homework Help

Summary: The CEO can view monthly or daily reports, view individual payments, change doctors salary and read patients’ information.

5.1. Log-in

• Use case name: Login
• Summary: CEO login into their accounts.
• Actor: CEO
• Precondition: Idle interface displayed on screen
• Description of main sequence:

1. User select Log-in button
2. User provide account ID and password, and proceed to log in the system
3. System retrieve patient’s account information and check if the account is valid
4. If the account is valid, System continue to check if the password matches with the account ID
5. If password matches with account ID, system grants access for the user
6. System rolls back to the homepage interface

• Alternatives:

• Step 1: User doesn’t have account yet and clicks on sign-up button
• Step 2: If the account ID doesn’t exist, then roll back to the log-in interface. System raises notification of invalid account and require to retype the information. .
• Step 3: If the password doesn’t match with the account ID, then roll back to the log-in interface. System raises notification of incorrect password and require to retype the information.

• Postcondition: User has logged in into the system

5.2. Sign up

• Use Case Name: Sign up
• Summary: CEO signs up for an account to access the healthcare system by creating a username and password.
• Actor: CEO
• Precondition: Patient access the sign-up interface
• Description:

1. Patient provides the mandated information( account ID, password, date of birth, full name, email) and unmandated information(medical history, address, phone number,…)
2. System checks if all the mandated information has been filled up
3. System verifies if accountID is available
4. System verifies if the password meets the security requirement
5. System checks if the re-typed password matches the password
6. After meeting all the registration requirements, the user is given access to the online system.

• Alternative

• Step 3: Systems raises an error that accountID is invalid, requires user to retype
• Step 4: The password doesn’t meet the security requirement, system requires user to retype
• Step 5: Re-typed password doesn’t match the password, system requires user to retype the re-typed password

• Postcondition: User has registered a new account on the system

5.3. Check Record

• Use Case Name: Check Record
• Summary : CEO checks the patient’s record
• Dependency: Include Login
• Actor: CEO
• Precondition: Idle interface displayed on screen
• Description of main sequence:

1. CEO selects Check Record, systems loads the Check Record session
2. CEO enters the patient’s information to look up for the record. The system retrieves the information
3. If system finds out the patient’s record, system displays the patient’s record on screen

• Alternatives:

• Step 3: If the system cannot retrieve the patient’s record, displays a message that system could not find any corresponding patient’s record
• Step 3: If the system cannot retrieve the patient’s record, staff can select Sign Up to create a new record

• Postcondition: The patient’s record has been fetch and displayed

5.4. Check Report

• Use Case Name: Check Report
• Summary : CEO checks the hospital’s report
• Dependency: Include Login
• Actor: CEO
• Precondition: Idle interface displayed on screen
• Description of main sequence:

1. CEO selects Check Report
2. The system displays recent monthly reports and daily reports. CEO can select one to observe the performance
3. System displays a specific report

• Postcondition: The report has been fetch

5.5. Change Salary

• Use Case Name: Check Report
• Summary : CEO change the employee’s salary
• Dependency: Include Login
• Actor: CEO
• Precondition: Idle interface displayed on screen
• Description of main sequence:

1. CEO selects Change Salary
2. CEO can search up employee’s name or employee ID to look up for the employee, and CEO can also filter by the category.
3. CEO change salary of a specific employee
4. After confirmed, system updates the new salary of the employee

• Alternatives:

• Step 2: The input doesn’t match with any data. System shows message of “No result”

• Postcondition: Salary has been changed

5.6. Read Payment Information

• Use Case Name: Read Payment Information
• Summary : CEO access the payment information
• Dependency: Include Login
• Actor: CEO
• Precondition: Idle interface displayed on screen
• Description of main sequence:

1. CEO selects Payment Information
2. CEO searches up either the patients information or the payment ID to check the payment information
3. System traverses through the database and retrieve the information
4. System displays the correspondent results
5. CEO select a specific payment which needed to be looked up
6. System displays the payment information details

• Alternative

• Step 3: The looked-up input doesn’t match with any data. System shows a message of “No Result”.

• Postcondition: The payment information has been fetch