Software
Requirements Specification
Smart medical box
based on robotic developments
1.
Project Scope
The “Smart Medical Box based on Robotic Development”
helps patients to collect their correct dosage of tablets on correct time. There
are Mobile apps to Doctor, Pharmacist and Caretaker.
Doctor checks the patient and prescribes tablets.
Patient handovers the prescription to a pharmacy. Pharmacist inputs
prescription details and labels barcode to each bin. Once the tablets are
filled and the prescription is inputted, the box is handover to the patients.
During the prescribed time, the box makes remainder
alarm. Once the patient placed his/her
palm under the dispenser’s mouth, all the tablets for that specific time will
be dispensed. It will dispense tablets only to the recognized palms. If the
patient failed to place his or her palm on that allocated time, the system will
send remainder message to the patient and caretaker as a final remainder. It will make “Thank You” voice alert to
confirm that all the tablets are dispensed.
Caretakers are facilitated to observe tablets collection of their family
members via the app. If the box got repaired it will notify the caretaker. In
case of emergency there’s an emergency button. This box can be located by GPRS.
At the end of each month, the box is going to automatically fix appointment
with doctor.
All the system information is maintained in cloud
database.
2.
Functional Requirements
2.1. For Mobile Application System:
Priority
Number
|
01
|
Function
Name
|
Unlocking
the Smart Medical Box
|
Description
|
The
pharmacist can only able to unlock the medical box by using mobile
application.
|
Input
|
User
name, password.
Input
type: string ,integer
|
Process
|
The
system will validate the entered user name and the password.
|
Output
|
If
the user name and the password are correct, the Smart Medicine Box will open
to fill the tablets.
Else
we can’t able to unlock it.
Output
type: text
|
Priority
Number
|
02
|
Function
Name
|
Managing
prescription.
|
Description
|
Name
of the medicine, Amount, Schedule, Exact time to remind, Interval details,
Compartment number will be stored to the medical box by the pharmacist.
|
Input
|
Enter
the details.
Input
type: string, integer
|
Process
|
All
details will save in the database and have connection with the programmed
Arduino.
|
Output
|
Voice
alert.
Output
type: sound
|
Priority
Number
|
03
|
Function
Name
|
Maintaining
storage.
|
Description
|
Check
the availability of the medicines in the box.
|
Input
|
Input
type: signal
|
Process
|
By
using IOT, the sensor unit should be able to measure the available medicines.
|
Output
|
Details of the current available medicines.
Output
type: text
|
Priority
Number
|
04
|
Function
Name
|
Tracking
of medicine intake.
|
Description
|
Caretaker
can able to track the in taking medicine of the patient with the help of
mobile application.
|
Input
|
Input
type: image
|
Process
|
Observing
and sending the details to the mobile app.
|
Output
|
Monitoring
the patient’s medication.
Output
type: text
|
2.2. For Smart medicine box system:
Priority
Number
|
01
|
Function
Name
|
Collecting
tablets.
|
Description
|
Robotic
arm of the medicine box should be picked the pills and put them into bin.
|
Input
|
Input
type: time
|
Process
|
With
the help of barcode reader the robotic arm will identify and collect the
correct medicines according to the given prescription.
|
Output
|
Scheduled
medication will be stored into a bin.
Input
type: action
|
Priority
Number
|
02
|
Function
Name
|
Voice
alert.
|
Description
|
Giving
voice alert on correct time of in taking medicine.
|
Input
|
Entered
the correct time of the medicine intake in the mobile application.
Input
type: time
|
Process
|
Real
time clock will check the entered time and the RTC’s time will be same value
or not.
|
Output
|
If
the entered time in the mobile app and the RTC’s time will be same, the box
will give a voice alert.
Else
there will be no response from the box.
Output
type: sound
|
Priority
Number
|
03
|
Function
Name
|
Recognizing
palm and distributing medicine.
|
Description
|
During
the medication time, the patient has to place their palm under the mouth of
the dispenser.
It
will dispense the tablets only to the recognized palm.
|
Input
|
Particular
patient’s palm has already scanned by the system.
Input
type: image
|
Process
|
The
camera will take picture of the palm and analysis whether the taken picture
and the already saved picture of the palm will be same or not.
|
Output
|
If
both pictures will be same, the dispenser will distribute the tablets into
the recognized palm.
Else
the dispenser won’t distribute tablets.
Output
type: action
|
Priority
Number
|
04
|
Function
Name
|
Confirming
intake of medicines.
|
Description
|
After
distribution of medication on the palm, medicine box will give a voice alert
for confirming intake of medicines.
|
Input
|
Input
type: signal
|
Process
|
After
collecting the tablets, the bin will give a vibration. Then only the system
gets to know that the patient collects tablets.
|
Output
|
Voice
alert.
Output
type: sound
|
Priority
Number
|
05
|
Function
Name
|
Giving
remainder alert message.
|
Description
|
If
patient does not take medicine on time, the box will give alert message to
the caretaker and the patient.
|
Input
|
Input
type: signal
|
Process
|
The
sensor will observe the distribution of the tablets.
|
Output
|
Voice
message.
Output
type: sound
|
Priority
Number
|
06
|
Function
Name
|
Disposing
tablets.
|
Description
|
If
there will be no response from the patient, then after 5 minutes those
particular medicines will dispose into another bin.
|
Input
|
Input
type: time
|
Process
|
Collected
tablets get a vibration and move into another bin.
|
Output
|
Dispose
medicines into another bin.
Output
type: action
|
Priority
Number
|
07
|
Function
Name
|
Emergency
alert
|
Description
|
When
press the button on the box which gives alert message to emergency service in
case of emergency.
|
Input
|
Input
type: action
|
Process
|
Making
connection.
|
Output
|
Sending
alert message to ambulance.
Output
type: text
|
Priority
Number
|
08
|
Function
Name
|
Fixing
appointment
|
Description
|
The
box will send a message to doctor to make an appointment in the end of every
month.
|
Input
|
Input
type: signal
|
Process
|
Making
connection.
|
Output
|
Sending
message to the doctor.
Output
type: text
|
Priority
Number
|
09
|
Function
Name
|
Repair
alert message.
|
Description
|
If
the box damaged or repaired, the box will give message to the user.
|
Input
|
Input
type: signal
|
Process
|
Making
connection.
|
Output
|
Give
alert message.
Output
type: text
|
3.
Non-functional
Requirement
3.1.
Non-functional
requirement for mobile app system
3.1.1.
Product Requirement
3.1.1.1.
Usability
Requirement
-
The
system shall be able to provide correct dosage of medicine on correct time
without any error.
3.1.1.2.
Efficiency
requirement
-
The
prescription is inputted by the pharmacist.
-
The
application shall be able to generate a notification. So that the patient can
take required medicine at the proper time.
-
The
system should be able to track the medication intake.
3.1.1.3.
Performance
requirement
-
The
application should be interactive with pharmacist, doctor, caretaker and
patients.
-
The
application will provide the availability of the medicines in the box.
3.1.1.3.1.
Space
requirement
-
The
application should be able to handle large amount of data there are name of the
medicine, Amount (Quantity of intake), Schedule, Exact time to remind, Interval
details and Compartment/bin Number. The details about each activity will be
stored in the local database.
3.1.1.3.2.
Reliability
requirement
-
The
application shall be available 24hours every day.
-
In
case the patient did not collect the prescribed tablet, the system shall
dispense that tablet.
-
The
application will be able to fix appointment with doctor.
-
The
application shall be able to track the in taking medicine of the patient.
3.1.1.4.
Portability
requirement
-
The
application will be user friendly.
-
The
system should be able to be handled from any place with internet facility.
-
The
medical box able to connect with the mobile app.
3.1.2.
Organizational Requirement
3.1.2.1.
Delivery
requirement
-
Pharmacist
is going to set the alert by using mobile app and refill the box. Then he is going
to handover the box to the patient.
3.2.2.1.
Implementation
requirement
-
The
application will be software which is to be implemented on a smart mobile
phone.
-
The
system can be completed within the allocated budget.
3.2.2.2.
Standard
requirement
The
system is developed to the patients it should be developed using proper
considerate.
3.2.3.
External
requirement
3.2.3.1.
Interoperability
requirement
The
system interact with 4 types of users, they are pharmacist, doctor,
caretaker and patients.
3.2.3.2.
Ethical
requirement
-
The
system is user friendly. It is not going to affect the society.
-
All
the information collected from the candidate is kept confidential and won’t be
used again unless the candidate’s wish.
-
The
testing is only to find the dispensing so society is not going to affect by the
wrong medical intake.
3.2.3.3.
Legislative
requirement
The
system shall not disclose any personal information about user when gives the
feedbacks
3.2.
Non-functional
Requirement for medical box system
3.2.1.
Product
Requirement
3.2.1.1.
Usability
Requirement
-
The
system shall be able to provide correct dosage of medicine on correct time
without any error.
3.2.1.2.
Efficiency
requirement
-
The
system shall be able to generate an alert signal and notification. So that the
patient can take required medicine at the proper time.
-
The
system should be able to track the medication intake and stock of medicine.
-
The
system will dispense the tablets only to the recognized palm
3.2.1.3.
Performance
requirements
-
The
system should be interactive with pharmacist, caretaker and patients.
-
If
there is no response from the patient, the system will dispose those particular
medicines into another bin.
3.2.1.3.1.
Space
requirement
-
The
system should be able to handle large amount of data there are name of the
medicine, Amount (Quantity of intake), Schedule, Exact time to remind, Interval
details and Compartment/bin Number. The details about each activity will be
stored in the local database.
3.2.1.3.2.
Reliability
requirement
-
The
system shall be available 24hours every day.
-
The
system should be able to generate voice alert at the prescribed time.
-
After
distribution the system should be able to generate voice alert for confirming
intake of medicine.
-
The
system shall be able to make appointment in the end of every month.
-
In
case of emergency, when the patients press the emergency button the system
would be able to send an emergency alert to the emergency service.
3.2.1.4.
Portability
requirement
-
The
medical box will be user friendly.
-
The
system should be able to be handled from any place and easy to carry.
-
The
medical box able to connect with the mobile app.
3.2.2.
Organizational Requirement
3.2.2.1.
Delivery
requirement
-
Pharmacist
is going to set the alert by using mobile app and refill the box. Then he is
going to handover the box to the patient.
3.2.2.2.
Implementation
requirement
-
The
system will be a box which is interactive with mobile app and user.
-
The
system can be completed within the allocated budget.
3.2.2.3.
Standard
requirement
-
The
system is developed to the patients it should be developed using proper
considerate.
3.2.3.
External
requirement
3.2.3.1.
Interoperability
requirement
-
The
system interact with 4 types of users, they are pharmacist, doctor, caretaker
and patients.
3.2.3.2.
Ethical
requirement
-
The
system is user friendly. It is not going to affect the society.
-
All
the information collected from the candidate is kept confidential and won’t be
used again unless the candidate’s wish.
-
The
testing is only to find the dispensing so society is not going to affect by the
wrong medical intake.
-
The
system shall not disclose any personal information about user when gives the
feedbacks.
3.2.3.3.
Legislative
requirement
3.2.3.3.1.
Privacy
requirement
The
system shall not disclose any personal information about user.
4. Enhanced Entity Relationship Diagram
No comments:
Post a Comment