SE1729 - NET - ProjectLab - Group 5
SE1729 - NET - ProjectLab - Group 5
Payment
6 - create payment transaction for patient banking fee
Gateway
2. Use case diagram
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
Edit Receipt
UC-16 Receptionist ThangPQ21
Admin,Doctor,Nurse,
Authenticate User Loctqhe170736
UC-20 Receptionist
UC-21 View Patient List Doctor,Nurse Loctqhe170736
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
Outstanding N/A
questions:
4.2 Logout
UC ID and Name: UC-02: Logout
Dependency: N/A
Alternative 4. After 2 hours using the system, the user logs out
sequences: automatically.
Outstanding N/A
questions:
4.3 View Home Page
Alternative N/A
sequences:
Outstanding N/A
questions:
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.
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
Actors: Doctor
Preconditions The user successfully logs into the system with a doctor
account.
Alternative N/A
sequences:
Outstanding N/A
questions:
4.6 Edit Patient Information
Summary This use case describes the process by which a doctor or nurse
wants to update patient information.
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:
Outstanding N/A
questions:
Dependency: N/A
Actors: Admin
Outstanding N/A
questions:
Dependency: N/A
Actors: Admin
Preconditions User has logged in as Admin
Outstanding N/A
questions:
Dependency: N/A
Actors: Admin
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.
Outstanding N/A
questions:
Summary This use case allows create appointments for patients with
specific doctors or medical departments.
Dependency: N/A
Actors: Admin
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.
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
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.
Outstanding N/A
questions:
4.12 Patient registration
Actors: Receptionist
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.
Outstanding N/A
questions:
Summary Receptionist remove patient from their bed and change status
to discharge
Actors: Receptionist
Outstanding N/A
questions:
Actors: Receptionist
Alternative N/A
sequences:
Outstanding N/A
questions:
Actors: Receptionist
Alternative Step 3: If the patient has not used any services or purchased
sequences: anything at the hospital, there will be no receipt
Outstanding N/A
questions:
Actors: Receptionist
Alternative Step 3: If the receptionist choose “no”, screen will back to list
sequences: receipt screen
Outstanding N/A
questions:
Summary This process involves the Doctor requesting tests and imaging
for a patient.
Actors: Doctor
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
Dependency: N/A
Actors: Admin
Alternative Step 6:User fill blank into fields ,an error message is displayed,
sequences and the user is prompted to re-enter their information
Outstanding N/A
questions:
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
Postcondition: User must login with an account have role Doctor or Nurse
Outstanding
questions:
4.21 View Patient List
Summary This use case describes the process of user view the Patient
List that available in system
Actors: Doctor,Nurse
Alternative
sequences: 3. User click on Patient List
4. System pop up window tell user to Login
Outstanding N/A
questions:
Actors: Doctor,Nurse
Preconditions User
Alternative 4. There is no name that contain all character in the search bar
sequences: so system return no result
Postcondition: User must login with an account have role Doctor or Nurse
Outstanding N/A
questions:
4.23 View Patient Record List
Summary This use case describes the process by which users want to
view a list of patient record
Actors: Doctor,Nurse
Alternative
sequences:
Postcondition: User can see all record of patient that available in database
Outstanding
questions:
4.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
Actors: Doctor,Nurse
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
Summary This use case describes the process by which users want to
view a patient record that already exist in database
Actors: Doctor,Nurse
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
Summary This use case describes the process by which users update a
patient record that already exist in database
Actors: Doctor,Nurse
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
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
Alternative Step 2: If the system cannot display data, an error message will
sequences: be displayed.
Outstanding N/A
questions:
II. Analysis
1.Entity Diagram
6.Dynamic View
7.Subsystem
8. Deployment View
9. Class Diagram
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
Summary Users use their username and password to access the Hospital
management system.
Dependency: N/A
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
Summary Users use their username and password to access the Hospital
management system.
Dependency: N/A
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.
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
2. Static modeling
3. Dynamic Modeling
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.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
2.Static Modeling
3.Dynamic Modeling
3.1 Search
c. Message
a.communication diagram
c. Message
d. Alternative sequence
b. Message
1. Requirements
Actors: Receptionist
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.
Outstanding N/A
questions:
Summary Receptionist remove patient from their bed and change status
to discharge
Actors: Receptionist
Outstanding N/A
questions:
2. Static Modeling
3. Dynamic Modeling
Dependency: N/A
Actors: Receptionist
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
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
3. Dynamic Modeling
3.1 UserList
Dependency: N/A
Actors: Admin
a.communication diagram
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
Actors: Admin
a.communication diagram
d.Alternative sequence
- M3.1: Admin click confirm but status of user not change
Dependency: N/A
Actors: Admin
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.
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