Princess Nourah Bint Abdulrahman University

College of Computer & Information Sciences

Computer Science Department

Software Engineering, CS385T- Project

Title: HealthBloom

Section: 5W2

Group no. 3

No Student Name Student Number

.
1 ‫سارة خالد الزكري‬ 439003235
2 ‫لمياء وليد الفهيد‬ 439000562
3 ‫غادة خالد ابوحيمد‬ 436002949
4 ‫يارا ماجد الفيفي‬ 439002562

First Semester 2020

Write ‘YES’ next to section(s) you worked on, or state you all shared the work by ticking on the
following statement box.

o We all share the work and responsibility of the project.

FOR INSTRUCTOR’S USE ONLY
PLO [Write student 1’s name] Max. Mark Notes
Mark Obtain
[write YES next your
Table of Contents part] 1
Project Description ‫ غادة أبوحيمد‬،‫سارة الزكري‬
Functional Requirements ‫يارا الفيفي‬
(user and system requirements)
2
Non-Functional Requirement ‫لمياء الفهيد‬
(user and system requirements)
Context Diagram with description 1
Use-case Diagram (for the whole
1
system)
Scenario (primary and secondary)
For Use Case 1 : [Name the use case]
Scenario (primary and secondary)
For Use Case 2 : [Name the use case]
1
Scenario (primary and secondary)
For Use Case 3 : [Name the use case]
Scenario (primary and secondary)
For Use Case 4 : [Name the use case]
Class Diagram (for the whole system) 1
Sequence Diagram
For Function 1 : [Name the function]
Sequence Diagram
1
For Function 2 : [Name the function]
Sequence Diagram
For Function 3 : [Name the function]
Activity Diagram
For Function 1 : [Name the function]
Activity Diagram
1
For Function 2 : [Name the function]
Activity Diagram
For Function 3 : [Name the function]
State Diagram (If any)
For Object 1 : [Name the object]
System Architecture 1
Total Score 9

2
 FOR INSTRUCTOR’S USE ONLY
PLO [Write student 1’s name] Max. Mark Notes
Mark Obtain
[write YES next your
Table of Contents part] 1
Project Description
Functional Requirements
(user and system requirements)
2
Non-Functional Requirement
(user and system requirements)
Context Diagram with description 1
Use-case Diagram (for the whole
1
system)
Scenario (primary and secondary)
For Use Case 1 : [Name the use case]
Scenario (primary and secondary)
For Use Case 2 : [Name the use case]
1
Scenario (primary and secondary)
For Use Case 3 : [Name the use case]
Scenario (primary and secondary)
For Use Case 4 : [Name the use case]
Class Diagram (for the whole system) 1
Sequence Diagram
For Function 1 : [Name the function]
Sequence Diagram
1
For Function 2 : [Name the function]
Sequence Diagram
For Function 3 : [Name the function]
Activity Diagram
For Function 1 : [Name the function]
Activity Diagram
1
For Function 2 : [Name the function]
Activity Diagram
For Function 3 : [Name the function]
State Diagram (If any)
For Object 1 : [Name the object]
System Architecture 1
Total Score 9

2
 FOR INSTRUCTOR’S USE ONLY
PLO [Write student 1’s name] Max. Mark Notes
Mark Obtain
[write YES next your
Table of Contents part] 1
Project Description
Functional Requirements
(user and system requirements)
2
Non-Functional Requirement
(user and system requirements)
Context Diagram with description 1
Use-case Diagram (for the whole
1
system)
Scenario (primary and secondary)
For Use Case 1 : [Name the use case]
Scenario (primary and secondary)
For Use Case 2 : [Name the use case]
1
Scenario (primary and secondary)
For Use Case 3 : [Name the use case]
Scenario (primary and secondary)
For Use Case 4 : [Name the use case]
Class Diagram (for the whole system) 1
Sequence Diagram
For Function 1 : [Name the function]
Sequence Diagram
1
For Function 2 : [Name the function]
Sequence Diagram
For Function 3 : [Name the function]
Activity Diagram
For Function 1 : [Name the function]
Activity Diagram
1
For Function 2 : [Name the function]
Activity Diagram
For Function 3 : [Name the function]
State Diagram (If any)
For Object 1 : [Name the object]
System Architecture 1
Total Score 9

2
 FOR INSTRUCTOR’S USE ONLY
PLO [Write student 1’s name] Max. Mark Notes
Mark Obtain
[write YES next your
Table of Contents part] 1
Project Description
Functional Requirements
(user and system requirements)
2
Non-Functional Requirement
(user and system requirements)
Context Diagram with description 1
Use-case Diagram (for the whole
1
system)
Scenario (primary and secondary)
For Use Case 1 : [Name the use case]
Scenario (primary and secondary)
For Use Case 2 : [Name the use case]
1
Scenario (primary and secondary)
For Use Case 3 : [Name the use case]
Scenario (primary and secondary)
For Use Case 4 : [Name the use case]
Class Diagram (for the whole system) 1
Sequence Diagram
For Function 1 : [Name the function]
Sequence Diagram
1
For Function 2 : [Name the function]
Sequence Diagram
For Function 3 : [Name the function]
Activity Diagram
For Function 1 : [Name the function]
Activity Diagram
1
For Function 2 : [Name the function]
Activity Diagram
For Function 3 : [Name the function]
State Diagram (If any)
For Object 1 : [Name the object]
System Architecture 1
Total Score 9

2
Contents

1. Chapter 1
System descriptions

Health Bloom system is an easy access application can provide a wide range of electronic
services to all patients, such as request appointments, review vital signs, review lab reports,
including access to medical information's and more.
HealthBloom being integrated with the centralized database allow doctors to look at the patient's
electronic medical record, see the results of the tests and make a new record in a very easy and
comfortable way.
making an appointment at the doctor or seeing the results of the test anywhere and anytime will
encourage the patients to utilize the app for requesting appoints and get notification to better
care. The application supports Arabic and English languages.

The development Process model used

The most appropriate model for a health bloom system is the incremental model. The patient
who uses the system may need some changes or modifications such as changing the appointment
date, canceling the appointment, requesting a new appointment, and the additional form is the
best option from this point. This model is suitable for our application because it generates work
programs quickly and early in the life cycle of the program, and it is also more flexible - less
costly to change scope and requirements. Plus, it's easier to test and debug with smaller
iterations. It also lowers the initial delivery cost. Ultimately, it is easier to manage risk because
hazardous parts are identified and dealt with as they are repeated.

System Requirements
Functional Requirements
User Requirements
1- User registration

The system shall require the user to register to be able to book appointments.

2
2- User verification

Users must confirm their accounts to use the application and book appointments.

3- User information

all users shall be able to view all their lab results, med treatments, and patient histories.

4- Search appointments

A user should be able to conduct a search by providing doctor's name, preferred time, and
appointment type, the result is displayed in a different page by default.

5- Book appointments

Users can book appointments by choosing a doctor from the Appointments page.

6- User support

Users should be able to cancel appointments anytime by contacting Support.

System Requirements
1.1 password recovery

Description: There is a method in the system to help recover the password of a user.

1.2 Home page

Description: The application shall have a home page that lists the purpose of the application.

1.3 Usability requirements

Description: The system offers a graphical interface that is easy to use for the users.

2.1 Email confirmation

Description: The system's job is to send emails to users to confirm their accounts.

3.1 Reporting requirements

Description: The system shall generate a list of patients who are expected to attend appointments
that day for each clinic on a daily basis.

3.2 Patient history

Description: The system shall display patient’s last name as a link to account history.

2
4.1 Modify user appointments

Description: A "Request Appointment" page shall provide a list of the clinics and all the doctors
in the hospital, but this process happens when the user want to change the time of their
appointment or the doctor.

Non-Functional Requirements
1. Usability Requirements

Description: Health Bloom System shall offer a graphical interface that is simple to use, comparable to

other existing systems, so that users do not need to learn a new interaction style.

2. Performance Requirements

Description: Health Bloom System shall be available 24 hours a day, and System should be able to handle
1000 transactions per second.

3. Safety requirement

Description: Health Bloom System shall include restore and recover functions in order to prevent data
loss and ensure data integrity

4. security Requirements

Description: in Health Bloom System the identity shall be at least 10 characters long with a personalized
password containing both letters and numbers for patient privacy.

5. availability Requirements

Description: Health Bloom System shall be available to all clinics during working hours And the
Downtime within normal working hours shall not exceed five seconds in any one day.

6. Portability Requirements

Description: Health Bloom System shall be managed by Internet Explorer, Google Chrome, Mozilla
Firefox, and Safari web browsers.

7. Patient Recognition

Description: The system shall require the individual to acknowledge herself or himself making use of the
phone or authenticate themselves using their health authority identity card.

8. Front Desk staff Rights

Description: Front Desk staff shall be able to view all information in system, add new patients to system
but shall not be able to modify any information in it.

2
9. Modification Requirements

Description: Any modification (insert, delete, update) for the Database shall be synchronized and done
only by the administrator.

2. Chapter 2
Context Diagram

System Use-case Diagram with description

In HealthBloom System patient can login, request appointments by selecting a day and time,
view appointments, view vital signs, lab reports, and get prescription. The system should check if
the user has signed in before he makes any booking. A patient can also cancel his appointment at
any time. Moreover, a patient can modify his appointment by selecting another date and time.
However, the system could display unavailable date/time selected message. A pharmacist can
realize a prescription, get prescription realization. A doctor can add clinic hours, writing a
prescription. Administrator can login, maintain and view resources state, manage system
settings, and register patients with the ability to delete, insert and update. The system should
display all bookings made each day, but only an administrator can view it,

2
2
Use case scenario (Primary +secondary)
Use case 1 [insert a title]
[For each use case in the use case diagram, state the scenario (primary and Secondary)]

Use case 2 [insert a title]

[For each use case in the use case diagram, state the scenario (primary and Secondary)]

Use case 3 [insert a title]

[For each use case in the use case diagram, state the scenario (primary and Secondary)]

Use case 4[insert a title]

[For each use case in the use case diagram, state the scenario (primary and Secondary)]

3. Chapter 3
System Class Diagram
[Draw the class diagram for your system with description (relationship, attributes and methods)]

Sequence Diagrams
Sequence diagram for [insert a title]
[Draw a sequence diagram (at least 3 sequence diagram) and their relationship with use case and
class diagram (as in tutorial)]

Sequence diagram for [insert a title]

[Draw a sequence diagram (at least 3 sequence diagram) and their relationship with use case and
class diagram (as in tutorial)]

Sequence diagram for [insert a title]

[Draw a sequence diagram (at least 3 sequence diagram) and their relationship with use case and
class diagram (as in tutorial)]

4. Chapter 4
Activity Diagram
Activity Diagram for [insert a title]
[Draw an Activity diagram ( for at least 3 functions)]

Activity Diagram for [insert a title]

[Draw an Activity diagram ( for at least 3 functions)]

Activity Diagram for [insert a title]

[Draw an Activity diagram ( for at least 3 functions)]

2
State Diagram
State Diagram for [insert a title]
[Draw a state diagram for one object in your system ( if exist one or more )]

5. Chapter 5
Architecture Diagram
[Draw an Architecture diagrams for your system, and explain the reason behind your choice]