Prepared by : SE1729_NET - Group 5

Lecturer : Lê Mai Đông - DongLM6

Vũ Đình Khiêm - HE170306

Trình Ngọc Tuân - HE163211
Phạm Quang Thắng - HE172671
Trương Quang Lộc - HE170736
Lê Bá Hải Hà - HE176636

– Hanoi, May 2024 –

I. Requirement Modeling
1. List Actor
No Actor Description

1 Admin - User management

- View,Document and add or update patient medical

records,report.
- Request Tests and Imaging
2 Doctor
- Prescribe medication for patients to use during
inpatient treatment or discharge from the
hospital

- View Document and add, update patient medical

records.
3 Nurse - Monitor symptoms and patient condition, reporting
any changes for emergencies to doctors and to the
system.

- Manage patient check-in and check-out,room

4 Receptionist locate processes, ensuring accurate record-
keeping and smooth transitions.

5 Receipt Printer - Print out receipt for patient

Payment
6 - create payment transaction for patient banking fee
Gateway
2. Use case diagram

3. List Use Case

ID Use case Actor Author

Admin, Doctor,
UC-01 Login KhiemVDHE170306
Nurse, Receptionist

Admin, Doctor,
UC-02 Logout KhiemVDHE170306
Nurse, Receptionist

Admin, Doctor,
UC-03 View Home Page KhiemVDHE170306
Nurse, Receptionist

UC-04 View Patient Reports Doctor,Nurse KhiemVDHE170306

UC-05 Prescribe Medications Doctor KhiemVDHE170306

UC-06 View Patient Information Doctor,Nurse KhiemVDHE170306

UC-07 View User List Admin TuanTNHE163211

UC-08 Active/Deactivate User Admin TuanTNHE163211

UC-09 Edit User Admin TuanTNHE163211

UC-10 Schedule Appointments Admin TuanTNHE163211

UC-11 Room Allocation Receptionist TuanTNHE163211

UC-12 Patient registration Receptionist ThangPQ21

UC-13 Patient Discharge Receptionist ThangPQ21

UC-14 View Receipt List Receptionist ThangPQ21

UC-15 Create Receipt Receptionist ThangPQ21

Edit Receipt
UC-16 Receptionist ThangPQ21

UC-17 Delete Receipt Receptionist ThangPQ21

UC-18 Request Tests and Imaging Doctor HaLBHHE176636

Create New User Account

Admin TuanTNHE163211
UC-19

Admin,Doctor,Nurse,
Authenticate User Loctqhe170736
UC-20 Receptionist
UC-21 View Patient List Doctor,Nurse Loctqhe170736

UC-22 Search Patient Doctor,Nurse Loctqhe170736

UC-23 View Patient Record List Doctor,Nurse Loctqhe170736

UC-24 View Patient Record Doctor,Nurse Loctqhe170736

UC-25 Add Patient Record Doctor,Nurse Loctqhe170736

UC-26 Update Patient Record Doctor,Nurse Loctqhe170736

UC-27 View user details Admin TuanTNHE163211

4. Use Case Description

4.1 Login
UC ID and Name: UC-01: Login

Summary Users use their username and password to access the Hospital
management system.

Dependency: N/A

Actors: Admin, Doctor, Nurse, Receptionist

Preconditions The user must have a valid account in the system.

Main sequence: 1. The user accesses the login page.

2. The system displays the login form.
3. The user enters their username and password.
4. The system validates the user's credentials.
 5. If the credentials are valid, the system logs the user in
and grants access.
6. Once logged in, the user can access the system's
features and functions.

Alternative 5. The credentials are invalid, an error message is displayed,

sequences: and the user is prompted to re-enter their information.

Nonfunctional Security: User passwords must be encrypted using MD5

requirements: hashing.
Performance: The system validates the user's credentials
within equal or less than 5 seconds.

Postcondition: The user is successfully logged into the hospital

management system.

Outstanding N/A
questions:

4.2 Logout
UC ID and Name: UC-02: Logout

Summary Users log out from the system

Dependency: N/A

Actors: Admin, Doctor, Nurse, Receptionist.

Preconditions Users already login to the system.

Main sequence: 1. User accesses the User Login screen.

2. User login successfully.
3. Home page is shown and users can access the system's
features and functions.
4. User clicks on the " log out” symbol.
5. System prompts a message to ask the user to confirm.
6. User logout successfully and return to the login page.

Alternative 4. After 2 hours using the system, the user logs out
sequences: automatically.

Nonfunctional Security: System requires user to logout and enter the

requirements: credentials again after 2 hours using the system.
Performance: Logout successfully within less than 5 seconds.

Postcondition: The user is successfully logged out from the system.

Outstanding N/A
questions:
4.3 View Home Page

UC ID and Name: UC-03: View Home Page

Summary The home page displays room management, discharge

process, patient report, bed charges and provides links to
different sections of the site. Users can easily navigate to
different parts of the website from the home page.

Dependency: Include login use case

Actors: Admin, Doctor, Nurse, Receptionist

Preconditions The user must have a valid account in the system.

Main sequence: 1.Include login use case.

2. Home page is shown and users can access the system's
features and functions.
3. The home page displays room management, discharge
process, patient report, bed charges options for users to
access.

Alternative N/A
sequences:

Nonfunctional Performance: Access home page successfully within less than

requirements: 5 seconds.

Postcondition: The user gets access to features in the home page.

Outstanding N/A
questions:

4.4 View Patient Report

UC ID and Name: UC-04: View Patient Report

Summary System allows the Doctor/Nurse to view the information and

medication of the patient.

Dependency: Extend: UC-21 View Patient List

Actors: Doctor, Nurse

Preconditions 1. The user successfully logs into the system with a doctor
or nurse account.
2. There is at least 1 patient in the database of the system.

Main sequence: 1. Home page is shown and the Doctor/Nurse can access
 the system's features and functions according to their
account .
2. Doctor/Nurse access the “Patient list” page by clicking
on the “Patient List button” in the home page to view the
list of patients.
3. Doctor/Nurse choose a patient in the list and access the
report of the patient in the list .
4. Doctor/Nurse successfully view patient information and
medication in patient report.

Alternative 4. If the report of the patient is null. The system prompts a

sequences: message to inform the Doctor/Nurse to write a report for a new
patient.

Nonfunctional The system shows the patient report from the patient list in
requirements: equal or less than 5 seconds.

Postcondition: The user successfully views the record of the chosen patient.

Outstanding N/A
questions:
4.5 Prescribe Medications

UC ID and Name: UC-05: Prescribe Medications

Summary System allows a doctor to write a medical prescription for a

patient.

Dependency: Extend: View Patient Report

Actors: Doctor

Preconditions The user successfully logs into the system with a doctor
account.

Main sequence: 1. Doctor accesses the User Login screen.

2. Doctor logins successfully.
3. Home page is shown and the Doctor can access the
system's features and functions.
4. Doctor clicks on the “Patients Information” symbol.
5. Doctor clicks on the “add prescription” symbol to add a
medical prescription.
6. Doctor writes medical prescriptions for the patient.

Alternative N/A
sequences:

Nonfunctional System updates the prescription within less than 3 seconds.

requirements:

Postcondition: Patient’s medical prescription is updated successfully.

Outstanding N/A
questions:
4.6 Edit Patient Information

UC ID and Name: UC-06: Edit Patient Information

Summary This use case describes the process by which a doctor or nurse
wants to update patient information.

Dependency: Extend: View Patient Report

Actors: Doctor, Nurse

Preconditions The user successfully logs into the system with a doctor or
nurse account.

Main sequence: 1. Home page is shown and the Doctor/Nurse can access
the system's features and functions according to their
account .
2. Doctor/Nurse access the “Patient list” page to view the
list of patients.
3. Doctor/Nurse access patient record of the patient in the
list.
 4. Doctor/Nurse successfully view patient information and
medication in patient record.
5. Doctor/Nurse access Patient Information page.
6. Doctor/Nurse enter the new information of the patient to
update.
7. System updates the information and returns to the
Patient Report page.

Alternative N/A
sequences:

Nonfunctional System updates the patient’s information within less than 3

requirements: seconds.

Postcondition: Patient’s information is updated successfully

Outstanding N/A
questions:

4.7 View User List

UC ID and Name: UC-07: View User List
Summary This use case helps the admin view the list of users in the
system.

Dependency: N/A

Actors: Admin

Preconditions Admin has logged in

Main sequence: 1.Admin login into the system successfully.

2.User clicks the “User Management” menu.
3.System shows user list.

Alternative Step 3: If the system cannot display data or list is empty , an

sequences: error message will be displayed.

Nonfunctional Performance: List users will be displayed after 3 seconds

requirements:

Postcondition: Admin can view the list of users.

Outstanding N/A
questions:

4.8 Active/Deactive User

UC ID and Name: UC-08: Active/Deactive User

Summary This use case allows admin to Activate/Deactivate user.

Dependency: N/A

Actors: Admin
Preconditions User has logged in as Admin

Main sequence: 1.Admin login into the system successfully.

2.User clicks the “User Management” menu.
3.System shows user list.
4.User click on ban/unban-visibility button
5.User click icon Active/Deactivate button.
6.System sets user’s status to Active/Deactivate

Alternative Step 5: User click Active/Deactivate button so the update

sequences: information will not change

Nonfunctional Performance: status of user will updated immediately

requirements:

Postcondition: User account is activated/deactivated status

Outstanding N/A
questions:

4.9 Edit User

UC ID and Name: UC-09: Edit User

Summary This use case allows admin to edit user

Dependency: N/A

Actors: Admin

Preconditions User has logged in as Admin.

Main sequence: 1.Admin login into the system successfully.
2.User clicks the “User Management” menu.
3.System shows user list.
4.User click the “Edit” icon in the user list.
5.System shows Edit user screen.
6.User change information and click submit.
7.System save the changes.

Alternative Step 5: Users fill in blank into fields ,an error message is
sequences: displayed, and the user is prompted to re-enter their
information.

Nonfunctional Performance: information of the user will update and return

requirements: userlist in 3 seconds.

Postcondition: User account is updated

Outstanding N/A
questions:

4.10 Schedule Appointments

UC ID and Name: UC-10: Schedule Appointments

Summary This use case allows create appointments for patients with
specific doctors or medical departments.

Dependency: N/A

Actors: Admin

Preconditions User has logged in as Admin

Main sequence: 1.Admin login into the system successfully.
2.Admin clicks “Schedule Appointments”.in homepage
3.System shows schedule form.
4.Admin fills in time and appointment information.
5.Admin clicks the “Create” button.
6.The system will create an appointment between the doctor
and the patient, and the doctor will also receive a notification
containing that appointment information.

Alternative Step 4: User fills input date which is in the past,an error
sequences: message is displayed, and the user is prompted to re-enter their
information.

Nonfunctional Performance: System can continuous create 5 appointments

requirements: for 5 doctors less or equal 1 minute

Postcondition: An appointment schedule between doctor and patient is created

Outstanding N/A
questions:
4.11 Room Allocation
UC ID and Name: UC-11: Room Allocation

Summary This use case allows the Receptionist booking bed for patients
with inpatient needs at the hospital.

Dependency: N/A

Actors: Receptionist

Preconditions The user must have a valid account in the system.

The system or application is running and accessible.

Main sequence: 1.Receptionist login into the system successfully.

2.User clicks the “Booking Room” in homepage.
3.User choose a room.
4.System required to enter information of patient and choose
bed for patient.
5.User click save button.
6.System save the changes and navigate to room list.

Alternative Step 4: User chooses a room but the bed is full ,so an error
sequences message is displayed, and the user is prompted to choose
another room.

Nonfunctional Performance: The system can continuously book beds for 100
requirements: patients in 1 minute.

Postcondition: The patient was successfully booked a bed.

Outstanding N/A
questions:
4.12 Patient registration

UC ID and Name: UC-12: Patient registration

Summary Receptionist adding a patient with that person's personal

information into the list of patient in the system

Dependency: Include: Login

Actors: Receptionist

Preconditions - User has logged in as Receptionist

- The number of patients in the system must not exceed
the maximum allowed number

Main sequence: 1. Include login use case.

2. Receptionist go to the Patient Registration site.
3. System show patient information form
4. Receptionist fills in patient information
5. Receptionist clicks “Create” button
6. The system adds 1 patient with the same information
entered as above to the list of patients and adds it to the
system.

Alternative Step 6: The system checks that the number of patients in the
sequences: system has exceeded the allowed number, the screen displays
a notification that the hospital has reached the maximum
 number of patients allowed and no more patients are allowed.

Nonfunctional Performance: Check and add patients to the system in less

requirements: than 10 seconds

Postcondition: 1 patient will be added to the system

Outstanding N/A
questions:

4.13 Patient Discharge

UC ID and Name: UC-13: Patient Discharge

Summary Receptionist remove patient from their bed and change status
to discharge

Dependency: Extends: view patient list

Actors: Receptionist

Preconditions - User has logged in as Receptionist

- There is at least 1 patient in the system

Main sequence: 1. Receptionist login in the system successfully

 2. Receptionist go to list patient
3. System show list patient
4. Receptionist clicks “Discharge” button
5. Receptionist select option yes
6. The system will change this patient status to discharge
in the list of patients.

Alternative Step 5: Receptionist select option no

sequences: 6. Back to homepage

Nonfunctional Performance: Remove patients to the list in less than 10

requirements: seconds

Postcondition: 1 patient will be removed from the patient list

Outstanding N/A
questions:

4.14 View Receipt List

UC ID and Name: UC-14: View Receipt List

Summary Receptionist view list of receipt

Dependency: Extends: Login

Actors: Receptionist

Preconditions - User has logged in as Receptionist

Main sequence: 1. Receptionist login in the system successfully

2. Receptionist clicks “Receipt”
3. System show list receipt

Alternative N/A
sequences:

Nonfunctional Performance: Can load each page in less than 5 seconds

requirements:

Postcondition: System show the list of receipt

Outstanding N/A
questions:

4.15 Create Receipt

UC ID and Name: UC-15: Create Receipt

Summary Receptionist create a receipt add a receipt into the system

Dependency: Extends: View Receipt List

Actors: Receptionist

Preconditions - User has logged in as Receptionist

Main sequence: 1. Receptionist clicks “Add Receipt”

2. Receptionist choose the patient want to create receipt
3. System show information of receipt

Alternative Step 3: If the patient has not used any services or purchased
sequences: anything at the hospital, there will be no receipt

Nonfunctional Performance: Create receipt less than 10 seconds

requirements:

Postcondition: A receipt is created and added into the system

Outstanding N/A
questions:

4.17 Delete Receipt

UC ID and Name: UC-17: Delete Receipt

Summary Receptionist delete a receipt in the system

Dependency: Include : UC-14 View Receipt List

Actors: Receptionist

Preconditions - User has logged in as Receptionist

Main sequence: 1. include UC 14 view receipt list

2. Receptionist clicks “Delete” beside the receipt
3. System show give notice if you are sure you want to
delete it
4. Receptionist choose “yes”
5. This receipt will be removed from the system
6. Reload the receipt list

Alternative Step 3: If the receptionist choose “no”, screen will back to list
sequences: receipt screen

Nonfunctional Performance: Delete receipt and reload less than 8 seconds

requirements:

Postcondition: A receipt is removed from system

Outstanding N/A
questions:

4.18 Request Tests and Imaging

UC ID and Name: UC-18: Request Tests and Imaging

Summary This process involves the Doctor requesting tests and imaging
for a patient.

Dependency: Include “Login”

Actors: Doctor

Preconditions - User has logged in as Doctor

Main sequence: 1. Include UC - 1 : Login

1. Doctor assesses the Patient List to view the list of
patients.
2. Doctor selects the "Request Tests and Imaging" option.
3. The system will display a message saying are you sure
you want the patient to be tested and imaging?
4. Doctor choose “yes”
5. Back to Patient List and tick X on the button

Alternative Step 3: If the doctor choose “no”, screen will back to list Patient
sequences: List

Nonfunctional
requirements:

Postcondition: The requested tests and imaging are logged and the patient’s
medical record is updated accordingly.

Outstanding N/A
questions:
4.19 Create New User Account

UC ID and Name: UC-19: Create New User Account

Summary This use case allows admin to create new user

Dependency: N/A

Actors: Admin

Preconditions User has logged in as Admin

Main sequence: 1.Admin login in the system successfully

2.User clicks “User Management” menu
3.System shows userlist
4.User click icon “Add” in the User list
5.System show Create user screen
6.User enter information and click submit.
7.System create new user account and send email to user

Alternative Step 6:User fill blank into fields ,an error message is displayed,
sequences and the user is prompted to re-enter their information

Nonfunctional Performance: The system can continuously created 100

requirements: patients in 1 minute

Postcondition: New account is created

Outstanding N/A
questions:

4.20 Authenticate User

UC ID and Name: UC-20: Authenticate User

Summary This use case describes the process system authenticate user
 so that defined the role is using system

Dependency:

Actors: Doctor,Nurse,Admin,Receptionist

Preconditions User have to login into an account that already exist in system

Main sequence: 1.The user initiates the authentication process (e.g., clicks on a
"Login" button).
2.The system prompts the user to enter their credentials.
3.The user enters their username/email and password.
4.The system validates the provided credentials against the
stored user data.
5.If the credentials are valid, the system authenticates the user
and grants access to authorized features and functionalities that
fit with the role of the account.
6.The system Send-Redirect User to the Home Page

Alternative 5.The Credential are invalid,system tell user that

sequences: username/password is wrong and let user to stay in login
window to re-input login credentials

Nonfunctional User passwords must be stored as a secure hash instead of in

requirements: plain text.

Postcondition: User must login with an account have role Doctor or Nurse

Outstanding
questions:
4.21 View Patient List

UC ID and Name: UC-21: View Patient List

Summary This use case describes the process of user view the Patient
List that available in system

Dependency: include UC-1 Login

Actors: Doctor,Nurse

Preconditions There is already patient record exist in database

and user been authenticate by logging the system

Main sequence: 1. Include from UC-1 Login

2. User click on Patient List
3. System send redirect user to the Patient List tab and get all
patient form a list

Alternative
sequences: 3. User click on Patient List
4. System pop up window tell user to Login

Nonfunctional - Only authorized medical personnel have access to

requirements: patient lists.
Patient data must be encrypted and protected from
unauthorized access.
- Patient List should be sorted by first character of patient
name

Postcondition: - All patient that exist in database should be display in the

list ,each information should be visible in a row is
+ Name
+ Gender
 + Age
+ Status (That the patient is discharged or is located
in a room)
+ Record ( To click and view record of that patient)
+ Report ( To click and view report of that patient)

Outstanding N/A
questions:

4.22 Search Patient

UC ID and Name: UC-22: Search Patient

Summary This use case describes the process by which users want to
view a specific patient by using searching bar

Dependency: include UC-21 View Patient List

Actors: Doctor,Nurse

Preconditions User

Main sequence: include UC-21 View Patient List

3. User input a specific patient name into search bar
4.System return patient with name that contain all character in
the search bar

Alternative 4. There is no name that contain all character in the search bar
sequences: so system return no result

Nonfunctional Search response times must be fast and results accurate

requirements:

Postcondition: User must login with an account have role Doctor or Nurse

Outstanding N/A
questions:
4.23 View Patient Record List

UC ID and Name: UC-23: View Patient Record List

Summary This use case describes the process by which users want to
view a list of patient record

Dependency: include UC-21: View Patient List

Actors: Doctor,Nurse

Preconditions There is already patient record exist in database

Main sequence: 1. include UC-21 : View Patient List

2. Find patient want to view record list and click “view record”
3. System send-redirect user to that patient record list
4. View Patient Record list

Alternative
sequences:

Nonfunctional All record must be sorted by date from newest to oldest

requirements:

Postcondition: User can see all record of patient that available in database

Outstanding
questions:
4.24 View Patient Record

UC ID and Name: UC-24: View Patient Record

Summary This use case describes the process by which users want to
view a patient record that already exist in patient record list

Dependency: Include UC-23 : View Patient Record List

Actors: Doctor,Nurse

Preconditions There is already patient record exist in patient record list

Main sequence: 1. User accesses the User Login screen and login with an
account have role is Doctor or Nurse
2. If login success,system send redirect user to home page
3. User click on Patient List
4. System send redirect user to Patient list tab
5. User click “View Record” of a patient that need to see record
list
6. System send redirect user to “Patient Record List”
7. Click on a Record
8. View Patient record

Alternative
sequences: 7.There is no record of a patient yet

Nonfunctional
requirements:

Postcondition: User must login with an account have role Doctor or Nurse
4.25 Add Patient Record

UC ID and Name: UC-25: View Patient Record

Summary This use case describes the process by which users want to
view a patient record that already exist in database

Dependency: include UC-23 : View Patient record list

Actors: Doctor,Nurse

Preconditions When there is new information that need new record

Main sequence: 1. include UC-23 View Patient record list

2.Click Add record
3.System will send redirect user to the add record tab
4.User input new record information
5.Click “Add Record”

Alternative 4. User miss some information that need to input

sequences: 5. Click “Add Record”
6. System show notification which field user miss

Nonfunctional All information should be save to database correctly and the

requirements: same

Postcondition: A new record will appear in database and system will display it
in record list of that patient

Outstanding
questions:
4.26 Update Patient Record

UC ID and Name: UC-26: Update Patient Record

Summary This use case describes the process by which users update a
patient record that already exist in database

Dependency: Include: UC-24 : View Patient Record

Actors: Doctor,Nurse

Preconditions There is already patient record exist in database that need to

update

Main sequence: 1. Include UC-24 View Patient Record

4.User click update button next to the record user want to
update
5.System send redirect user to update record`s tab
6.User update patient record information and click “Update
Record”
7.System update patient record to the latest information

Alternative Step 4. User click back button so the update information will not
sequences: change

Nonfunctional The information should be update correctly and replace with the
requirements: old information

Postcondition: -Patient record should be change and update successfully into

database
-User must login with an account have role Doctor or Nurse

Outstanding
questions:
4.27 View user details
UC ID and Name: UC-27: View user details

Summary This use case allows admin to view user details page

Dependency: N/A

Actors: Admin

Preconditions User has logged in as Admin

Main sequence: 1.Include UC 7 View Userlist

2.User click icon “View” button in the User list
3.System display user details screen for user to view

Alternative Step 2: If the system cannot display data, an error message will
sequences: be displayed.

Nonfunctional Performance: The system can load all information of user in 1

requirements: second

Postcondition: Admin can view user details page

Outstanding N/A
questions:

II. Analysis
1.Entity Diagram

2.System Context Diagram

3.Boundary Class

4.Integrated Communication Diagram

5. Structural View

6.Dynamic View
7.Subsystem
8. Deployment View
9. Class Diagram

10. Layer Of Abstraction

11. Individual Part

A. Vũ Đình Khiêm( He170306 )

1. Requirement
4.1 Login
4.3 View Home Page

2. Static modeling
Entity Class

2.1.1 Login
 2.1.2 View HomePage

Class

2.2.1 Login
 2.2.2 View HomePage

3. Dynamic Modeling

3.1 Login

UC ID and Name: UC-01: Login

Summary Users use their username and password to access the Hospital
management system.

Dependency: N/A

Actors: Admin, Doctor, Nurse, Receptionist

Preconditions The user must have a valid account in the system.

Main sequence: 1.The user accesses the login page.

2.The UserCoordinators display the login form.
3.The user enters their username and password.
4.The UserService validates the user's credentials.
5.If the credentials are valid, the UserCoordinators log
the user in and grant access.
6.Once logged in, the user can access the system's
features and functions.

Postcondition: The user is successfully logged into the hospital

management system.
Identify boundaries and internal objects
-Boundary object: LoginInteraction
-Internal object: UserCoordinators
-Service: UserService

Messages
M1: Guest sends request to LoginInteraction
M2: LoginInteraction passes the login request to UserCoordinators for processing.
M3: User Coordinators send authentication requests for login information to the User
M4: Users Service validate information then send login success response to
UserCoordinatiors
M5: UserCoordinators send response login success to LoginInteraction
M6: LoginInteraction show message login success

Alternative: [wrong information]

UC ID and UC-01: Login
Name:

Summary Users use their username and password to access the Hospital
management system.

Dependency: N/A

Actors: Admin, Doctor, Nurse, Receptionist

Preconditions The user must have a valid account in the system.

Alternative 5a. UserService checked that the credentials are invalid,

sequences: 6a. an error message is sent to UserCoordinators , and the user
is prompted to re-enter their information.

Postcondition: The user is successfully logged into the hospital

management system.

Messages
M4A.1: User Service sends response validation failed to UserCoordinators.
M5A.2: UserCoordinators send message error to LoginInteraction.
M6A.3: LoginInteraction show [wrong input information] error message and prompt request to
enter credential again.

3.3 View Home Page

UC ID and Name: UC-03: View Home Page

Summary The home page displays room management, discharge

process, patient report, bed charges and provides links to
different sections of the site. Users can easily navigate to
different parts of the website from the home page.

Dependency: Include login use case

Actors: Admin, Doctor, Nurse, Receptionist

Preconditions The user must have a valid account in the system.

Main sequence: 1. Include login use case.

2. Home page is shown and users can access the system's
features and functions.
3. The home page displays room management, discharge
process, patient report, bed charges options for users to
access.

Postcondition: The user gets access to features in the home page.

Identify boundaries and internal objects
-Boundary object: HomePageInteraction
-Internal object: UserService

Messages
M1: User sends a request to HomepageInteraction.
M2: HomepageInteraction sends a request to the HomeSystem to load the
homepage.
M3: The HomeSystem sends data of the account to UserService
M4: User Service sends authorization of account to HomeSystem.
M5: HomeSystem sends homepage data to HomepageInteraction.
M6: HomepageInteraction displays the homepage to the customer.

B. Lê Bá Hải Hà (HE176636)

1. Requirement

1.1 UC-25 Add Patient Record

1.2 UC-26 Update Patient Record

2. Static modeling

2.1 Add Patient Record

 2.2 Update Patient Record

3. Dynamic Modeling

3.1.1 Use case model

UC-25 Add Patient Record

3.1.2 Identify boundary and internal objects.

- Boundary objects: PatientPage
- Internal objects: PatientService, PatientCoordinator

3.1.3 Messages
M1: Doctor adds a new patient record on PatientPage.
M2: PatientPage sends the PatientRecord to the doctor.
M3: PatientCoordinator send new PatientRecord to PatientService
M4: PatientService return update status "Succeed" to PatientCoordinator
M5: PatientCoordinator return update status "Succeed" to Patient Page
M6: Patientpage display update status

3.1.4 Alternative
a. Alternative 1: Doctor enters incomplete details
M1a1.1:Missing a field required
M2a1.2:Return error message
 3.2.1 Use case model
UC-26 Update Patient Record

3.2.2 Identify boundary and internal objects.

- Boundary objects: PatientPage
- Internal objects: PatientService, PatientCoordinator

3.2.3 Messages
M1: Doctor selects a patient record to update on PatientPage.
M2: PatientPage sends PatientRecord updated to PatientCoordinator.
M3: PatientCoordinator send PatientRecord updated to PatientService
M4: PatientService return update status "Update Succeed" to
PatientCoordinator
M5: PatientCoordinator return update status "Update Succeed" to
PatientPage
M6: Patientpage display update status

3.2.4 Alternative
Alternative 1: Invalid Data Entry
M2a1.2: invalid or incomplete data
M2a1.2: Return error message

2
4. Architecture design

C. Trương Quang Lộc (HE170736)

1.Requirement
UC-20 : Authenticate User
UC-21 : View Patient List
UC-22 : Seach Patient
UC-23 : View Patient Record List
UC-24 : View Patient Record

2.Static Modeling
3.Dynamic Modeling

3.1 Search

b. Identify boundary and internal objects.

 Boundary object : PatientListPage
Internal Object : User(Doctor/Nurse),Impatient data service

c. Message

M1.1: Doctor/Nurse input search key in patient record list page

M1.2: User Interaction send search request Patient Coordinator
M1.3: Patient Coordinator request data from Impation data service
M1.4: Impation data service return data result
M1.5:

3.2 View Patient List

a.communication diagram

b. Identify boundary and internal objects.

Boundary object : Homepage, PatientListPage

Internal Object : User(Doctor/Nurse),Database

c. Message

M1.1: Doctor/Nurse request to access patient list page

M1.2: user Interaction request access patient list data
M1.3: Coordinator request data
M1.4: data service return data of patient list
M1.5: Redirect user to Patient List page

d. Alternative sequence

a1: User role is not Doctor and Nurse

M1.2.1: System Validate role return fail
M1.2.2: Request access to patient list fail

3.3. View patient record list

a.communication diagram

b. Message

M1.1: Doctor/Nurse request to access patient record list page

M1.2 : User Interaction request patient coordinator to access patient data service
M1.3: Coordinator request patient record list data
M1.4: Patient Service data service return patient record data
M1.5: system send redirect user to patient record list page

3.3. View patient record

a.communication diagram
D. Phạm Quang Thắng (HE172620)

1. Requirements

1.1 Patient registration

UC ID and Name: UC-12: Patient registration

Summary Receptionist adding a patient with that person's personal

information into the list of patient in the system

Dependency: Include: Login

Actors: Receptionist

Preconditions - User has logged in as Receptionist

- The number of patients in the system must not exceed
the maximum allowed number

Main sequence: 1. Extend login use case.

2. Receptionist go to the Patient Registration site.
3. System show patient information form
4. Receptionist fills in patient information
5. Receptionist clicks “Create” button
6. The system adds 1 patient with the same information
entered as above to the list of patients and adds it to the
system.

Alternative Step 6: The system checks that the number of patients in the
sequences: system has exceeded the allowed number, the screen displays
 a notification that the hospital has reached the maximum
number of patients allowed and no more patients are allowed.

Nonfunctional Performance: Check and add patients to the system in less

requirements: than 10 seconds

Postcondition: 1 patient will be added to the system

Outstanding N/A
questions:

1.2 Patient discharge

UC ID and Name: UC-13: Patient Discharge

Summary Receptionist remove patient from their bed and change status
to discharge

Dependency: Extend: view patient list

Actors: Receptionist

Preconditions - User has logged in as Receptionist

- There is at least 1 patient in the system

Main sequence: 1. Receptionist login in the system successfully

2. Receptionist go to list patient
3. System show list patient
4. Receptionist clicks “Discharge” button
5. Receptionist select option yes
6. The system will change this patient status to discharge
in the list of patients.

Alternative Step 5: Receptionist select option no

sequences: 6. Back to homepage

Nonfunctional Performance: Remove patients to the list in less than 10

requirements: seconds

Postcondition: 1 patient will be removed from the patient list

Outstanding N/A
questions:
2. Static Modeling

2.1 Entity Class

2.1.1 Patient registration

2.1.2 Patient discharge

2.2 Entity Attribute Class

2.2.1 Patient registration

2.2.2 Patient discharge

3. Dynamic Modeling

3.1 Patient registration

3.1.1 Use Case model

UC ID and Name: UC-12: Patient registration

Summary Receptionist adding a patient with that person's personal

information into the list of patient in the system

Dependency: N/A

Actors: Receptionist

Preconditions - User has logged in as Receptionist

- The number of patients in the system must not exceed
the maximum allowed number

Main sequence: ● 1 Receptionist go to the Patient Registration site

● 2 PatientRegistrationPage send information of patient to Receptionistcoordinator
● 3 ReceptionistCoordinator send registration patient to ReceptionistService
● 4 ReceptionistService send created patient information to
ReceptionistCoordinator
● 5 ReceptionistCoordinator send "successful" message to
PatientRegistrationPage
● 6 PatientRegistrationPage redirect receptionist to PatientListPag and display
"successfully" message

Alternative ● 4 ReceptionistService check the number of patients has exceeded the number
sequences: in the system and send error message
● 5 ReceptionistCoordinator send error message to PatientRegistrationPage
 ● 6 PatientRegistrationPage redirect receptionist to PatientListPage and display
error notification

Nonfunctional Performance: Check and add patients to the system in less

requirements: than 10 seconds

Postcondition: 1 patient will be added to the system

3.1.2 Identify boundaries and internal objects

● Boundary object: PatientRegistrationPage
● Internal objects: PatientService, ReceptionistCoordinator

3.1.3 Messages
Main sequence:
● M1 Receptionist go to the Patient Registration site
● M2 PatientRegistrationPage send information of patient to Receptionistcoordinator
● M3 ReceptionistCoordinator send registration patient to ReceptionistService
● M4 ReceptionistService send created patient information to ReceptionistCoordinator
● M5 ReceptionistCoordinator send "successful" message to PatientRegistrationPage
● M6 PatientRegistrationPage redirect receptionist to PatientListPag and display "successfully" message

Alternative sequence:
● M1 Receptionist go to the Patient Registration site
● M2 PatientRegistrationPage send information of patient to Receptionistcoordinator
● M3 ReceptionistCoordinator send registration patient to ReceptionistService
● M4 ReceptionistService check the number of patients has exceeded the number in the system and send error
message
● M5 ReceptionistCoordinator send error message to PatientRegistrationPage
● M6 PatientRegistrationPage redirect receptionist to PatientListPage and display error notification
E.Trình Ngọc Tuân (HE163211)

1. Requirement
4.7: UserList
4.8: Active/Deactive User
4.9: Edit User

2.Static Modeling

2.1 View UserList

2.2 Active/Deactive User

2.3 Edit User

3. Dynamic Modeling

3.1 UserList

UC ID and Name: UC-07: View User List

Summary This use case helps the admin view the list of users in the
system.

Dependency: N/A

Actors: Admin

Preconditions Admin has logged in

Main sequence: 1.Admin login into the system successfully.

2.User clicks the “User Management” menu.
3.System shows user list.

Alternative Step 3: If the system cannot display data or list is empty , an

sequences: error message will be displayed.

Nonfunctional Performance: List users will be displayed after 3 seconds

requirements:

Postcondition: Admin can view the list of users.

a.communication diagram

b.Identify boundary and internal objects

- Boundary objects: UserListPage
- Internal objects:Admin,UserList, Database

c.Message
M1: Admin send request to access userlist
M2: UserList request userlist data from database
M3: Database return list data to
M4: System send redirect to UserListPage
 d.Alternative sequence
- M3.1: System cannot return userlist data

3.2 Active/Deactive User

UC ID and Name: UC-08: Active/Deactive User

Summary This use case allows admin to Activate/Deactivate user.

Actors: Admin

Preconditions User has logged in as Admin

Main sequence: 1.Admin login into the system successfully.

2.User clicks the “User Management” menu.
3.System shows user list.
4.User click on ban/unban-visibility button
5.User click icon Active/Deactivate button.
6.System show dialog to user confirm
7.System sets user’s status to Active/Deactivate

Alternative Step 5: User click Active/Deactivate button so the update

sequences: information will not change

Postcondition: User account is activated/deactivated status

a.communication diagram

b.Identify boundary and internal objects

- Boundary objects: UserDetailPage, Dialog
- Internal objects:Admin, Database
 c.Message
- M1:Admin request deactvie/active user in UserDetailPage
- M2:UserDetailPage open dialog to confirm change status
- M3:If confirm , database return new status of user to UserDetailPage
- M4:If cancel, back to dialog.

d.Alternative sequence
- M3.1: Admin click confirm but status of user not change

3.3 Edit User

UC ID and Name: UC-09: Edit User

Summary This use case allows admin to edit user

Dependency: N/A

Actors: Admin

Preconditions User has logged in as Admin.

Main sequence: 1.Admin login into the system successfully.

2.User clicks the “User Management” menu.
3.System shows user list.
4.User click the “Edit” icon in the user list.
5.System shows Edit user screen.
6.User change information and click submit.
7.System save the changes.

Alternative Step 5: Users fill in blank into fields ,an error message is
sequences: displayed, and the user is prompted to re-enter their
information.

Postcondition: User account is updated

 a.communication diagram

b.Identify boundary and internal objects

- Boundary objects: UserDetailPage,UserListPage
- Internal objects:Admin, Database,Validate

c.Message
- M1:Admin send request edit user in UserDetailPage
- M2:System validate information
- M3:Validate successfully , database return UserList
- M4:System send redirect to UserDetailPage

d.Alternative sequence
- M2.1: System validate information return fail

4. Architecture design
SUBSYSTEM