Aim :​To develop Software Specification Requirements (SRS) document in IEEE

format for the project Smart Health Management System

1. Introduction

1.1 Purpose

This document is meant to delineate the features of SHMS, so as

to serve as a guide to the developers on one hand and a software
validation document for the prospective client on the other. The
Smart Health Management System (SHMS) is a permanent
lifestyle change that teaches you how to naturally reduce the
number of calories you consume by selecting fresh, minimally
processed foods that are rich in nutrients in relation to their calorie
content.

1.2 Scope

This system will be used by people who want to know what type of
food serving that are suitable for them and want to manage their
diet better. It can also be used by people who works relate to the
diet field. This will include the public, the expert dietitian/nutritionist,
medical/health staff, individuals who is involved in campaign or talk
to promote health and diet and so on.

1.3 Terminology

SHMS-Smart Health Management System

SRS- Software Requirement Specification

GUI- Graphical User Interface

Stockholder- The person who will participate in system

Ex. Customer, dietitian, nutritionist, medical/health staff etc.

2. Description of Project

2.1 Project Perspective

Most people are concern about what they eat

everyday. This is because "we are what we eat".
People tend to search information about the things that
they eat or what related to their diet. Nowadays, there
are systems which help people to manage their diet.
However, the systems are not specifically focusing on
the user's own needs. Different people will require
different dietary needs or nutrition for their body. This is
due to variety of weight, daily activity level and so on.
So they need something that will help them with their
own personal body needs. The system that has been
developed is an Online Diet Planning System. This
web-based application system will help user to get
information about their dietary intake. There will be
dietary recommendations for the user based on what
they need. It is more focusing on the user with his or
her own needs rather than just giving the general
recommendations to all users.

2.2 Product Function

1. User will enter data related to his/her height, weight,

age, type of physical activity.
2. Depending on user input app will generate diet plan for
user for breakfast, lunch, supper, dinner .
3. If the user is not satisfy with the diet plan suggested by
the app then he/she can request for review of diet plan
by dietician.
4. User can request for change of diet plan after specific
period of time .

2.3 User Characteristic

1. Patient: Can do the following - register, login, view

diet, request for diet change through dietician.
2. Dietician : Can review the diet created by app.
 2.4 General Assumption
​1.​ Diet plan can be change at any time.
3. Specific Requirement
3.1 Functional Requirement :
3.1.1 User Interface :
GUI is provided by the software which is
self-explanatory.
User friendly forms, menus and options are contained
by the software.
The user has to select a menu, request for delivery and
select the mode of payment.
3.1.2 Hardware Interface :
1. Personal Computer
2. XAMPP server.
3.1.3 Software Interface :
1. Web browser
2. HTML , CSS, Javascript and PHP

3.1.4 Communication Interface :

Communication function require the internet protocol
version 6 and it will follow HTTPS.
3.2 Software product feature :
The software will allow the user to maintain their entire
record in one place which will be easy to manage. It will also
reduce the risk of errors.Features:Store information of all
user diet, Easy search for diet plan,User friendly, Feedback
directly, reaching the owner, Handling stock information of
each branch,Tracks Damaged/Date Expired/Returned
Products, Easy account maintenance.

3.3 Non-functional Requirements :

3.3.1 Design Constraints:

Software gives warnings with necessary assistance to
the clients.
 Secure access to user’s confidential data.

3.3.2 Efficiency :
90% of responses should be within 1 second, except
for Update content for which more time is acceptable.
3.3.3 Usability :​ ​24/7 availability.
3.3.4 Correctness :
Coding conventions and follow-up documents for
maintenance activities.
3.3.5 Testability :
This system will work on client-server architecture. The
system should support common browsers such as IE,
mozilla firefox, chrome, etc.

3.4 Security Requirement :

We are going to develop a secure database. There are
different categories of user namely administrator, Patient,
Dietician who will be viewing either all or some specific
information from the database. Depending upon the category
of user the access rights are decided. It means if the user is
patient then he can only view diet plan and he/she cannot
modify the diet plan. All other user have right to retrieve the
information from database.

4.0 Other Requirement :

4.1 Apportioning of requirement :
Patient
Dietician
Diet Plan
4.2 Database
All data will be stored in relational database (using Xampp
software ). Different database created are patient, Dietician, Diet
plan.

4.2.1 For Patient

Name Email Contact password Gender Age Weight Activity

4.2.2 For Dietician

Name Email Contact password Certificate Experience

4.2.3 Diet Plan

Time Diet Serving size Energy Alcohol

(fl oz) (kcal/serving) (g/serving)

4.3 Schedule And Budget

Roll no Assigned Task Weeks

person
41 Saif Forms and content 2
Krunal Homepage ,form 2
39 Ankit Backend, 2
connectivity
Total 6
 Sr.No. Software Budget
1 Xampp $80/-
2 Vs code $40/-
3 kompozer $60/-
Total $180/-

Conclusion
For given case study SRS Document is completed.