Mamta SRS Document

COMSATS University Islamabad,
Park Road, Chak Shahzad, Islamabad Pakistan
SOFTWARE REQUIREMENTS
SPECIFICATION
(SRS DOCUMENT)
for
Mamta
Version 1.0
By
Saira Mehmood CIIT/SP16-BCS-008/ISB
Arsam Farooq Ahmed CIIT/SP16-BCS-065/ISB
Khalil Ahmed CIIT/SP16-BCS-076/ISB
Supervisor
Mr. Tehseen Riaz Abbasi
Bachelor of Science in Computer Science (2016-2020)
1
2
Table of Contents
Revision History iii

1. Introduction 1
1.1 Purpose 1
1.2 Scope 1
2. Overall description 1
2.1 Product perspective 1
2.2 Operating environment 1
2.3 Design and implementation constraints 1
3. Requirement identifying technique 2
3.1 Use Case Diagram 2
3.2 Use Case Description 2
4. Specific Requirements 4
4.1 System feature X 4
5. Quality attributes 5
5.1 Usability 6
5.2 Performance 6
6. External interface requirements 6
6.1 User interfaces 6
6.2 Software interfaces 7
6.3 Hardware interfaces 7
6.4 Communications interfaces 7
7. Project Gantt chart 8
8. References 8
3
Revision History
Name Date Reason for changes Version
4
Application Evaluation History
Comments (by committee) Action Taken

*include the ones given at scope time both in doc and
presentation
Supervised by
<Supervisor’s Name>
0Signature_____________
5
1. Introduction
The main purpose of this document is to brief about the requirements of “Mamta” which is developed
primarily for parents so that they can be actively involved in their child’s development and learning
activities. The document includes the diagrams and tabular use cases, functional requirements and the
non-functional requirements.
Parenting is not an easy job as responsibilities seem to change every day. The tasks and roles you
perform daily as a parent are bound to change as your child gets older. This system will help parents to
become more knowledgeable, updated and keep tracks of the precious moments of their child. Its main
focus is on enhancing parenting practices, such as learning age-appropriate child development skills and
developing and practicing positive discipline techniques through modern technology. The system helps a
parent to train for some necessary things (like placing a baby properly) in Augmented Reality. It also
provides milestones to be achieved to help parent keeping the baby on track on developmental cycle.
Furthermore, this system also notify the health situation and monitors the early symptoms of “Sudden
infant death Syndrome” (SIDS), “Anemia” and “Fever” etc. and notifies their parents about any abnormal
health activity through mobile app.
Moreover, it also keep the parents updated about the nutritional requirements of their child from stage to
stage. The system provides an intelligent bot which can answer parent’s F.A.Q about their babies. While,
In case of any health emergency, this system also connects and communicates the guardians with the
relevant online doctors.
1.1.Purpose
Majority of the parents do not have the right knowledge or guidance about their child’s
development, health or nutritional requirements. Children need to be cared for in a way that
promotes their growth both physically and emotionally. Parents are ideal resources for their
children from where they can get positive emotional and physical growth. Because of lack of
awareness in parents about proper child care and growth, many children are unable to meet the
necessary standards of growth and physical development.
According to “Centers for Disease Control” there were almost 1600 kids who died from “Sudden
Infant Syndrome” (SIDS) in 2015 in USA. In SIDS, a child die suddenly usually in their sleep
and no one gets to know or to provide them help until it’s too late already. Similarly according a
research almost 5.6% population of USA has “Anemia” [1]. In Anemia oxygen level in blood
decreases due to lack of haemoglobin. Also, the infants suffer from fever very often. But in some
cases the rise in temperature can cause “Febrile seizures” in babies. Similarly, some parents
don’t know when their baby’s diaper is wet and needs changing and this can cause rashes in
babies. Also, many children miss their vaccinations because some parents don’t know when it is
the right time for their kid to have vaccination for diseases like polio etc.
Moreover parents don’t have a single platform which can answer their common queries
regarding their babies, provide them knowledge in accordance to their baby’s age or inform them
about what to do in emergency situations. Even through every parent wishes best for his/her
6
child but lack of right parental information gets in the way of achieving this.
1.2.Scope
After downloading the application, user will have to sign up for the account through entering
email and password. There are two type of users, parents and doctors. When a parent signs into
the created account for the first time, he/she will then configure the “Health gadget” using
smartphone application.
Parent will be able to see multiple options on the screen. By selecting “Add New Baby” the
parent will be able to set the details of the new born child. The parent can then learn about “how
to take care of the baby” and other necessary trainings in Augmented Reality. The parent would
be given details like how to hold babies head, how to put the baby on bed etc. using augmented
reality. The parent will also be able to view information regarding the baby caring in form of text
and videos. The parent can also mark any of the information as important and set a reminder for
it.
When selecting health monitoring, user (parent) will be able to monitor the health by monitoring
the heart rate, blood oxygen level and temperature of the body any time. The system would also
check if any unusual change in the health monitoring is occurred, the parent will be notified
about it through the mobile application. It also provides status update on diaper status i.e. if it is
wet or not. If it gets wet enough and needs changing it generates an alert to the parent.
The parents can also ask some common questions from the Chat bot. The chatbot can also
provide some home remedies to some of the commonly occurring problems of the kids like
diarrhea etc. The parent will also be able to make an appointment with the doctor, if he/she sees
any change in health of the baby. The parent will also be able to make an audio call to doctor in
case of any emergency. They can also send text message to the doctor regarding the health of the
baby. On weekly basis few milestone would be given to the parent regarding the baby progress..
2.3 Overall description

2.1.Product perspective
Describe the product’s context and origin. Is it the next member of a growing product line, the
next version of a mature system, a replacement for an existing application, or an entirely new
product?
2.2.Operating environment
The environment in which Mumta will operate is given below:

OE-1: The system will operate correctly on android version greater or equal to 4.4 kitKat.
OE-2: The system will operate correctly on any mini Arduino version.
7
2.3.Design and implementation constraints
The design and implementation constraints of Mumta are given below:
CO-1: The system will be using firebase cloud database to save the data.
CO-2: The system will use vuforia AR kit for supporting augmented reality.
CO-3: The system will use sinch call API for audio communication between the parent
and doctor.
CO-4 Node
3.3 Requirement identifying technique

Use case is an effective technique for interactive end-user applications, so Use case is used as a
requirement identifying technique
3.1.Use case diagram
The Use Case Diagrams of the system are given below:
Use Case Diagram SEQ

Use_Case_Diagram \* ARABIC 1 Doctors
8
Use Case Diagram SEQ Use_Case_Diagram \*
ARABIC 2 Parent Module 1 and 2 Diagram
3.2. Use case description

The use case tabular description is given below:
3.2.1. Module 1: Profile Management
UC-1.1: Sign UP
Table 1 Signup Use Case
Use Case ID: UC-1.1

Use Case Signup
Name:
Actors: Primary Actor: Parent, Doctor
Description: Parent will be able to create an account in application.

Trigger: User will click on sign up button.
Preconditions 1. Internet connection is available and working properly.

:
9
Post 1. User account created successfully.
conditions:
Normal Flow: 1. User opens the “Mamta” application.
2. User clicks on “Sign up” button.
3. User enters all the required details.
4. User clicks on the sign up button.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes None
Assumptions: 1. User knows the basic knowledge of using smartphones.
2. User understands English language.
Notes And N/A.

Issues
UC-1.2: Sign In
Table 2: Sign In Use Case
Use Case ID: UC-1.2

Use Case Sign In
Name:
Description: User will be able to access their respective dashboard by logging into their account.
Trigger: User opens the application.

:
Post 1. User is logged into their respective account.

conditions:
Normal Flow: 1. User opens the application.

2. User enters Email and password and select “Parent” Account type.
3. User clicks on Sign in button.
Alternative 2.1. User enters Email and password and select “Doctor” Account type.
Flows:
10
2.2. User clicks on sign in button.
Exceptions: N/A
Business N/A
Rules
Includes UC-1.1

Notes And N/A.
Issues
UC-1.3: Forget password

Table 3: Forget Password Use Case
Use Case ID: UC-1.3

Use Case Forget password
Name:
Description: User can reset their forgotten password by clicking on “Forgot password?”.
Trigger: User clicks on “Forgot password?”

:
Post 1. User’s password reset successfully.

conditions:
Normal Flow: 1. User clicks on “Forgot password?” text.

2. User enters his/her email address to verify their identity.
3. User enters the answers to the security questions.
4. User clicks on “Reset” button.
Alternative N/A
Flows:
Exceptions: N/A
Business 1. Parent must have an account.
Rules
Includes N/A
11
Notes And N/A.

Issues
UC-1.4: Add New Baby

Table 4: Add New Baby Use Case
Use Case ID: UC-1.4

Use Case Add New Baby
Name:
Description: User can add new baby into their same account to manage multiple babies in the same
account.
Trigger: User Clicks on “Add New Baby” Button.

:
Post 1. A new Baby will be added into the account and can be managed from the same
conditions: account.
Normal Flow: 1. User clicks on the “Add new baby” button.

2. User enters the details of the baby.
3. User clicks on “Add” button.
Alternative N/A
Flows:
Exceptions: N/A
Rules 2. Parent must be logged in.
Includes UC-1.2

Notes And N/A.
Issues
UC-1.5: Remove Baby from account
12
Table 5: Remove Baby from account use case
Use Case ID: UC-1.5
Use Case Remove Baby from account

Name:

Description: User would be able to delete added child from the account by clicking “Delete Child
Data” button.
Trigger: User clicks on “Delete Child Data” Button.

: 2. User have already added at least one baby before.
Post 1. Child Data removed from the account successfully.

conditions:
Normal Flow: 1. User selects the child from “Added Babies list”.
2. User clicks on “Delete child Data” button.
3. User selects “Yes” on Dialog box.
Alternative N/A
Flows:
Exceptions: N/A
Business 1. User must have an account.
Rules 2. User must be logged in.
Includes UC-1.2

Notes And N/A.
Issues
UC-1.6: Edit Baby Details

Table 6: Edit Baby Details Use Case
Use Case ID: UC-1.6

Use Case Edit Baby Details
Name:
Description: User will be able to edit already added baby’s details like name and age etc.
13
Trigger: User clicks on “Edit Baby Details” button.
: 2. User have already added at least one baby into their account.
Post 1. Baby’s Details changed successfully.

conditions:
Normal Flow: 1. User selects the child from “Added babies list”.
2. User clicks on Edit Baby Details Button.
3. User changes details.
4. User clicks on “Submit” button.
Alternative N/A
Flows:
Exceptions: N/A
Includes UC-1.2

Notes And N/A.
Issues
UC-1.7: Change Baby Image

Table 7: Change Baby Image Use Case
Use Case ID: UC-1.7
Use Case Change Baby image

Name:

Description: User can change baby’s image by selecting the image from the gallery.
Trigger: User clicks on “Edit baby details” button.

:
Post 1. Image for the corresponding baby is changed in the account.
conditions:
14
Normal Flow: 1. User selects the child from “Added Babies List”.
2. User clicks on “Edit Baby’s Details” button.
3. User clicks browse button and select an image.
4. User clicks on Change image button.
Alternative N/A
Flows:
Exceptions: N/A

Includes UC-1.2
Notes And N/A.

Issues
UC-1.8: Change Password

Table 8: Change Password Use Case
Use Case ID: UC-1.8

Use Case Change Password
Name:
Description: User can change his/her account password if necessary by logging into his/her account.
Trigger: User clicks on settings button.

:
Post 1. User password changed successfully.

conditions:
Normal Flow: 1. User clicks on Settings button.

2. User enters new password and clicks on “Change Password” button.
Alternative N/A
Flows:
Exceptions: N/A
15
Includes UC-1.2

Notes And N/A.
Issues
UC-1.9: Add Health Gadget

Table 9: Add Health Gadget Use Case
Use Case ID: UC-1.9
Use Case Add Health Gadget

Name:

Description: User can add a new health gadget for an added baby in “Added Babies List”. This gadget
will be responsible for tracking the health of the baby.
Trigger: User clicks on Add health gadget button.

: 2. User have already added at least one baby in his/her account.
Post 1. Health gadget would be added for a baby and would start sending sensor’s data
conditions: to the application.
Normal Flow: 1. User selects the baby from the “added babies list”.
2. User click on Health Monitoring.
3. User clicks on Settings
4. User clicks on Add health gadget button.
5. User synchronize the gadget with Bluetooth first time.
Alternative N/A
Flows:
Exceptions: N/A
16
Includes UC-1.2
Notes And N/A.

Issues
UC-1.10: Remove health gadget

Table 10 : Remove Health gadget Use Case
Use Case ID: UC-1.10

Use Case Remove health gadget
Name:
Description: User can remove already added health gadget if they want.
Trigger: User Clicks on “Remove Gadget” button.

: 2. User have already added a gadget into his/her account.
Post 1. Health gadget will be removed from the account.
conditions:
Normal Flow: 1. User selects the baby from “Added babies list”.
2. User clicks on Health Monitoring.
3. User clicks on the settings.
4. User clicks on “remove health gadget” button.
Alternative N/A
Flows:
Exceptions: N/A

Includes UC-1.2
17
Notes And N/A.

Issues
Module 2: Augmented Reality Based Training

UC-2.1: Start Baby head placing training
Table 11: Start Baby head placing training Use Case
Use Case ID: UC-2.1

Use Case Start Baby head placing training
Name:
Actors: Primary Actor: Parent
Description: User will be able to start viewing Head placing training. This will help them
understanding how to place baby’s head properly.
Trigger: User clicks on Head placing training button.

:
Post 2. Baby head placing training started successfully.

conditions:
Normal Flow: User clicks on AR based Training.
User selects Baby Head placing Training.
User clicks on start training button.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2
Notes And N/A.

Issues
UC-2.2: Stop Baby head placing training

18
Table 12: Stop Baby head placing training
Use Case ID: UC-2.2
Use Case Stop Baby head placing training

Name:

Description: User will be able to stop viewing Head placing training. This will stop already running
Head placing training.
Trigger: User clicks on Stop training button.

:
Post 1. Baby head placing training stopped successfully.
conditions:
Normal Flow: 4. User clicks on Stop Training Button.
Alternative N/]A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2,UC-2.1
Notes And N/A.

Issues
UC-2.3: Start Proper Baby Pick up Training

Table 13: Start Proper Baby Pick up Training
Use Case ID: UC-2.3

Use Case Start “Proper Baby Pick up” Training
Name:
Description: User will be able to start viewing “Proper baby pick up” training. This will help them
understanding how to pick up a baby properly.
19
Trigger: User clicks on Proper Baby Pick up training button.

:
Post 1. Baby Proper Picking Training started successfully.

conditions:
Normal Flow: 1. User clicks on AR based Training.
2. User selects Proper Baby Pick up Training.
3. User clicks on start training button.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2
Notes And N/A.

Issues
UC-2.4: Stop Proper Baby Pick up Training

Table 14:Stop Proper Baby Pick up Training Use Case
Use Case ID: UC-2.4

Use Case Stop Proper Baby Pick Up training
Name:
Description: User will be able to stop viewing Proper Baby Pick Up training. This will stop already
running Proper Baby Pick Up training.
Trigger: User clicks on Stop Proper Baby Pick Up training button.

:
Post 2. Baby head placing training stopped successfully.

conditions:
20
Alternative N/]A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2,UC-2.3

Notes And N/A.
Issues
UC-2.5: Start Baby Medicine Giving training

Table 15: Start Baby Medicine giving training
Use Case ID: UC-2.5
Use Case Start Baby Medicine Giving training

Name:

Description: User will be able to start viewing Giving Medicine to Baby training. This will help them
understanding how to place give medicine to a baby in a proper way.
Trigger: User clicks on Giving Medicine Training button.

:
Post 1. Baby Medicine Giving training started successfully.

conditions:
Normal Flow: 1. User clicks on AR based Training.

2. User selects Medicine Giving Training Button.
3. User clicks on start training button.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
21
Includes UC-1.2

Notes And N/A.
Issues
UC-2.6: Stop Medicine Giving Training

Table 16: Stop Medicine Giving Training
Use Case ID: UC-2.6
Use Case Stop Medicine Giving Training

Name:

Description: User will be able to stop viewing Medicine Giving training. This will stop already running
Medicine Giving training.
Trigger: User clicks on Stop Medicine Giving training button.

:
Post 1. Medicine giving training stopped successfully.
conditions:
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2, UC-2.5

Notes And N/A.

Issues
UC-2.7: Zoom In
22
Table 17: Zoom In Use Case
Use Case ID: UC-2.7
Use Case Zoom In (Baby Model)

Name:

Description: User would be able to zoom in during the training. This will make Training model more
zoomed in (looks bigger) than before.
Trigger: User clicks on Zoom in button.

:
Post 1. Training Model zoomed in.

conditions:
Normal Flow: 1. User Selects AR Based training.

2. User starts a training.
3. User clicks on Zoom in Button.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
UC-2.8: Zoom Out

Table 18: Zoom Out Use Case
Use Case ID: UC-2.8
Use Case Zoom Out (Baby Model)

Name:

Description: User would be able to zoom out during the training. This will make Training model
23
Zoomed out (Looks smaller) than before.
Trigger: User clicks on Zoom out button.

:
Post 1. Training Model zoomed out.

conditions:

3. User clicks on Zoom out Button.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
Use Case ID: UC-2.9
Use Case Zoom Out (Baby Model)

Name:

Description: User would be able to zoom out during the training. This will make Training model
Zoomed out (Looks smaller) than before.
Trigger: User clicks on Stop Medicine Giving training button.

:
Post 1. Training Model zoomed out.

conditions:

24
3. User clicks on Zoom out Button.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2
Notes And N/A.

Issues
Module 3: Video and Textual Training

UC-3.1: View newBorn to 3 Month baby Information
Use Case ID: UC-3.1
Use Case Name: View newBorn to 3 Month baby Information
Description: User selects the options of View newBorn to 3 Month Baby, after that the parent can check
the information about what the parent should do, what the baby should be given
Trigger: User will click on View Food Information from Video and Textual training menu.
Preconditions: 1. Parent is logged into Mumta Application.

2. A Parent Should be registered.
Post conditions: Selecting View newBorn to 3 Month baby Information would result in displaying the details
of about what the parent should do, what the baby should be given.
Normal Flow: 1. User selects newBorn to 3 Month baby from Video and Textual training menu.
2. “Mumta” Application then displays the details of what the parents should do and what
the baby should be given to eat.
Alternative None
Flows:
Exceptions: None
Business Rules N/A
25
Includes UC-1.2
Assumptions: 1. User knows the basic knowledge of android phone usage.

Notes And N/A.

Issues
UC-3.2: View 3 month to 6 months baby Information
Use Case ID: UC-3.2
Use Case Name: View 3 month to 6 months baby Information
Description: User selects the options of View 3 month to 6 months Baby, after that the parent can check the
information about what the parent should do, what the baby should be given

Post conditions: Selecting View 3 month to 6 months baby Information would result in displaying the details
Normal Flow: 3. User selects 3 month to 6 months baby from Video and Textual training menu.
4. “Mumta” Application then displays the details of what the parents should do and what
the baby should be given to eat.
Alternative None
Flows:
Exceptions: None
Business Rules N/A
Includes UC-1.2

Notes And N/A.

Issues
UC-3.3: View 6 months to 9 months baby Information
Use Case ID: UC-3.3
Use Case Name: View 6 months to 9 months baby Information
26
Description: User selects the options of View 6 months to 9 months Baby, after that the parent can check

Post conditions: Selecting View 6 months to 9 months baby Information would result in displaying the details
Normal Flow: 5. User selects 6 months to 9 months baby from Video and Textual training menu.
6. “Mumta” Application then displays the details of what the parents should do and what the
baby should be given to eat.
Alternative None
Flows:
Exceptions: None
Business Rules N/A
Includes UC-1.2

Notes And N/A.

Issues
UC-3.4: View 9 months to 12 months baby Information

Use Case ID: UC-3.4
Use Case Name: View 9 months to 12 months baby Information
Description: User selects the options of View 9 months to 12 months Baby, after that the parent can check

Post conditions: Selecting View 9 months to 12 months baby Information would result in displaying the details
27
Normal Flow: 7. User selects 9 months to 12 months baby from Video and Textual training menu.
8. “Mumta” Application then displays the details of what the parents should do and what the
baby should be given to eat.
Alternative None
Flows:
Exceptions: None
Business Rules N/A
Includes UC-1.2

Notes And N/A.

Issues
UC-3.5: View Common Disease Symptoms

Use Case ID: UC-3.5
Use Case View Common Disease Symptoms

Name:
Description: User selects the options of View Common Disease Symptoms, after that the parent can
check the common Disease symptoms of newly born babies..
Trigger: User will click on View Common Disease Symptoms from Video and Textual training
menu.
Preconditions: Parent is logged into Mumta Application.
A Parent Should be registered.

Post Selecting View Common Disease Symptoms would result in displaying the common
conditions: disease symptoms of newly born babies.
Normal Flow: User selects the View Common Disease Symptoms from Video and Textual training
menu.
“Mumta” Application then displays the common disease symptoms of newly born
babies.
Alternative None
28
Flows:
Exceptions: None
Business Rules Use cases and business rules are intertwined. Some business rules constrain which roles
can perform all or parts of a use case. Perhaps only users who have certain privilege
levels can perform specific alternative flows. That is, the rule might impose
preconditions that the system must test before letting the user proceed. Business rules
can influence specific steps in the normal flow by defining valid input values or dictating
how computations are to be performed e.g.
BR-1 Delivery time windows are 15 minutes, beginning on each quarter hour.
BR-2 Deliveries must be completed between 11:00 A.M. and 2:00 P.M. local time,
inclusive.
Note: If you are maintaining the business rule in a separate table in SRS then only
mention here their IDs.
Includes UC-1.2
Assumptions: User knows the basic knowledge of android phone usage.
User understands English language.
Notes And N/A.

Issues
UC-3.6: Add Information

Use Case ID: UC-3.6
Use Case Add Information
Name:

Description: User selects the options of Add Information, after that the parent can add any
information she finds useful for the baby.
Trigger: User will click on Add Information from Video and Textual training menu.
29
Post Selecting Add Information would result in can adding any information she finds useful
conditions: for the baby.
Normal Flow: User selects the Add Information from Video and Textual training menu.
Parent can then add any information she/he finds useful for the baby.
Alternative None
Flows:
Exceptions: None
Business Rules Use cases and business rules are intertwined. Some business rules coNnstrain which
roles can perform all or parts of a use case. Perhaps only users who have certain
privilege levels can perform specific alternative flows. That is, the rule might impose
inclusive.
Includes UC-1.2
Notes And N/A.

Issues
UC-3.7: Mark Important

Use Case ID: UC-3.7
Use Case Mark Important
Name:
30
Description: User selects the options of Mark Important, after that the parent can mark all the
marked information she thinks is important.
Trigger: User will click on Mark Important from Video and Textual training menu.
Post Selecting View Mark Important would result in displaying the marked information she
conditions: thinks is important.
Normal Flow: User selects the Mark Important option from Video and Textual training menu.
“Mumta” Application then displays all the marked information by the parent .
Alternative None
Flows:
Exceptions: None
inclusive.
Includes UC-1.2

Notes And N/A.
Issues
31
UC-3.8: View Marked Information
Use Case ID: UC-3.8
Use Case View Marked Information

Name:
Description: User selects the options of View Information, after that the parent can view the
previously added or important marked information
Trigger: User will click on View Information from Video and Textual training menu.

Post Selecting View Information would result in displaying the previously added or important
conditions: marked information
Normal Flow: User selects the View Information option from Video and Textual training menu.
“Mumta” Application then displays all the previously added or important marked
information.
Alternative None
Flows:
Exceptions: None
Business Rules Use cases and business rules are intertwined. Some business rules constrain which roles
can perform all or parts of a use case. Perhaps only users who have certain privilege
levels can perform specific alternative flows. That is, the rule might impose
inclusive.
32
Includes UC-1.2

Notes And N/A.
Issues
UC-3.9: View Diaper changing video

Use Case ID: UC-3.9
Use Case View Diaper changing video

Name:
Description: User selects the options of View Diaper changing video, after that the parent will be
able to see the video showing how to change the diaper of the children.
Trigger: User will click on View Diaper changing video and Textual training menu.

Post Selecting View Diaper changing video would result in displaying the video which shows
conditions: how to change the diaper of the children.
Normal Flow: User selects the View Diaper changing video from Video and Textual training menu.
“Mumta” Application then displays the video which shows how to change the diaper of
the children..
Alternative None
Flows:
Exceptions: None
33
inclusive.
Includes UC-1.2
Notes And N/A.

Issues
Module 4: Health Monitoring

UC-4.1:View Current Heart Rate
Use Case ID: UC-4.1
Use Case View Current Heart Rate
Name:
Actors: Primary Actor: Parent Secondary Actor: “Mumta” Application , Arduino
Description: User will be able to view the current Heartrate of the baby by tapping the Current
heartrate button. So that the user is aware about the current health situation of the
baby.
Trigger: User will click on Current Heartrate Button.
Preconditions 3. Hardware is attached with the baby’s body.

: 4. Internet service is available.
Post 3. Current Heartrate of the baby is displayed.
conditions:
Normal Flow: User selects the Current Heartrate Button.
“Mumta” Application then sends the request to the Arduino.
“Arduino” then fetches the values from the sensor attached to the baby’s body
After fetching the value the Arduino calculates the heartrate and return the value.
“Mumta” Application then displays the heartrate.
Alternative N/A
34
Flows:
Exceptions: N/A

Includes UC-1.2
Notes And N/A.

Issues
UC-4.2: View Current Body Temperature

Use Case ID: UC-4.2
Use Case View Current Body Temperature
Name:
Description: User will be able to view the current Body Temperature of the baby by tapping the
Current Body Temperature button. So that the user is aware about the current health
situation of the baby.
Trigger: User will click on Current Body Temperature Button.

Post 2. Current Body Temperature of the baby is displayed.
conditions:
Normal Flow: 6. User selects the Current Body Temperature Button.
7. “Mumta” Application then sends the request to the Arduino.
8. “Arduino” then fetches the values from the sensor attached to the baby’s body
9. After fetching the value the Arduino calculates the Body temperature and
return the value.
10. “Mumta” Application then displays the Body Temperature.
Alternative N/A
Flows:
Exceptions: N/A
35
Includes UC-1.2

Notes And N/A.
Issues
UC-4.3: View Current Blood Oxygen Level

Use Case ID: UC-4.3
Use Case View Current Blood Oxygen Level

Name:

Description: User will be able to view the current Blood Oxygen Level of the baby by tapping the
Current Blood Oxygen level button. So that the user is aware about the current health
situation of the baby.
Trigger: User will click on Current Body Temperature Button.

Post 2. Current Body Temperature of the baby is displayed.

conditions:
Normal Flow: 5. User selects the Current Blood Oxygen Level Button.
7. “Arduino” then fetches the values from the sensor attached to the baby’s body
8. After fetching the value the Arduino calculates the Blood Oxygen Level and
returns the value.
9. “Mumta” Application then displays the Blood Oxygen Level.
Alternative N/A
Flows:
Exceptions: N/A
Includes UC-1.2
36
Notes And N/A.

Issues
UC-4.4: View Current Diaper Moisture Level

Use Case ID: UC-4.4
Use Case View Current Diaper Moisture level
Name:
Description: User will be able to view the current Moisture Level of the diaper by tapping the
Current Diaper Moisture level button. So that the user is aware about when to change
the diaper of the baby.
Trigger: User will click on Current Moisture Level.
Preconditions 2. Hardware is attached with the diaper worn by baby.

Post 2. Current Moisture Level would be displayed with reference to the max moisture
conditions: allowed.
Normal Flow: 4. User selects the Current Diaper Moisture Level Button.
6. “Arduino” then fetches the values from the sensor attached to the diaper worn
by the baby.
7. After fetching the value the Arduino calculates the Current Moisture Level of
the Diaper and returns the value.
8. “Mumta” Application then displays the Current Moisture Level of the Diaper.
Alternative N/A
Flows:
Exceptions: N/A
Includes UC-1.2

37
Notes And N/A.
Issues
UC-4.5: Disable Heartrate sensor

Use Case ID: UC-4.5
Use Case Disable Heartrate sensor

Name:

Description: User will be able to Disable Heartrate Sensor by tapping the Disable Heartrate Sensor.
So that the user can save the battery and disable the sensor when it is not needed.
Trigger: User will click on Disable Heartrate Sensor.

Preconditions 3. Internet service is available.
:
Post 2. The heartrate sensor would stop sending data.
conditions: 3. “Enable Heartrate Sensor” button would enabled.
Normal Flow: 4. User selects the Disable Heartrate Sensor Button.

6. “Arduino” then disables the heartrate sensor.
Alternative N/A
Flows:
Exceptions: N/A
5. Heartrate Sensor should be enabled before setting it to disable mode
Includes UC-1.2
Notes And N/A.

Issues
UC-4.6: Disable Body Temperature Sensor

Use Case ID: UC-4.6
Use Case Disable Body Temperature sensor
38
Name:

Description: User will be able to Disable Body Temperature Sensor by tapping the Disable Body
Temperature Sensor. So that the user can save the battery and disable the sensor when
it is not needed.
Trigger: User will click on Disable Body Temperature sensor.

:
conditions: 3. “Enable Body Temperature Sensor” button would enabled.
Normal Flow: 5. User selects the Disable Body temperature Sensor Button.
7. “Arduino” then disables the Body Temperature sensor.
Alternative N/A
Flows:
Exceptions: N/A
5. Body temperature Sensor should be enabled before setting it to disable mode
Includes UC-1.2
Notes And N/A.

Issues
UC-4.7: Disable Oxygen Level Sensor

Use Case ID: UC-4.7
Use Case Disable Oxygen Level sensor
Name:
Description: User will be able to Disable Blood Oxygen Level Sensor by tapping the Disable Blood
Oxygen level Sensor. So that the user can save the battery and disable the sensor when
it is not needed.
39
Trigger: User will click on Disable Oxygen Level sensor.

:
Post 2. The Oxygen level sensor would stop sending data.

conditions: 3. “Enable Blood Oxygen Level Sensor” button would enabled.
Normal Flow: 5. User selects the Disable Blood Oxygen Level Sensor Button.
7. “Arduino” then disables the Blood Oxygen Level sensor.
Alternative N/A
Flows:
Exceptions: N/A

5. Blood Oxygen Level Sensor should be enabled before setting it to the disable
mode
Includes UC-1.2
Notes And N/A.

Issues
UC-4.8: Disable Diaper Moisture Level Sensor

Use Case ID: UC-4.8
Use Case Disable Diaper Moisture Level sensor
Name:
Description: User will be able to disable diaper moisture level sensor by tapping the “disable diaper
moisture level sensor”. So that the user can save the battery and disable the sensor
when it is not needed.
Trigger: User will click on Disable diaper moisture level sensor.

:
Post 2. The diaper moisture level sensor would stop sending data.
conditions: 3. “Enable Diaper Moisture Level Sensor” button would enabled.
40
Normal Flow: 3. User selects the Diaper Moisture Level Sensor Button.
5. “Arduino” then disables the Diaper Moisture Level sensor.
Alternative N/A
Flows:
Exceptions: N/A

5. Diaper Moisture Level Sensor should be enabled before setting it to the disable
mode
Includes UC-1.2
Notes And N/A.

Issues
UC-4.9: Enable Heartrate Sensor

Use Case ID: UC-4.9
Use Case Enable Heartrate sensor
Name:
Actors: Primary Actor: Parent Secondary Actor: Application , Arduino
Description: User will be able to Enable Heartrate Sensor by tapping the Enable Heartrate Sensor. So
that the user can get the heartrate readings.
Trigger: User will click on Enable Heartrate Sensor.

: 5. User must be logged in.
6. Heartrate Sensor should be disabled before setting it to enable mode
Post 4. The heartrate sensor would start sending data.

conditions: 5. “Enable Heartrate Sensor” button would disabled.
Normal Flow: 7. User selects the Enable Heartrate Sensor Button.
9. “Arduino” then enables the heartrate sensor.
10. “Arduino” then start getting the readings from the sensor.
Alternative N/A
Flows:
41
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
UC-4.10: Enable Body Temperature Sensor

Use Case Enable Body Temperature sensor

Name:

Description: User will be able to Enable Body Temperature Sensor by tapping the Enable Body
Temperature Sensor. So that the user can get the Body temperature readings..
Trigger: User will click on Enable Body Temperature sensor.

8. Body temperature Sensor should be disabled before setting it to enable mode

conditions: 5. “Enable Body Temperature Sensor” button would be disabled.
Normal Flow: 8. User selects the Enable Body temperature Sensor Button.
10. “Arduino” then enables the Body Temperature sensor.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2
42
Notes And N/A.

Issues
UC-4.11: Enable Oxygen Level Sensor

Use Case Enable Oxygen Level sensor
Name:
Description: User will be able to Enable Blood Oxygen Level Sensor by tapping the Enable Blood
Oxygen level Sensor. So that the user can get the Oxygen Level readings.
Trigger: User will click on Enable Oxygen Level sensor.

5. Blood Oxygen Level Sensor should be disabled before setting it to the enable
mode
Post 4. The Oxygen level sensor would start sending data.

conditions: 5. “Enable Blood Oxygen Level Sensor” button would disabled.
Normal Flow: 8. User selects the Enable Blood Oxygen Level Sensor Button.
10. “Arduino” then enables the Blood Oxygen Level sensor.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2
Notes And N/A.

Issues
43
UC-4.12: Enable Diaper Moisture Level sensor
Use Case Enable Diaper Moisture Level sensor

Name:

Description: User will be able to enable diaper moisture level sensor by tapping the “enable diaper
moisture level sensor”. So that the user can get the Diaper Moisture readings.
Trigger: User will click on Enable diaper moisture level sensor.

: 4. Parent must be logged in.
5. Diaper Moisture Level Sensor should be disabled before setting it to the enable
mode
Post 4. The diaper moisture level sensor would start sending data.
conditions: 5. “Enable Diaper Moisture Level Sensor” button would be disabled.
Normal Flow: 6. User selects the Diaper Moisture Level Sensor Button.
8. “Arduino” then enables the Diaper Moisture Level sensor.
Alternative N/A
Flows:
Exceptions: N/A
Business 6.
Rules
Includes UC-1.2

Notes And N/A.
Issues
UC-4.13: Add Medicine Details

Use Case Add Medicine Details

Name:
Actors: Primary Actor: Parent Secondary Actor: “Mumta” Application
44
Description: User will be able to add the details of the medicine like medicine name, medicine intake
quantity, medicine intake time. So that the user remembers when and what medicine is
to be given to the baby.
Trigger: User will click on Add New Medicine.

:
Post 2. Details of the Medicine would be saved.

conditions:
Normal Flow: 6. User selects the Add Medicine Details Option.

7. User then enters medicine name.
8. User then enters medicine in take quantity.
9. User then enters medicine in take time.
10. User Presses save button.
11. “Mumta” Applications saves all details of the medicine.
Alternative Step 4a : If user wants to enter more than one medicine in take time then
Flows:
1. Press the “add another time” button.
2. Repeat step 4 of normal flow.
3. Go to step 5 of normal flow.
Exceptions: Step 2a : if user enters the medicine with same name then
1. “Mumta” Application displays an error message “ Medicine already added”

5. Two medicine with same name cannot be entered.
6. Medicine intake time must be entered.
Includes UC-1.2

Notes And N/A.
Issues
UC-4.14: View Medicine Details

45
Use Case View Medicine Details
Name:
Description: User will be able to View the details of all the added medicine.
Trigger: User will click on View Medicine.

: 4. At least one Medicine Detail is already added
Post 2. Details of All the added Medicine would be displayed.
conditions:
Normal Flow: 5. User selects the View Medicine Details.
6. “Mumta” Application then fetches all the medicines and there details.
7. “Mumta” Application then displays all the medicines and there details.
Alternative N/A
Flows:
Exceptions: N/A

Includes UC-1.2
Notes And N/A.

Issues
UC-4.15: Edit Medicine Details

Use Case Edit Medicine Details
Name:
Description: User will be able to Edit the details of a selected Medicine. So that the details of any
medicine can be edited if needed.
Trigger: User will click on Add New Medicine.
Preconditions 1. Details of All medicines are displayed.
46
:
Post 1. Details of the selected medicine would be edited and saved.

conditions:
Normal Flow: 1. User selects the One of the enlisted medicine.

2. “Mumta” Application then displays all the details of that medicine.
3. User then edits the specific detail which user wants to edit.
4. User then presses save.
5. “Mumta” Application then validates the intake time.
6. “Mumta” Application then saves details.
Alternative N/A
Flows:
Exceptions: Step 5a : if the intake time is empty then:
1. “Mumta” application displays the error “Please the intake time”

3. Medicine in take Time must be entered.
Includes UC-4.14
Notes And N/A.

Issues
UC-4.16: Delete Medicine

Use Case Delete Medicine
Name:
Description: User will be able to Delete the details of a selected Medicine. So that the Medicines
details which are not in use can be deleted.
Trigger: User will click on Delete Medicine.
Preconditions 1. Details of All medicines are displayed.

:
47
Post 1. The selected Medicine would be delete.
conditions:
Normal Flow: 1. User selects the One of the enlisted medicine.
2. “Mumta” Application then displays all the details of that medicine.
3. User presses the delete button.
4. “Mumta” Application then asks the user for confirmation.
5. “Mumta” Application then deletes the selected medicine.
Alternative Step 4a : if the user selects cancel option then:

Flows:
1. “Mumta” application will than not delete the Medicine.
Exceptions: N/A

Includes UC-4.14
Notes And N/A.

Issues
Module 5: AI chat Bot and FAQ

Use Case ID: UC-5.1
Use Case Do Greetings
Name:
Description: User selects the options Ask FAQs, after that the parent Views a chat window.
User will then type a greetings. And then the AI bot will reply back with a
greeting.
Trigger: User will click on Ask FAQS from Main Menu.
Preconditions 1. Internet Service is available.
: 2. Parent must be logged into the Application.
Post 1. Application will reply to the greetings of the users.
conditions:
Normal Flow: 1. User selects the ASK FAQS from Main Menu.
48
2. User then types in the greetings Message.
3. Application then checks if the typed message is a greetings message.
4. Application then responds to the users greetings with a greetings reply.
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not a greetings
message then
1. Application would reply with a message “cannot get you”.
Business N/A.
Rules
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-5.2

Use Case Ask Fever Home Remedy
Name:
Description: User types in the message that asks for the Fever Home Remedy. So that the
user can apply the early home remedies to the baby.
Trigger: User will click on Send Message.
Post 1. Application will reply to the user’s message in which he asks about the
conditions: fever remedy.
Normal Flow: 1. User then types in the Message asking about fever remedy.
2. Application then checks if the typed message is a fever remedy.
3. Application then responds to the user’s message with the remedy of the
fever.
Alternative N/A
49
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not a fever remedy
message or any other message that the AI chat Bot does not know how to
respond.
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
Issues
Use Case ID: UC-5.3

Use Case Ask Fever Symptoms
Name:
Description: User types in the message that asks for the Fever Symptoms. So that the user
can check if the baby has the fever or not.
conditions: fever Symptoms.
Normal Flow: 1. User then types in the Message asking about fever symptoms in baby.
2. Application then checks if the typed message is about fever symptoms.
3. Application then responds to the user’s message with the symptoms of
the fever.
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not a fever
50
symptom message or any other message that the AI chat Bot does not know
how to respond.
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
Issues
Use Case ID: UC-5.4

Use Case Ask Fever Causes
Name:
Description: User types in the message that asks for the Fever Causes. So that the user can
remove the causes of the fever, so that next time baby remains in good health.
conditions: fever causes.
Normal Flow: 1. User then types in the Message asking about fever causes.
2. Application then checks if the typed message is a fever causes.
3. Application then responds to the user’s message with the causes of the
fever.
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not a fever cause
respond.
51
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
Issues
Use Case ID: UC-5.5

Use Case Ask Anemia Home Remedy
Name:
Description: User types in the message that asks for the Anemia Home Remedy. So that the
conditions: Anemia remedy.
Normal Flow: 1. User then types in the Message asking about Anemia remedy.
2. Application then checks if the typed message is an Anemia remedy.
Anemia.
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not a Anemia
remedy message or any other message that the AI chat Bot does not know how
to respond.
Business N/A.
Rules
Includes UC-5.1
52
Notes And N/A.
Issues
Use Case ID: UC-5.6

Use Case Ask Anemia Symptoms
Name:
Description: User types in the message that asks for the Anemia Symptoms. So that the user
conditions: Anemia Symptoms.
Normal Flow: 1. User then types in the Message asking about Anemia symptoms in baby.
2. Application then checks if the typed message is about Anemia symptoms.
the Anemia
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not an Anemia
how to respond.
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
53
Issues
Use Case ID: UC-5.7

Use Case Ask Anemia Causes
Name:
Description: User types in the message that asks for the Anemia Causes. So that the user can
remove the causes of the Anemia, and the baby remains in good health.
conditions: Anemia causes.
Normal Flow: 1. User then types in the Message asking about Anemia causes.
2. Application then checks if the typed message is a Anemia causes.
Anemia.
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not a Anemia cause
respond.
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
Issues
54
Use Case ID: UC-5.8
Use Case Ask Sudden child death syndrome Home Remedy
Name:

Description: User types in the message that asks for the Sudden child death syndrome Home
Remedy. So that the user can apply the early home remedies to the baby.
conditions: sudden child death syndrome remedy.
Normal Flow: 1. User then types in the Message asking about sudden child death
syndrome remedy.
2. Application then checks if the typed message is a sudden child death
syndrome remedy.
sudden child death syndrome.
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not a Sudden child
death syndrome remedy message or any other message that the AI chat Bot
does not know how to respond.
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
Issues
55
Use Case ID: UC-5.9
Use Case Ask Sudden child death syndrome Symptoms
Name:

Description: User types in the message that asks for the Sudden child death syndrome
Symptoms. So that the user can check if the baby has the fever or not.
conditions: sudden child death syndrome Symptoms.
syndrome symptoms in baby.
2. Application then checks if the typed message is about sudden child death
syndrome symptoms.
the Sudden child death syndrome
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not an sudden child
death syndrome symptom message or any other message that the AI chat Bot
does not know how to respond.
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
Issues
56
Use Case Ask Sudden child death syndrome Causes
Name:
Description: User types in the message that asks for the Sudden child death syndrome
Causes. So that the user can remove the causes of the Sudden child death
syndrome, and the baby remains in good health.
conditions: sudden child death syndrome causes.
syndrome causes.
2. Application then checks if the typed message is a sudden child death
syndrome causes.
sudden child death syndrome.
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not a sudden child
death syndrome cause message or any other message that the AI chat Bot does
not know how to respond.
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
Issues

Use Case Ask Diarrhea Home Remedy
57
Name:

Description: User types in the message that asks for the diarrhea Home Remedy. So that the
conditions: diarrhea remedy.
Normal Flow: 1. User then types in the Message asking about diarrhea remedy.
2. Application then checks if the typed message is a diarrhea remedy.
diarrhea.
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not a Diarrhea
remedy message or any other message that the AI chat Bot does not know how
to respond.
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
Issues

Use Case Ask Diarrhea Symptoms
Name:
Description: User types in the message that asks for the Diarrhea Symptoms. So that the user
58
conditions: diarrhea Symptoms.
Normal Flow: 1. User then types in the Message asking about diarrhea symptoms in baby.
2. Application then checks if the typed message is about diarrhea
symptoms.
the diarrhea.
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not an diarrhea
how to respond.
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
Issues

Use Case Ask Diarrhea Causes
Name:
Description: User types in the message that asks for the Diarrhea Causes. So that the user can
remove the causes of the Sudden child death syndrome, and the baby remains
in good health.
59
conditions: diarrhea causes.
Normal Flow: 1. User then types in the Message asking about diarrhea causes.
2. Application then checks if the typed message is a diarrhea causes.
diarrhea.
Alternative N/A
Flows:
Exceptions: Step 3a: In step 3 of the normal flow if the typed message is not a diarrhea
cause message or any other message that the AI chat Bot does not know how to
respond.
Business N/A.
Rules
Includes UC-5.1
Notes And N/A.
Issues
Module 6: Consult your Doctor

Use Case ID: UC-6.1
Use Case View Near By Doctors
Name:

Description: User selects the options of View Near By Doctors, after that the parent Views
the List of all Doctors which are in the same city as of the parent. And then
Select One Doctor for Consultation.
60
Trigger: User will click on View nearby Doctors from Doctor Consultation Menu.
: 4. Parent must be logged into Mumta Application.
5. A Doctor Should be registered.
Post 2. Selecting One Doctor would result in Displaying Details of the specific
conditions: Doctor.
Normal Flow: 5. User selects the View nearby Doctors from Doctor Consultation Menu.
6. “Mumta” Application then fetches the current Location of the Parent.
7. “Mumta” Application then displays the list of doctors which are in the
same city as of Parent.
8. User Selects one of the Doctor from the given List
3. 5. “Mumta” Application Displays the Details of the Selected Doctor.
Alternative Step 2a. In step 2 of the normal flow, if there is no location Permission then.
Flows: 1. Application Requests for the Location Permission.
2. User selects the option of “allow” for location Permission.
Exceptions: Step 2a: In step 2 of the normal flow if the location is not fetched then
2. Application would display an error “Location not fetched”.
Business 1. Validate that Doctor and Parent are from same city.
Rules
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-6.2

Use Case Send Request
Name:
61
Description: User would be able to send a Request to the doctor so that chat and audio calls
can be done.
Trigger: User will click on Send Request.
Preconditions 1. Internet Services is available.
: 2. Parent must be logged into Mumta Application.
3. A Doctor Should be registered.
Post 1. A request Would be sent to the Selected Doctor
conditions: 2. The status of the request would be set as pending.
Normal Flow: 1. User Clicks on Send Request.
2. The status of the Request is displayed as Pending.
Alternative Step 1a. In step 1 of the normal flow, if the request is already sent.
Flows: 1. The user will click cancel Request.
2. The status of the request would be set as not sent.
Exceptions: N/A
Business 1. Validate that Doctor and Parent are from same city.
Rules
Includes UC-6.1
Notes And N/A.
Issues
Use Case ID: UC-6.3

Use Case View Pending Request
Name:
Actors: Primary Actor: Doctor
Description: User selects the option of Pending Requests, after that the Doctor Views the List
of all the pending requests which are sent to the doctor.
Trigger: User will click on Pending Request button.
Preconditions 1. Doctor is logged onto Mumta Application.
:
Post 1. List of All the pending requests are displayed to the Doctor
conditions:
62
Normal Flow: 1. User selects the Pending Requests from Doctors Menu.
2. “Mumta” Application then fetches all the requests that are sent to the
doctor and are pending.
3. “Mumta” Application then displays the list of the Requests that are sent
to the doctor and are pending.
Alternative Step 2a: In step 2 of the normal flow if there is no request pending then
Flows:
1. Application would display a message “No requests pending”.
Exceptions: N/A.
Business N/A
Rules
Includes UC-6.2
Notes And N/A.
Issues
Use Case ID: UC-6.4

Use Case Accept/Reject Pending Request
Name:
:
conditions:
Normal Flow: User selects the Pending Requests from Doctors Menu.
“Mumta” Application then fetches all the requests that are sent to the doctor
and are pending.
“Mumta” Application then displays the list of the Requests that are sent to the
63
Flows: 1. Application would display a message “No requests pending”.
Exceptions: N/A.
Business 1. User can accept or decline request
Rules
Includes UC-6.2
Notes And N/A.
Issues
Use Case ID: UC-6.5

Use Case View Added Doctors
Name:
:
conditions:
Flows:
Exceptions: N/A.
64
Rules
Includes UC-6.2
Notes And N/A.
Issues
Use Case ID: UC-6.6

Use Case Send Message
Name:

Description: User selects the option of Post Question, after that the Doctor Views the List of
all the pending requests which are sent to the doctor.
:
conditions:
Flows:
Exceptions: N/A.
Rules
Includes UC-6.2
65
Notes And N/A.
Issues
Use Case ID: UC-6.6

Use Case Make Appointment
Name:
:
conditions:
Flows:
Exceptions: N/A.
Rules
Includes UC-6.2
Notes And N/A.
Issues
66
Use Case ID: UC-6.7
Use Case Call doctor
Name:

:
conditions:
Flows:
Exceptions: N/A.
Rules
Includes UC-6.2
Notes And N/A.
Issues
Use Case ID: UC-6.8
67
Use Case Post Question
Name:
Description: User selects the option of Post Questions, after that the User Types in the
Questions that the user wants to ask and clicks the button post. Then the
question gets visible to all the parents and the Doctors.
Trigger: User will click on Questions button.
Preconditions 1. Internet services are available
: 2. User is logged into the Application.
Post 1. The Questions the user wants to ask gets posted and gets visible to other
conditions: users.
Normal Flow: 1. User types in the Question he wants to ask from other users.
2. User then clicks the send button.
3. Application then saves the post.
4. Application then makes the post visible to all the other users.
Alternative N/A.
Flows:
Exceptions: N/A.
Business N/A
Rules
Includes UC-6.2
Notes And N/A.
Issues
Use Case ID: UC-6.9

Use Case View Questions in Past Month.
Name:
68
Description: User selects the option of View Past Questions, then the user gets past
questions that were posted in the past month.
:
Post 1. List of All the Questions posted by the other users are displayed.
conditions:
Normal Flow: 1. User selects the Option view Past Questions.
2. Application then fetches all the Past Questions in the recent month.
3. Application then displays the list all the Past Questions in the recent
month.
Alternative N/A.
Flows:
Exceptions: N/A.
Business N/A.
Rules
Includes UC-6.2
Notes And N/A.
Issues

Use Case Comment on Post
Name:
Actors: Primary Actor: Parents
Description: User types the answer to the question in the post. And then press the comment
button so that the question posted by the other user is answered.
Trigger: User will click on Comment button.
: 2. Doctor is logged into the Application.
69
Post 1. The Answer to the posted question is commented.
conditions:
Normal Flow: 1. User types the answer to the question posted.
2. Application then saves the response.
3. Application then makes the response visible to all the other users.
Alternative N/A
Flows:
Exceptions: N/A.
Business N/A
Rules
Includes UC-6.9
Notes And N/A.
Issues

Use Case View Own Posts
Name:
Description: User selects the option of View my posts. The user is then able to see the posts
and the comments on his recent posts.
Trigger: User will click on my posts.
Preconditions 1. Internet Services are available
: 2. Doctor is logged onto Mumta Application.
Post 1. The past posts of the users and the comments on that post are displayed.
conditions:
Normal Flow: 1. User presses the button my posts.
2. Application then fetches all the posts done by the user and the
70
comments on that post.
3. Application then displays the past post and the comments on that posts.
Alternative Step 2a: In step 2 of the normal flow if there is no past post then
Flows:
1. Application would display a message “No recent post”.
Exceptions: N/A.
Rules
Includes UC-6.2
Notes And N/A.
Issues

Use Case Delete your Post
Name:
Actors: Primary Actor: Parent.
Description: User will be able to delete the post he has selected. So that he can delete the
post of which he has got the answer.
Trigger: User will click on Delete Button.
Post 1. The selected post is deleted.
conditions:
Normal Flow: 1. User selects the post he wants to delete.
2. Application then shows the option of delete.
3. User then selects the delete option.
4. Application then deletes the selected Post. And is no longer visible to the
other users.
Alternative N/A.*
Flows:
71
Exceptions: N/A.
Rules
Includes UC-6.11
Notes And N/A.
Issues

Use Case Search a Question
Name:

Description: User types in the Question he wants to search. So that he can find if any other
user has posted that question.
Trigger: User will click on Search button.
Post 1. Posts would be displayed containing the question searched by the user.
conditions:
Normal Flow: 1. User types the question he wants to search.

2. Application then fetches all the recent post.
3. Application then check if any of the recent post has the same question.
4. Application then displays the post containing the same question.
Alternative Step 4a: In step 4 of the normal flow if there is no same post found then.
Flows:
1. Application would display a message “No post found”.
Exceptions: N/A.
Rules
Includes UC-6.2
72
Notes And N/A.
Issues
Module 7: Age Based MileStones

Use Case ID: UC-7.1
Use Case Baby Cry Milestone
Name:
Description: User selects the options of Baby Cry Milestone , after that the system will show
the details of cry milestone of baby in 1st week and parent can mark it done if
achieved.
Trigger: User will click on Baby Cry Milestone from Age based Milestones .
Preconditions 6. Parent is logged into Application.
: 7. A Parent Should be registered.
Post 4. Selecting Baby Cry Milestone would result in displaying cry milestone of
conditions: baby in first week.
5. In case of achieving the milestone , parent will mark it done
Normal Flow: 1. User selects the Baby Cry Milestone from Age based Milestones
2. This application then displays the details of cry milestone of baby in 1st
week
3. User will mark it done if achieved.
Alternative None
Flows:
Exceptions: None
Business Use cases and business rules are intertwined. Some business rules coNnstrain
Rules which roles can perform all or parts of a use case. Perhaps only users who have
certain privilege levels can perform specific alternative flows. That is, the rule
might impose preconditions that the system must test before letting the user
proceed. Business rules can influence specific steps in the normal flow by
defining valid input values or dictating how computations are to be performed
e.g.
73
BR-2 Deliveries must be completed between 11:00 A.M. and 2:00 P.M. local
time, inclusive.
Note: If you are maintaining the business rule in a separate table in SRS then
only mention here their IDs.
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-7.2

Use Case Baby Follow Object Milestone
Name:
Description: User selects the options of Baby Follow Object Milestone, after that the system
will show “follow object milestone” in 1st week and parent can mark it done if
achieved
Preconditions 8. Parent is logged into Mumta Application.
Post 6. Selecting “Baby Follow Object Milestone” would result in displaying the
conditions: details of follow object milestone of baby in first week.
7. In case of achieving the milestone, parent will mark it done .
Normal Flow: 9. User selects the Baby Cry Milestone from Age based Milestones
10. This Application then displays the details of follow object milestone of
baby in first week.
74
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-7.3

Use Case Polio Vaccination
Name:

Description: User selects the options of Polio Vaccination, after that the system will show
polio vaccination milestone of baby.
Trigger: User will click on Polio Vaccination from Age based Milestones .
75
Post 1. Selecting Polio Vaccination would result in displaying polio
conditions: vaccination milestone of baby.
2. In case of achieving the milestone , parent will mark it done.
Normal Flow: 1. User selects the Polio Vaccination from Age based Milestones
2. This Application then displays the details of polio vaccination
milestone of baby.
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
76
Use Case ID: UC-7.4
Use Case Hep-B
Name:

Description: User selects the options of Polio Vaccination, after that the system will show
Hep-B vaccination milestone of baby.
Trigger: User will click on Hep-B Vaccination from Age based Milestones .
Post 3. Selecting Hep-B Vaccination would result in displaying Hep-B
conditions: vaccination milestone of baby.
4. In case of achieving the milestone , parent will mark it done.
Normal Flow: 4. User selects the Hep-b Vaccination from Age based Milestones
5. This Application then displays the details of Hep-B vaccination
milestone of baby.
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
77
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-7.5

Use Case Erythromycin Vaccination
Name:

Description: User selects the options of Erythromycin Vaccination, after that the system will
show Erythromycin vaccination milestone of baby.
Trigger: User will click on Erythromycin Vaccination from Age based Milestones .
Post 5. Selecting Erythromycin Vaccination would result in displaying
conditions: Erythromycin vaccination milestone of baby.
6. In case of achieving the milestone, parent will mark it done.
Normal Flow: 7. User selects the Erythromycin Vaccination from Age based
Milestones
8. This Application then displays the details of Erythromycin vaccination
milestone of baby.
Alternative None
Flows:
Exceptions: None
78
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-7.6

Use Case Share Milestone
Name:

Description: User selects the options of Share Milestone, after that the parent can share the
milestones with friends and family.
79
Post 1. Selecting Share Milestone would result in sharing of the milestones
conditions: with friends and family.
Normal Flow: 1. User selects the Share Milestone from Age based Milestones Menu.
2. This Application then will then show sharing options.
3. User will select one option.
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
Includes UC-1.
Notes And N/A.
Issues
80
Use Case ID: UC-7.7
Use Case Baby Speaking Milestone
Name:

Description: User selects the options of Baby Speaking Milestone , after that the system will
show the details of Speaking milestone of baby in 1st week and parent can
mark it done if achieved.
Trigger: User will click on Baby Speaking Milestone from Age based Milestones .
Post 1. Selecting Baby Speaking Milestone would result in displaying Speaking
conditions: milestone of baby in first week.
Normal Flow: 1. User selects the Baby Speaking Milestone from Age based Milestones
2. This application then displays the details of Speaking milestone of baby
in 1st week
Alternative None
Flows:
Exceptions: None
81
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-7.8

Use Case Baby Crawling Milestone
Name:

Description: User selects the options of Baby Crawling Milestone, after that the system will
show the details of Crawling milestone of baby in 1st week and parent can mark
it done if achieved.
Trigger: User will click on Baby Crawling Milestone from Age based Milestones.
Post 3. Selecting Baby Crawling Milestone would result in displaying Crawling
82
Normal Flow: 4. User selects the Baby Crawling Milestone from Age based Milestones
5. This application then displays the details of Crawling milestone of baby
in 1st week
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
83
Use Case ID: UC-7.9
Use Case First word Milestone
Name:

Description: User selects the options of First word Milestone, after that the system will show
the details of First word milestone of baby in 1st week and parent can mark it
done if achieved.
Trigger: User will click on First word Milestone from Age based Milestones .
Post 1. Selecting First word Milestone would result in displaying first word
conditions: Milestone of baby in first week.
Normal Flow: 7. User selects the First word Milestone from Age based Milestones
8. This application then displays the details of first word Milestone of baby
in 1st week
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
84
Includes UC-1.2
Notes And N/A.
Issues

Use Case First step Milestone
Name:
Description: User selects the options of First step Milestone, after that the system will show
the details of First step milestone of baby in 1st week and parent can mark it
done if achieved.
Trigger: User will click on First step Milestone from Age based Milestones .
Post 3. Selecting First step Milestone would result in displaying first step
Normal Flow: 10. User selects the First step Milestone from Age based Milestones
11. This application then displays the details of First step Milestone of baby
in 1st week
Alternative None
Flows:
Exceptions: None
85
Business Use cases and business rules are intertwined. Some business rules constrain
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Module 8: Notification Generation

Use Case ID: UC-8.1
Use Case Abnormal Heart Rate Notification
Name:
Actors: Primary Actor: Mamta Application

Description: When the heart rate fluctuate from the set range of 110 to 170 beats per minute
then Abnormal Heart Rate notification will be generated .
Trigger: Fluctuation in value of heart rate from normal range will trigger Abnormal Heart
Rate Notification .
:
86
Post 8. A notification showing Abnormal Heart Rate will be shown on the screen
conditions:
Normal Flow: 4. Data is fetched from heart rate sensors .
5. Deviated data from normal range is received .
6. Notification of Abnormal Heart Rate is generated
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-8.2
87
Use Case Abnormal Body Temperature Notification
Name:
Description: When the body temperature fluctuate from the set range of 97 to 100.3
degrees Fahrenheit then Abnormal Body Temperature notification will be
generated .
Trigger: Fluctuation in value of Body Temperature from normal range will trigger
Abnormal Body Temperature Notification .
:
Post 1. A notification showing Abnormal Body Temperature will be shown on

conditions: the screen
Normal Flow: 1. Data is fetched from Body Temperature sensors .
3. Notification of Abnormal Body Temperature is generated
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
88
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-8.3

Use Case Abnormal Blood oxygen level Notification
Name:

Description: When the oxygen level fluctuate from the set range then Abnormal Blood
oxygen level notification will be generated .
Trigger: Fluctuation in Blood oxygen level from normal range will trigger Abnormal Blood
oxygen level Notification .
:
Post 1. A notification showing Abnormal Blood oxygen level will be shown on

conditions: the screen
Normal Flow: 1. Data is fetched from Blood oxygen level measuring sensors.
3. Notification of Abnormal Blood oxygen level is generated
Alternative None
Flows:
Exceptions: None
e.g.
89
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-8.4

Use Case Accepted Appointment Notification
Name:
Description: When the requested appointment application is accepted then Accepted
Appointment Notification is generated
Trigger: The requested appointment application is accepted.
:
Post 1. A notification showing Accepted Appointment will be shown on the

conditions: screen
Normal Flow: 1. Requested appointment application is accepted.
2. Notification of Accepted Appointment is generated .
Alternative None
Flows:
Exceptions: None
90
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-8.5

Use Case Rejected Appointment Notification
Name:
Description: When the requested appointment application is rejected then Rejected
Appointment Notification is generated
Trigger: The requested appointment application is rejected
:
Post 1. A notification showing Rejected Appointment will be shown on the

conditions: screen
91
Normal Flow: 1. Requested appointment application is rejected.
2. Notification of Rejected Appointment is generated .
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-8.6

Use Case Diaper change Notification
Name:
92
Description: When the moisture level deviated from the set range then Diaper change
notification will be generated .
Trigger: Fluctuation in value of moisture level of diaper from normal range will trigger
Diaper change notification
:
Post 1. A notification showing Diaper change will be shown on the screen

conditions:
Normal Flow: 1. Data is fetched from moisture level measuring sensors .

3. Notification of Diaper change is generated .
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
Includes UC-1.2
93
Notes And N/A.
Issues
Use Case ID: UC-8.7

Use Case Medicine Timing Notification
Name:
Description: System generate Medicine Timing Notification when it’s time to take medicine .
Trigger: When it’s time to take medicine then it triggers to generate Medicine Timing
Notification.
:
Post 1. A notification showing Medicine Timing will be shown on the screen

conditions:
Normal Flow: 1. Time to take medicine is reached .

2. Notification of Medicine Timing is generated.
Alternative None
Flows:
Exceptions: None
94
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-8.8

Use Case Vaccination period Notification
Name:

Description: System generate Vaccination period Notification when it’s time to take
vaccination .
Trigger: When it’s time to take vaccination then it triggers to generate Vaccination
period Notification.
:
Post 1. A notification showing Vaccination period will be shown on the screen

conditions:
95
Normal Flow: 1. Time to take vaccination is reached .
2. Notification of Vaccination period is generated.
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Use Case ID: UC-8.9

Use Case Pending chat request notification
Name:
Description: When the user send request for chat to the doctor then Pending chat request
Notification is generated and send to the doctor whether to accept or reject it.
96
Trigger: Send chat Request to the doctor triggers to generate Pending chat request
notification.
:
Post 1. A notification showing Pending chat request will be shown on the

conditions: screen
Normal Flow: 1. The user sends request for chat to the doctor.
2. Notification of Pending chat request is generated .
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
97
Use Case Approved chat request notification
Name:

Description: When the user send request for chat to the doctor then Approved chat request
Notification is generated when the doctor accepts it.
Trigger: Accepting chat Request by the doctor triggers to generate Approved chat
request notification.
:
Post 1. A notification showing Approved chat request will be shown on the

conditions: screen
2. The doctor accepts the chat request.
3. Notification of Approved chat request is generated .
Alternative None
Flows:
Exceptions: None
e.g.
time, inclusive.
98
Includes UC-1.2
Notes And N/A.
Issues

Use Case Rejected chat request notification
Name:
Description: When the user send request for chat to the doctor then Rejected chat request
Notification is generated when the doctor rejected it.
Trigger: Rejecting chat Request by the doctor triggers to generate Rejected chat request
notification.
:
Post 1. A notification showing Rejected Approved chat request will be

conditions: shown on the screen
2. The doctor rejects the chat request.
3. Notification of Rejected chat request is generated .
Alternative None
Flows:
Exceptions: None
99
e.g.
time, inclusive.
Includes UC-1.2
Notes And N/A.
Issues
Module 9: User Guidance

Use Case ID: UC-9.1
Use Case Device Configuration (settings) guidance

Name:

Description: User will be able to see guidance on how to configure their device properly. This guide
will help them in doing proper settings required for proper functioning of the
application.
Trigger: User clicks on Device Configuration Guidance button.

:
Post 5. Device Configuration guidance shown to the user on the screen.

conditions:
100
Normal Flow: 10.User clicks on User Guidance Tab.
11.User is displayed with a list of guides.
12.User selects Device Configuration Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
Use Case ID: UC-9.2
Use Case Synchronizing Hardware

Name:

application.
Trigger: User clicks on Synchronizing Hardware Guidance button.

:
Post 6. Synchronizing Hardware guidance shown to the user on the screen.

conditions:

15.User selects Synchronizing Hardware Guide.
Alternative N/A
Flows:
101
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2
Notes And N/A.

Issues
Use Case ID: UC-9.3

Use Case Adding a New Baby Guidance
Name:
application.
Trigger: User clicks on Adding a New Baby Guidance button.

:
Post 7. Adding a New Baby guidance shown to the user on the screen.
conditions:
18.User selects adding a New Baby Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
102
Issues
Use Case ID: UC-9.4

Use Case Deleting a baby's Data Guidance
Name:
application.
Trigger: User clicks on Deleting a baby’s Data Guidance button.

:
Post 8. Deleting a baby’s Data guidance shown to the user on the screen.
conditions:
21.User selects deleting a baby’s Data Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
Use Case ID: UC-9.5
Use Case Checking Milestones Guidance

Name:
103
application.
Trigger: User clicks on Checking Milestones Guidance button.

:
Post 9. Checking Milestones guidance shown to the user on the screen.

conditions:
24.User selects Checking Milestones Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
Use Case ID: UC-9.6
Use Case Using F.A.Q Bot Guidance

Name:

application.
Trigger: User clicks on Using F.A.Q Bot Guidance button.
104
:
Post 10. Using F.A.Q Bot guidance shown to the user on the screen.
conditions:

27.User selects Using F.A.Q Bot Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2
Notes And N/A.

Issues
Use Case ID: UC-9.6

Use Case Milestones Marking Guidance
Name:
application.
Trigger: User clicks on Milestones Marking Guidance button.

:
Post 11. Milestones marking guidance shown to the user on the screen.
conditions:
105
30.User selects Milestones Marking Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
Use Case ID: UC-9.7
Use Case Editing a Baby’s Details Guidance

Name:

application.
Trigger: User clicks on Editing a Baby’s Details Guidance button.

:
Post 12. Editing a Baby’s Details guidance shown to the user on the screen.
conditions:

33.User selects editing a Baby’s Details Guide.
106
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
Use Case ID: UC-9.8
Use Case Messaging a doctor Guidance

Name:

application.
Trigger: User clicks on Messaging a doctor Guidance button.

:
Post 13. Messaging a doctor guidance shown to the user on the screen.
conditions:

36.User selects messaging a doctor Guide.
Alternative N/A
Flows:
Exceptions: N/A
107
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
Use Case ID: UC-9.9
Use Case Calling a doctor Guidance

Name:

application.
Trigger: User clicks on Calling a doctor Guidance button.

:
Post 14. Calling a doctor guidance shown to the user on the screen.
conditions:

39.User selects calling a doctor Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2
108
Notes And N/A.

Issues

Use Case Attaching Health Gadget to a baby Guidance
Name:
application.
Trigger: User clicks on Attaching Health Gadget to a baby Guidance button.

:
Post 15. Attaching Health Gadget to a baby guidance shown to the user on the screen.
conditions:
42.User selects Attaching Health Gadget to a baby Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
109
Use Case Removing health gadget from baby Guidance
Name:
application.
Trigger: User clicks on Removing health gadget from baby Guidance button.

:
Post 16. Removing health gadget from baby guidance shown to the user on the screen.
conditions:
45.User selects Removing health gadget from baby Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
Use Case Synchronizing Attached hardware Guidance

Name:

110
application.
Trigger: User clicks on Synchronizing Attached hardware Guidance button.

:
Post 17. Synchronizing Attached hardware guidance shown to the user on the screen.
conditions:

48.User selects Synchronizing Attached hardware Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2
Notes And N/A.

Issues

Use Case Recharging Health Gadget Guidance
Name:
application.
Trigger: User clicks on Recharging Health Gadget Guidance button.
111
:
Post 18. Recharging Health Gadget guidance shown to the user on the screen.
conditions:

51.User selects Recharging Health Gadget Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2
Notes And N/A.

Issues

Use Case Attaching smart diaper device Guidance
Name:
application.
Trigger: User clicks on Attaching smart diaper device Guidance button.

:
Post 19. Attaching smart diaper device guidance shown to the user on the screen.
conditions:
112
54.User selects Attaching smart diaper device Guide.
Alternative N/A
Flows:
Exceptions: N/A
Business N/A
Rules
Includes UC-1.2

Notes And N/A.
Issues
4. Functional Requirements
The Functional Requirements of the proposed system are as follows:
Functional Requirement
Identifier VFI-3.1.1
Title View Food Information
Requirement User press the button to view food information
Source Parent
Rationale To view the details
Business Rule (if This button must be pressed to view the details .
required)
Dependencies no
Priority Medium
Usecase 3.2
113
Identifier VCDS-3.2.1
Title View Common Disease Symptoms
Requirement User press the button to view common disease symptoms
Source Parent
Business Rule (if This button must be pressed to view the details .
required)
Dependencies no
Priority Medium
Usecase 3.3
Identifier AI-3.3.1
Title Add Information
Requirement User press the button to add information
Source Parent
Business Rule (if This button must be pressed to add information
required)
Dependencies no
Priority Medium
Identifier AI-3.3.2
Title Enter Information
Requirement User will enter the information
Source Parent
Rationale To add the information
Business Rule (if This text field must be full filled to send message.
required)
114
Dependencies no
Priority Medium
Identifier AI-3.3.3
Title Save Information
Requirement User press the button to save information
Source Parent
Rationale To save the information
Business Rule (if This button must be pressed to save the information .
required)
Dependencies no
Priority high
Usecase 3.4
Identifier MI-3.4.1
Title Mark Important
Requirement User press the button to mark important
Source Parent
Rationale To mark the important details
Business Rule (if This button must be pressed to mark the important information .
required)
Dependencies no
Priority Medium
Usecase 3.5
Identifier VI-3.5.1
Title View Information
Requirement User press the button to view information
115
Source Parent
Business Rule (if This button must be pressed to view the information .
required)
Dependencies no
Priority Medium
Usecase 3.6
Identifier VDCV-3.6.1
Title View Diaper changing video
Requirement User press the button to view diaper changing video
Source Parent
Rationale To view the diaper changing video
Business Rule (if This button must be pressed to view Diaper changing video.
required)
Dependencies no
Priority Medium
Usecase: 7.1 Baby Cry Milestone
Identifier BCM-7.1.1
Title Baby Cry Milestone
Requirement User will click on Baby Cry Milestone option
Source parent
Rationale To display details of cry milestone of baby in first week.
Business Rule (if
required)
Dependencies no
Priority high
116
Title Mark done
Requirement User will click on mark done
Source parent
Rationale To mark the milestone done.
Business Rule (if

required)
Dependencies no
Priority high
Usecase 7.2
Baby Follow Object Milestone
Title Baby Follow Object Milestone
Requirement User will click on Baby Follow Object Milestone option
Source parent
Rationale To display details of follow object milestone of baby in
first week.
Business Rule (if
required)
Dependencies no
Priority high
Title Mark done
Source parent
117
Business Rule (if

required)
Dependencies no
Priority high
Usecase 7.3
Title Baby Follow Object Milestone
Requirement User will click on Baby Follow Object Milestone option
Source parent
Rationale To display details of follow object milestone of baby in
first week.
Business Rule (if
required)
Dependencies no
Priority high
Title Mark done
Source parent
Business Rule (if

required)
Dependencies no
Priority high
118
USECASE 7.4
Identifier PV-7.4.1
Title Polio Vaccination
Requirement User will click on Polio Vaccination option
Source parent
Rationale To show polio vaccination milestone of baby.
Business Rule (if
required)
Dependencies no
Priority high
Title Mark done
Source parent
Business Rule (if

required)
Dependencies no
Priority high
USECASE 7.5
Identifier PV-7.5.1
Title Hep-B
Requirement User will click on Hep-B option
Source parent
119
Rationale To show Hep-B vaccination milestone of baby.
Business Rule (if
required)
Dependencies no
Priority high
Title Mark done
Source parent
Business Rule (if

required)
Dependencies no
Priority high
USECASE 7.6
Identifier PV-7.6.1
Title Erythromycin Vaccination
Requirement User will click on Erythromycin Vaccination option
Source parent
Rationale To show Erythromycin vaccination milestone of baby.
Business Rule (if
required)
Dependencies no
Priority high
120
Title Mark done
Source parent
Business Rule (if

required)
Dependencies no
Priority high
USECASE 7.6
Identifier PV-7.6.1
Title Share Milestone
Requirement User will click on Share Milestone button
Source parent
Rationale To share milestones of baby.
Business Rule (if
required)
Dependencies no
Priority high
Title Share to facebook
Requirement User will click on Share to facebook button
Source parent
Rationale To share milestones of baby on facebook.
121
Business Rule (if
required)
Dependencies no
Priority high
Title Share to Instagram
Requirement User will click on Share to Instagram button
Source parent
Rationale To share milestones of baby on Instagram.
Business Rule (if
required)
Dependencies no
Priority high
Usecase 7.7
Identifier BSM-7.7.1
Title Baby Speaking Milestone
Requirement User will click on Baby Speaking Milestone option
Source parent
Rationale To display details Baby Speaking Milestone in first week.
Business Rule (if
required)
Dependencies no
Priority high
Identifier BSM-7.7.2
Title Mark done
122
Source parent
Business Rule (if

required)
Dependencies no
Priority high
Usecase 7.8
Title Baby Crawling Milestone
Requirement User will click on Baby Crawling Milestone option
Source parent
Rationale To display details Baby Crawling Milestone in first week.
Business Rule (if
required)
Dependencies no
Priority high
Title Mark done
Source parent
Business Rule (if

required)
Dependencies no
Priority high
123
Usecase 7.9
Identifier FWM-7.9.1
Title First word Milestone
Requirement User will click on First word Milestone option
Source parent
Rationale To display details First word Milestone in first week.
Business Rule (if
required)
Dependencies no
Priority high
Identifier FWM -7.9.2

Title Mark done
Source parent
Business Rule (if

required)
Dependencies no
Priority high
Usecase : 8.1
Abnormal Heart Rate Notification
Identifier AHRN-8.
Title Abnormal Heart Rate Notification
Requirement System will send notification to parent when the heart
rate fluctuate from the set range of 110 to 170 beats per
minute
124
Source System
Rationale To alert about the fluctuation in heart rate
Business Rule (if This notification must be send to alert about the
required) fluctuation in heart rate
Dependencies no
Priority high
Usecase 8.2
Identifier ABTN-8.2.1
Title Abnormal Body Temperature Notification
Requirement System will send notification to parent when the body
temperature fluctuate from the set range of 97 to 100.3
degrees Fahrenheit
Source System
Rationale To alert about the fluctuation in body temperature
required) fluctuation in body temperature
Dependencies no
Priority high
USECASE 8.3
Title Abnormal Blood oxygen level Notification
Requirement System will send notification to parent when the body
temperature fluctuate from the set range of 97 to 100.3
degrees Fahrenheit
Source System
Rationale To alert about the fluctuation in body temperature
125
Dependencies no
Priority high
Usecase 8.4
Identfier AAN-8.4.1
Title Accepted Appointment Notification
Requirement System will send notification to parent when the
requested appointment application is accepted
Source System
Rationale To aware about the accepted appointment to parent.
Dependencies no
Priority high
Usecase : 8.5
Identifier RAN-8.5.2
Title Rejected Appointment Notification
Requirement System will send notification to parent when the
requested appointment application is rejected
Source System
Rationale To aware about the rejected appointment to parent.
Business Rule (if This notification must be sent to aware about the rejected
required) appointment to parent.
Dependencies no
Priority high
Usecase 8.6
Title Diaper change Notification
126
Requirement System will send notification to parent when the moisture
level of baby’s diaper is deviated from the set range.
Source System
Rationale To alert about the baby’s diaper high moisture level.
Business Rule (if This notification must be send to alert about the baby’s
required) diaper high moisture level.
Dependencies no
Priority high
Usecase 8.7
Identifier MTN-8.7.1
Title Medicine Timing Notification
Requirement System will send Medicine Timing notification to parent
when it’s time to take medicine
Source System
Rationale To alert about medicine time.
Business Rule (if This notification must be send to alert about the medicine
required) time
Dependencies no
Priority high
Usecase 8.8
Identifier VPN-8.8.1
Title Vaccination period Notification
Requirement System will send Vaccination period Notification to parent
when it’s time to take vaccination
Source System
Rationale To alert about vaccination taking time .
127
Business Rule (if This notification must be send to alert about vaccination
required) taking time .
Dependencies no
Priority high
USECASE 8.9
Identifier PCRN-8.9.1
Title Pending chat request notification
Requirement System will send Pending chat request Notification to
doctor whether to accept or reject the chat request .
Source System
Rationale To aware doctor about the chat request
Business Rule (if This notification must be send to aware doctor about the
required) chat request.
Dependencies no
Priority high
Usecase 8.10
Identifier ACRN-8.10.1
Title Approved chat request notification
Requirement System will send Approved chat request Notification to
parent when doctor to accept the chat request .
Source System
Rationale To aware parent about the acceptance of chat request
from doctor.
Business Rule (if This notification must be send to aware parent about the
required) acceptance of chat request from doctor.
128
Dependencies no
Priority high
Usecase 8.11
Identifier ACRN-8.11.1
Title Rejected chat request notification
Requirement System will send Approved chat request Notification to
parent when doctor to rejects the chat request .
Source System
Rationale To aware parent about the rejection of chat request from
doctor.
Business Rule (if This notification must be send to aware parent about the
required) rejection of chat request from doctor.
Dependencies no
Priority high
Table 1: Functional Requirement of Request Current Heart Rate

Identifier FR-4.1.1
Title Request Current Heart Rate
Requirement Parent will be able to press the button of “Health Monitoring” and
the request for the current Heart Rate would be sent.
Source Parent
Rationale Parent must be able to get the current Heart Rate of the baby.
Business Rule (if N/A
required)
Dependencies 4.1.2
Priority High
Table 1: Functional Requirement of View Current Heart Rate
Identifier FR-4.1.2
Title View Current Heart Rate
129
Requirement Parent will be able to view the current heart rate of the baby after
the data is fetched.
Source Parent
Rationale Parent must be able to View the current Heart Rate of the baby.
required)
Dependencies N/A
Priority High
Table 1: Functional Requirement of Request Current Body Temperature

Identifier FR-4.2.1
Title Request Current Body Temperature
the request for the current Body Temperature would be sent.
Source Parent
Rationale Parent must be able to get the current Body Temperature of the
baby.
required)
Dependencies 4.2.2
Priority High
Table 1: Functional Requirement of View Current Body Temperature

Identifier FR-4.2.2
Title View Current Body Temperature
Requirement Parent will be able to view the current body temperature of the baby
after the data from the sensor is fetched.
Source Parent
Rationale Parent must be able to View the current body temperature of the
baby.
required)
130
Dependencies N/A
Priority High
Table 1: Functional Requirement of Request Current Blood Oxygen level

Identifier FR-4.3.1
Title Request Current Blood Oxygen level
the request for the current Blood Oxygen level would be sent to the
aurdino.
Source Parent
Rationale Parent must be able to get the current Blood Oxygen level of the
baby.
required)
Dependencies 4.3.2
Priority High
Table 1: Functional Requirement of View Current Blood Oxygen level

Identifier FR-4.3.2
Title View Current Blood Oxygen level
Requirement Parent will be able to view the current Blood Oxygen level of the
baby after the data from the sensor is fetched.
Source Parent
Rationale Parent must be able to View the current Blood Oxygen level of the
baby.
required)
Dependencies N/A
Priority High
Table 1: Functional Requirement of Request Current Diaper Moisture level

Identifier FR-4.4.1
131
Title Request Current Diaper Moisture level
the request for the current Diaper Moisture level would be sent to
the Arduino.
Source Parent
Rationale Parent must be able to get the current Diaper Moisture level of the
baby.
required)
Dependencies 4.4.2
Priority High
Table 1: Functional Requirement of View Current Diaper Moisture level

Identifier FR-4.4.2
Title View Current Diaper moisture level
Requirement Parent will be able to view the current Diaper moisture level of the
baby after the data from the sensor is fetched.
Source Parent
Rationale Parent must be able to View the current Diaper moisture level of the
baby.
required)
Dependencies N/A
Priority High

Identifier FR-4.5.1
Title Disable Heart Rate sensor
Requirement Parent will be able to press the button of “Disable Heart Rate
Sensor” and the data from the heart rate sensor would be stopped.
Source Parent
132
Rationale Parent must be able to disable the sensor if there is no need or if he
wants to save the battery.
required)
Dependencies 4.5.2
Priority High

Identifier FR-4.5.2
Title Show Sensor Disabled Message
Requirement Parent will be able to view Message of “ Heart Rate Sensor Disabled”
Source Parent
Rationale Parent must be able to View the message if the sensor is disabled.
required)
Dependencies N/A
Priority Medium

Identifier FR-4.5.3
Title Enable “Heart Rate Sensor Enable Button”
Requirement Button for Enabling Heart Rate Sensor would be enabled
Source Parent
Rationale Parent must be able to view the button of “Enable Heart Rate
Sensor”.
required)
Dependencies N/A
Priority Medium
133
Identifier FR-4.6.1
Title Disable Body Temperature sensor
Requirement Parent will be able to press the button of “Disable Body Temperature
Sensor” and the data from the Body Temperature sensor would be
stopped.
Source Parent
required)
Dependencies 4.6.2, 4.6.3
Priority High

Identifier FR-4.6.2
Requirement Parent will be able to view Message of “ Body Temperature Sensor
Disabled”
Source Parent
required)
Dependencies N/A
Priority Medium

Identifier FR-4.6.3
Title Enable “Body Temperature Sensor Enable Button”
Requirement Button for Enabling Body Temperature Sensor would be enabled
Source Parent
Rationale Parent must be able to view the button of “Enable Body
134
Temperature Sensor”.
required)
Dependencies N/A
Priority Medium

Identifier FR-4.7.1
Title Disable Blood Oxygen Level sensor
Requirement Parent will be able to press the button of “Disable Blood Oxygen
Level Sensor” and the data from the Blood Oxygen Level sensor
would be stopped.
Source Parent
required)
Priority High

Identifier FR-4.7.2
Requirement Parent will be able to view Message of “ Blood Oxygen Level Sensor
Disabled”
Source Parent
required)
Dependencies N/A
135
Priority Medium

Identifier FR-4.7.3
Title Enable “Blood Oxygen Level Sensor Enable Button”
Requirement Button for Enabling Blood Oxygen Level Sensor would be enabled
Source Parent
Rationale Parent must be able to view the button of “Enable Blood Oxygen
Level Sensor”.
required)
Dependencies N/A
Priority Medium

Identifier FR-4.8.1
Title Disable Diaper Moisture Level sensor
Requirement Parent will be able to press the button of “Disable Diaper Moisture
Level Sensor” and the data from the Diaper Moisture Level sensor
would be stopped.
Source Parent
required)
Priority High

Identifier FR-4.8.2
136
Requirement Parent will be able to view Message of “ Diaper Moisture Level
Sensor Disabled”
Source Parent
required)
Dependencies N/A
Priority Medium

Identifier FR-4.8.3
Title Enable “Diaper Moisture Level Sensor Enable Button”
Requirement Button for Enabling Diaper Moisture Level Sensor would be enabled
Source Parent
Rationale Parent must be able to view the button of “Enable Diaper Moisture
Level Sensor”.
required)
Dependencies N/A
Identifier FR-4.9.1
Title Enable Heart Rate sensor
Requirement Parent will be able to press the button of “Enable Heart Rate Sensor”
and then the data from the Heart Rate sensor would be sent to the
application.
Source Parent
Rationale Parent must be able to Enable the sensor so that the user can check
the Heart Rate of the baby.
required)
Dependencies 4.9.2
Priority High
137
Identifier FR-4.9.2
Title Show Sensor Enabled Message
Requirement Parent will be able to view Message of “ Heart Rate Sensor Enabled”
Source Parent
Rationale Parent must be able to View the message if the sensor is Enabled.
required)
Dependencies N/A
Priority Low

Identifier FR-4.9.3
Title Enable “Heart Rate Sensor Disable Button”
Requirement Button for Disabling the Heart Rate Sensor would be enabled
Source Parent
Rationale Parent must be able to view the button of “Disable Heart Rate
Sensor”.
required)
Dependencies N/A
Priority Medium
Identifier FR-4.10.1
Title Enable Body Temperature sensor
Requirement Parent will be able to press the button of “Enable Body Temperature
Sensor” and then the data from the Body Temperature sensor would
be sent to the application.
138
Source Parent
the Body Temperature of the baby.
required)
Dependencies 4.10.2
Priority High

Requirement Parent will be able to view Message of “ Body Temperature Sensor
Enabled”
Source Parent
required)
Dependencies N/A
Priority Low

Title Enable “Body Temperature Sensor Disable Button”
Requirement Button for Disabling the Body Temperature Sensor would be enabled
Source Parent
Rationale Parent must be able to view the button of “Disable Body
Temperature Sensor”.
required)
Dependencies N/A
Priority Medium
139
Title Enable Blood Oxygen Level sensor
Requirement Parent will be able to press the button of “Enable Blood Oxygen
Level Sensor” and then the data from the Blood Oxygen Level sensor
would be sent to the application.
Source Parent
the Blood Oxygen Level of the baby.
required)
Dependencies 4.11.2
Priority High

Requirement Parent will be able to view Message of “ Blood Oxygen Level Sensor
Enabled”
Source Parent
required)
Dependencies N/A
Priority Low

Title Enable “Blood Oxygen Level Sensor Disable Button”
Requirement Button for Disabling the Blood Oxygen Level Sensor would be
enabled
Source Parent
Rationale Parent must be able to view the button of “Disable Blood Oxygen
140
Level Sensor”.
required)
Dependencies N/A
Priority Medium
Title Enable Diaper Moisture Level sensor
Requirement Parent will be able to press the button of “Enable Diaper Moisture
Level Sensor” and then the data from the Diaper Moisture Level
sensor would be sent to the application.
Source Parent
the Diaper Moisture Level of the baby.
required)
Dependencies 4.12.2
Priority High

Requirement Parent will be able to view Message of “ Diaper Moisture Level
Sensor Enabled”
Source Parent
required)
Dependencies N/A
Priority Low

141
Title Enable “Diaper Moisture Level Sensor Disable Button”
Requirement Button for Disabling the Diaper Moisture Level Sensor would be
enabled
Source Parent
Rationale Parent must be able to view the button of “Disable Diaper Moisture
Level Sensor”.
required)
Dependencies N/A
Priority Medium

Title Enter Medicine Name
Requirement User Would be able to enter the medicine name which is prescribed
to the baby by the doctor.
Source Parent
Rationale Parent can Enter the Medicine name that is needed to be taken.
required)
Dependencies N/A
Priority Medium

Title Enter Medicine In take Time
Requirement Parent would be able to Enter the time at which the specific
medicine is to be taken.
Source Parent
Rationale So that parent always gives the medicine to the baby on time.
142
required)
Dependencies N/A
Priority High

Title Enter Medicine In take Quantity
Requirement Parent would be able to Enter the quantity of the medicine to be
taken.
Source Parent
Rationale So that parent never under or over doses the baby.
required)
Dependencies N/A
Priority High

Title View Medicine Name
Requirement Parent Would be able to View the Names of all the added medicines
by pressing the button “Medicine Detail”
Source Parent
Rationale So that parent knows which medicines are added and which are not
added.
required)
Dependencies N/A
Priority Medium
143
Title View Medicine Intake Time
Requirement Parent Would be able to View the intake time of all the added
medicines by pressing the button “Medicine Detail”
Source Parent
Rationale So that parent can check if the time entered is correct or not.
required)
Dependencies N/A
Priority Medium
Title View Medicine Intake Quantity
Requirement Parent Would be able to View the intake Quantity of all the added
medicines by pressing the button “Medicine Detail”
Source Parent
Rationale So that parent can check if the quantity entered is correct or not.
required)
Dependencies N/A
Priority Medium

Title Edit Medicine Name
Requirement Parent Would be able to edit the Name of the selected medicine by
clicking the edit button
Source Parent
Rationale So that parent can edit the name if the entered name was not
144
correct.
required)
Dependencies N/A
Priority Medium

Title Edit Medicine Intake time
Requirement Parent Would be able to edit the intake time of the selected
medicine by clicking the edit button.
Source Parent
Rationale So that parent can edit the intake time if the entered name was not
correct or the doctor has changed the timing.
required)
Dependencies N/A
Priority Medium

Title Edit Medicine Intake quantity
Requirement Parent Would be able to edit the intake quantity of the selected
medicine by clicking the edit button.
Source Parent
Rationale So that parent can edit the intake quantity if the entered name was
not correct or the doctor has changed the quantity.
required)
Dependencies N/A
Priority Medium
145
Title Delete Selected Medicine
Requirement Parent Would be able to delete all the details of the selected
medicine by clicking the delete button
Source Parent
Rationale So that parent can edit the intake time if the entered name was not
correct or the doctor has changed the timing.
required)
Dependencies N/A
Priority Medium
Module 5:
Identifier FR-5.1.1
Title Enter greeting Message
Requirement Parent Would be able to send a message with greeting the AI bot
Source Parent
Rationale So that the parent has a more real feeling of chatting.
Business Rule (if The message must include a greeting word.
required)
Dependencies N/A
Priority Medium
Identifier FR-5.1.2
Title Send greeting Message
Requirement Parent Would be able to send a message with greeting the AI bot
Source Parent
146
required)
Dependencies 5.1.3
Priority Medium

Identifier FR-5.1.3
Title Receive greeting message reply
Requirement Parent Would be able to receive the reply of the greetings message
by AI bot.
Source Parent
required)
Dependencies N/A
Priority High

Identifier FR-5.2.1
Title Enter Fever Remedy Message
Requirement Parent Would be able to send a message asking about Fever Remedy
from the AI bot
Source Parent
Rationale Parent will be able type message asking about fever
Business Rule (if The message must include a Fever Remedy message.
required)
Dependencies 5.2.2
Priority Medium
Identifier FR-5.2.2
147
Title Send Fever Remedy Message
Requirement Parent Would be able to send a message asking about Fever Remedy
from the AI bot
Source Parent
Rationale Parent will be able to send a message asking about fever remedy
from the AI bot.
Business Rule (if The message must include a Fever Remedy message.
required)
Dependencies 5.2.3
Priority Medium

Identifier FR-5.2.3
Title Receive Fever Remedy message reply
Requirement Parent Would be able to receive the reply of the Fever Remedy’s
message by AI bot.
Source Parent
Rationale So that the parent knows what to do urgently when the baby has got
fever.
required)
Dependencies N/A
Priority High

Identifier FR-5.3.1
Title Enter Fever symptoms Message
Requirement Parent Would be able to send a message asking about Fever
symptoms from the AI bot
Source Parent
Rationale Parent will be able type message asking about fever symptoms.
Business Rule (if The message must include a Fever symptoms message.
148
required)
Dependencies 5.3.2
Priority Medium

Identifier FR-5.3.2
Title Send Fever symptoms Message
Requirement Parent Would be able to send a message asking about Fever
Source Parent
Rationale Sending Message so that AI bot can reply.
Business Rule (if The message must include a Fever symptoms message.
required)
Dependencies 5.3.3
Priority Medium

Identifier FR-5.3.3
Title Receive Fever symptoms reply
Requirement Parent Would be able to receive the reply of the Fever symptoms
message by AI bot.
Source Parent
Rationale So that the parent knows what are the symptoms of Fever.
required)
Dependencies N/A
Priority High

Identifier FR-5.4.1
Title Enter Fever Causes Message
149
Requirement Parent Would be able to send a message asking about Fever Causes
from the AI bot
Source Parent
Rationale Parent will be able type message asking about Fever Causes.
Business Rule (if The message must include a Fever Causes message.
required)
Dependencies 5.4.2
Priority Medium

Identifier FR-5.4.2
Title Send Fever Causes Message
Requirement Parent Would be able to send a message asking about Fever Causes
from the AI bot
Source Parent
Business Rule (if The message must include a Fever Causes message.
required)
Dependencies 5.4.3
Priority Medium

Identifier FR-5.4.3
Title Receive Fever Causes reply
Requirement Parent Would be able to receive the reply of the Fever Causes
message by AI bot.
Source Parent
Rationale So that the parent knows what are the causes of Fever.
required)
Dependencies N/A
Priority High
150
Identifier FR-5.5.1
Title Enter Anemia Remedy Message
Requirement Parent Would be able to send a message asking about Anemia
Remedy from the AI bot
Source Parent
Rationale Parent will be able to type message asking about Anemia.
Business Rule (if The message must include Anemia Remedy message.
required)
Dependencies 5.5.2
Priority Medium
Identifier FR-5.5.2
Title Send Anemia Remedy Message
Source Parent
Rationale Parent will be able to send a message asking about Anemia remedy
from the AI bot.
Business Rule (if The message must include Anemia Remedy message.
required)
Dependencies 5.5.3
Priority Medium

Identifier FR-5.5.3
Title Receive Anemia Remedy message reply
Requirement Parent Would be able to receive the reply of the Anemia Remedy’s
message by AI bot.
Source Parent
151
Anemia.
required)
Dependencies N/A
Priority High

Identifier FR-5.6.1
Title Enter Anemia symptoms Message
Source Parent
Rationale Parent will be able type message asking about Anemia symptoms.
Business Rule (if The message must include Anemia symptoms message.
required)
Dependencies 5.3.2
Priority Medium

Identifier FR-5.6.2
Title Send Anemia symptoms Message
Source Parent
Business Rule (if The message must include a Anemia symptoms message.
required)
Dependencies 5.3.3
Priority Medium
152
Identifier FR-5.6.3
Title Receive Anemia symptoms reply
Requirement Parent Would be able to receive the reply of the Anemia symptoms
message by AI bot.
Source Parent
Rationale So that the parent knows what are the symptoms of Anemia.
required)
Dependencies N/A
Priority High

Identifier FR-5.7.1
Title Enter Anemia Causes Message
Causes from the AI bot
Source Parent
Rationale Parent will be able to type message asking about Anemia Causes.
Business Rule (if The message must include Anemia Causes message.
required)
Dependencies 5.7.2
Priority Medium

Identifier FR-5.7.2
Title Send Anemia Causes Message
Source Parent
Business Rule (if The message must include a Anemia Causes message.
153
required)
Dependencies 5.7.3
Priority Medium

Identifier FR-5.7.3
Title Receive Anemia Causes reply
Requirement Parent Would be able to receive the reply of the Anemia Causes
message by AI bot.
Source Parent
Rationale So that the parent knows what are the causes of Anemia.
required)
Dependencies N/A
Priority High

Identifier FR-5.8.1
Title Enter SIDS Remedy Message
Requirement Parent Would be able to send a message asking about SIDS Remedy
from the AI bot
Source Parent
Rationale Parent will be able to type message asking about SIDS.
Business Rule (if The message must include SIDS Remedy message.
required)
Dependencies 5.8.2
Priority Medium
Identifier FR-5.8.2
Title Send SIDS Remedy Message
154
Requirement Parent Would be able to send a message asking about SIDS Remedy
from the AI bot
Source Parent
Rationale Parent will be able to send a message asking about SIDS remedy
from the AI bot.
Business Rule (if The message must include SIDS Remedy message.
required)
Dependencies 5.8.3
Priority Medium

Identifier FR-5.8.3
Title Receive SIDS Remedy message reply
Requirement Parent Would be able to receive the reply of the SIDS Remedy’s
message by AI bot.
Source Parent
SIDS.
required)
Dependencies N/A
Priority High

Identifier FR-5.9.1
Title Enter SIDS symptoms Message
Requirement Parent Would be able to send a message asking about SIDS
Source Parent
Rationale Parent will be able type message asking about SIDS symptoms.
Business Rule (if The message must include SIDS symptoms message.
155
required)
Dependencies 5.9.2
Priority Medium

Identifier FR-5.9.2
Title Send SIDS symptoms Message
Requirement Parent Would be able to send a message asking about SIDS
symptoms from the AI bot.
Source Parent
Business Rule (if The message must include SIDS symptoms message.
required)
Dependencies 5.9.3
Priority Medium

Identifier FR-5.9.3
Title Receive SIDS symptoms reply
Requirement Parent Would be able to receive the reply of the SIDS symptoms
message by AI bot.
Source Parent
Rationale So that the parent knows what are the symptoms of SIDS.
required)
Dependencies N/A
Priority High

Title Enter SIDS Causes Message
156
Requirement Parent Would be able to send a message asking about SIDS Causes
from the AI bot
Source Parent
Rationale Parent will be able type message asking about SIDS Causes.
Business Rule (if The message must include a SIDS Causes message.
required)
Dependencies 5.10.2
Priority Medium

Title Send SIDS Causes Message
Requirement Parent Would be able to send a message asking about SIDS Causes
from the AI bot
Source Parent
Business Rule (if The message must include a SIDS Causes message.
required)
Dependencies 5.10.3
Priority Medium

Title Receive SIDS Causes reply
Requirement Parent Would be able to receive the reply of the SIDS Causes
message by AI bot.
Source Parent
Rationale So that the parent knows what are the causes of SIDS.
required)
Dependencies N/A
Priority High
157
Title Enter DIARRHEA Remedy Message
Requirement Parent Would be able to send a message asking about DIARRHEA
Source Parent
Rationale Parent will be able to type message asking about DIARRHEA.
Business Rule (if The message must include DIARRHEA Remedy message.
required)
Dependencies 5.11.2
Priority Medium
Title Send DIARRHEA Remedy Message
Source Parent
Rationale Parent will be able to send a message asking about DIARRHEA
remedy from the AI bot.
Business Rule (if The message must include DIARRHEA Remedy message.
required)
Dependencies 5.11.3
Priority Medium

Title Receive DIARRHEA Remedy message reply
Requirement Parent Would be able to receive the reply of the DIARRHEA
158
Remedy’s message by AI bot.
Source Parent
DIARRHEA.
required)
Dependencies N/A
Priority High

Title Enter DIARRHEA symptoms Message
Source Parent
Rationale Parent will be able type message asking about DIARRHEA symptoms.
Business Rule (if The message must include DIARRHEA symptoms message.
required)
Dependencies 5.12.2
Priority Medium

Title Send DIARRHEA symptoms Message
symptoms from the AI bot.
Source Parent
Business Rule (if The message must include DIARRHEA symptoms message.
required)
Dependencies 5.12.3
Priority Medium
159
Title Receive DIARRHEA symptoms reply
Requirement Parent Would be able to receive the reply of the DIARRHEA
symptoms message by AI bot.
Source Parent
Rationale So that the parent knows what are the symptoms of DIARRHEA.
required)
Dependencies N/A
Priority High

Title Enter DIARRHEA Causes Message
Source Parent
Rationale Parent will be able type message asking about DIARRHEA Causes.
Business Rule (if The message must include a DIARRHEA Causes message.
required)
Dependencies 5.13.2
Priority Medium

Title Send DIARRHEA Causes Message
160
Source Parent
Business Rule (if The message must include a DIARRHEA Causes message.
required)
Dependencies 5.13.3
Priority Medium

Title Receive DIARRHEA Causes reply
Requirement Parent Would be able to receive the reply of the DIARRHEA Causes
message by AI bot.
Source Parent
Rationale So that the parent knows what are the causes of DIARRHEA.
required)
Dependencies N/A
Priority High

Identifier FR-6.1.1
Title Get Current Location
Requirement Get the current location of the user so that nearby doctors can be
shown.
Source Parent
Rationale To know in which area is the parent.
Business Rule (if 6.1.2
required)
Dependencies N/A
161
Priority High

Identifier FR-6.1.2
Title Get Doctors List
Requirement List of all the doctors which are registered in the city where the
parent is will be fetched.
Source Parent
Rationale To get the list of doctors in the city.
required)
Dependencies N/A
Priority High

Identifier FR-6.1.3
Title Show Doctors Name
Requirement The name of the Doctors which are near the parent would be
displayed
Source Parent
Rationale To know which doctor is near the parent.
required)
Dependencies N/A
Priority High

Identifier FR-6.1.4
Title Show Doctors Profile Picture
Requirement The profile Picture of the Doctors which are near the parent would
162
be displayed
Source Parent
Rationale To know which doctor is near the parent.
required)
Dependencies N/A
Priority Low

Identifier FR-6.2.1
Title Send Request
Requirement User will be able to send the request to the doctor with which he
wants to interact by clicking “send request” button
Source Parent
Rationale So that doctor has the control with whom he wants to interact.
required)
Dependencies N/A
Priority High

Identifier FR-6.3.1
Title Get Pending request List
Requirement The request which are pending are fetched.
Source Doctor
Rationale So that the Doctor knows which request is pending
required)
Dependencies 6.3.2
Priority Medium
163
Identifier FR-6.3.2
Title View Name of Pending request user.
Requirement The doctor should know which user has sent him the request.
Source Doctor
Rationale So that the Doctor knows the name of the user.
required)
Dependencies N/A
Priority Medium

Identifier FR-6.3.3
Title View Profile picture of pending request user.
Requirement The doctor should know which user has sent him the request.
Source Doctor
Rationale So that the Doctor knows who is the user which has sent him
request.
required)
Dependencies N/A
Priority Medium

Identifier FR-6.4.1
Title Accept Pending Request
Requirement The doctor would be able to accept the pending request by pressing
the pending request button.
Source Doctor
Rationale So that doctor and parent can interact.
164
required)
Dependencies N/A
Priority High

Identifier FR-6.4.2
Title Reject Pending Request
Requirement The doctor would be able to reject the pending request by pressing
the pending request button.
Source Doctor
Rationale So that doctor can reject the request of a parent with which he does
not want to interact.
required)
Dependencies N/A
Priority Medium

Identifier FR-6.5.1
Title Show Added Doctors Name
Requirement The name of the Doctors which are added by the parent would be
displayed
Source Parent
Rationale To know which doctor is added to the parents doctor list.
required)
Dependencies 6.6.1
Priority High
165
Identifier FR-6.5.2
Title Show Doctors Profile Picture
Requirement The profile Picture of the Doctors which are added by the parent
would be displayed.
Source Parent
Rationale To know which doctor is added to the parents doctor list.
required)
Dependencies N/A
Priority Low
Identifier FR-6.6.1
Title Select doctor
Requirement Parent would be able to select one of the doctor with which parent
wants to chat.
Source Parent
Rationale To select one doctor for chatting and making appointment for call.
required)
Dependencies 6.6.1
Priority High
Identifier FR-6.6.2
Title Enter Message
Requirement Parent Would be able to type a message which is to be sent to the
selected doctor
Source Parent
Rationale Parent will be able to type message.
required)
166
Dependencies 5.3.2
Priority Medium

Identifier FR-6.6.3
Title Send Message
Requirement Parent Would be able to send a message to the selected doctor.
Source Parent, Doctor.
Rationale Sending Message so that doctor any reply to that message.
Business Rule (if N/A.
required)
Dependencies N/A
Priority Medium

Identifier FR-6.6.4
Title View Older Message
Requirement User Would be able to view the older messages that were send to
the User by the selected user.
Source Parent, Doctor
Rationale So that the user can see the previous conversion.
required)
Dependencies N/A
Priority High

Identifier FR-6.8.1
Title Enter Question to be posted
167
Requirement User Would be type the question which the user wants to ask from
the other users of the application.
Rationale To get the answers to the questions which the user wants to know
required)
Dependencies 6.8.3
Priority High

Identifier FR-6.8.2
Title Enter Question title
Requirement User Would be type the question title which will be visible to other
users.
Rationale To tell the users about the theme of the question.
required)
Dependencies 6.8.3
Priority Low

Identifier FR-6.8.3
Title Post Question.
Requirement User Would be able to post the question that would be visible to all
the other users of the application.
Rationale To ask the questions from the other users.
required)
Dependencies N/A
168
Priority High

Identifier FR-6.9.1
Title View Past Month Questions Title
Requirement User Would be able to view the titles of the posts of the past month.
Rationale To reply to that post or to see if anyone else has asked a specific
question before.
required)
Dependencies 6.9.2
Priority Medium

Identifier FR-6.9.2
Title View One Past Question (post)
Requirement User Would be able to select one of the past question which the user
wants- to see.
Rationale To see the complete post.
required)
Dependencies 6.9.3,6.10.1
Priority Medium

Identifier FR-6.9.3
Title View Name of the User
Requirement User Would be able to view the name of the user which has posted
the selected question.
169
Rationale To know who has posted the question.
required)
Dependencies N/A
Priority Low

Title Enter the reply to the post
Requirement User Would be able to type the reply to the question asked by the
other user
Rationale To help the other user on the question asked.
required)
Dependencies N/A
Priority High

Title Comment on Post
Requirement User Would be able to click the button “Post” and the comment
would be posted and visible to all the other users.
Rationale To help the other user on the question asked.
required)
Dependencies N/A
Priority High
170
Title View titles of all own post
Requirement User Would click on button “My Posts” and would be able to view
the titles of all the post then by him.
Rationale To help the user view his previous posts.
required)
Dependencies N/A
Priority High

Title View Selected own Post
Requirement User Would be able to view one of his own post my selecting its
titles
Rationale So that user can view the question which was previously posted.
required)
Dependencies 6.12.1
Priority Medium

Title Delete Selected Post
Requirement User Would be able to delete the post and it would not be visible to
the other users.
Rationale To remove the post if it is not needed.
171
required)
Dependencies N/A
Priority Low
5. Non Functional Requirements

The nonfunctional requirements of Mumta are given below:
4.3 Usability
USE-1: The Mumta shall allow a user to retrieve the previous post with a single interaction.
USE-2: The app will take a maximum of 5 minutes for an average user to learn the system.
USE-3: All delays in the system longer than 2 seconds will produce a message of “please wait”
5.3 Performance
PER-1: Maximum of 100,000 Simultaneous users can be supported by the application.

PER-2: Maximum of 100,000 Simultaneous users can be supported by the application.
PER-3: Maximum of 100 accounts/hour can be created
PER-4: The data transfer rate from application to cloud is max 10MB/sec for an internet
connection greater or equal to 10MB/sec
6.3 Supportability
SR-1
The application will be compatible with android version 4.4, kit Kat and higher.pokm2221
7. References
7.1 Research Papers

• Health Facts research paper on Sudden Infant Death Syndrome
7.2 Blog
• Top five challenges new moms have to face.
• Common infant problems
7.3 Books
• Ian Somerville for concepts of Software Engineering.
172
173

Mamta SRS Document

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mamta SRS Document

Uploaded by

Copyright:

Available Formats

COMSATS University Islamabad,

Park Road, Chak Shahzad, Islamabad Pakistan

Bachelor of Science in Computer Science (2016-2020)

Revision History iii

Comments (by committee) Action Taken

2.3 Overall description

The environment in which Mumta will operate is given below:

The design and implementation constraints of Mumta are given below:

3.3 Requirement identifying technique

Use Case Diagram SEQ

3.2. Use case description

Table 1 Signup Use Case

Use Case ID: UC-1.1

Description: Parent will be able to create an account in application.

Preconditions 1. Internet connection is available and working properly.

Notes And N/A.

Use Case ID: UC-1.2

Preconditions 1. Internet connection is available and working properly.

Post 1. User is logged into their respective account.

Normal Flow: 1. User opens the application.

Assumptions: 1. User knows the basic knowledge of using smartphones.

UC-1.3: Forget password

Use Case ID: UC-1.3

Preconditions 1. Internet connection is available and working properly.

Post 1. User’s password reset successfully.

Normal Flow: 1. User clicks on “Forgot password?” text.

Assumptions: 1. User knows the basic knowledge of using smartphones.

Notes And N/A.

UC-1.4: Add New Baby

Use Case ID: UC-1.4

Preconditions 1. Internet connection is available and working properly.

Normal Flow: 1. User clicks on the “Add new baby” button.

Assumptions: 1. User knows the basic knowledge of using smartphones.

UC-1.5: Remove Baby from account

Use Case ID: UC-1.5

Use Case Remove Baby from account

Actors: Primary Actor: Parent, Doctor

Trigger: User clicks on “Delete Child Data” Button.

Post 1. Child Data removed from the account successfully.

Assumptions: 1. User knows the basic knowledge of using smartphones.

UC-1.6: Edit Baby Details

Use Case ID: UC-1.6

Post 1. Baby’s Details changed successfully.

Assumptions: 1. User knows the basic knowledge of using smartphones.

UC-1.7: Change Baby Image

Use Case ID: UC-1.7

Use Case Change Baby image

Actors: Primary Actor: Parent, Doctor

Trigger: User clicks on “Edit baby details” button.

Business 1. Parent must have an account.

Notes And N/A.

UC-1.8: Change Password

Use Case ID: UC-1.8

Preconditions 1. Internet connection is available and working properly.

Post 1. User password changed successfully.

Normal Flow: 1. User clicks on Settings button.

Assumptions: 1. User knows the basic knowledge of using smartphones.

UC-1.9: Add Health Gadget

Use Case ID: UC-1.9

Use Case Add Health Gadget

Actors: Primary Actor: Parent, Doctor

Trigger: User clicks on Add health gadget button.

Business 1. Parent must have an account.