CHAPTER 1

INTRODUCTION

1.1. NEED OF THE SYSTEM

Faster make your weight in control.
Maintain your body according to your weight.
Protect your body from cholesterol and you can protect yourself from many
hygienic dieses.
You can get attractive Figure without any Surgery.

1.2

DETAILED PROBLEM DEFINITION

The idea behind the system is to develop a web portal which suggests
and manages the diet plan and weight loss tips.
This system is set of useful features needed for the person struggling
from obesity, plumpness and overweight.

1.3

VIABILITY OF THE SYSTEM

The system is viable as its need is not going to end and the weight gaining
and weight loosing tips are reliable.
The system features are definite and the suggestions suggested accurate
and precise to fulfill its functionality.

1.4

PRESENTLY AVAILABLE SYSTEM

After studying current system we find that current system has less facility
and it takes much time to perform the operation.
Current system cannot provide the central data storage and storage and it
leads to the data redundancy and is also time consuming.

1.5

FUTURE PROSPECT

Secure registration and profile management facilities.

Adequate searching for easy and quick access to particular exercise
equipment.
Maintaining database of regular customers of different needs.
Feedback mechanism, so that user can give feedback for the facility or
website. Also feedback the entire user.

CHAPTER 2
ANALYSIS

2.1

REQUIREMENT ANALYSIS

The requirements for the new system we concluded were as below

To generate the quick reports
To make accuracy and efficient calculations
To provide proper information briefly

To provide data security

To provide huge maintenance of records
Flexibility of transactions can be completed in time

After understanding the existing system and understanding the need for
developing a new system different people involved in the related activities have
been consulted. The data needed for the study has been collected from company
records.
The computerization of this system would avoid the wrong
interpretation and bad calculation of data .The system help the user to see any
documents, source code, tasks, activities, team information with details at the
click of a button. The record data is maintained and backed up such a way that
data is not loss. The speed of the system could also increase.

2.2

PROJECT MODEL

We are using the iterative waterfall model for this system.

Feasibility Study

Requirement
analysis and
Specification

Design

Coding And Unit

Testing

Integrtion and System

Testing

Maintanance

FIGURE-1

2.3

SCHEDULE REPRESENTATION
TABLE-1 SCHEDULE REPRESENTATION

ACTIVITY

START

FINISH

DATE

DATE

Feasibility study

26/06/2015

28/07/2015

System Analysis

28/07/2015

01/09/2015

System Design

01/09/2015

06/10/2015

System Coding

06/10/2015

05/03/2016

Testing and Integration

05/03/2016

10/04/2016

2.4

FEASIBILITY STUDY

Preliminary investigation examines project feasibility, the likelihood the system

will be useful to the organization. The main objective of the feasibility study is to
test the Technical, Operational and Economical feasibility for adding new
modules and debugging old running system. All system is feasible if they are
unlimited resources and infinite time. There are aspects in the feasibility study
portion of the preliminary investigation:
2.4.1 Technical Feasibility
2.4.2 Operational Feasibility
2.4.3 Economical Feasibility

2.4.1 Technical Feasibility:

The technical issue usually raised during the feasibility stage of the
investigation includes the following:
Does the necessary technology exist to do what is suggested?
Do the proposed equipments have the technical capacity to hold
the data required to use the new system?
Will the proposed system provide adequate response to inquiries,
regardless of the number or location of users?
Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of
access and data security?
. The current system developed is technically feasible. Thus it provides an
easy access to the users. The databases purpose is to create, establish and maintain a
workflow among various entities in order to facilitate all concerned users in their
various capacities or roles. Permission to the users would be granted based on the
6

roles specified. Therefore, it provides the technical guarantee of accuracy,

reliability and security. The software and hard requirements for the development
of this project are not many and are already available in-house at NIC or are
available as free as open source.

2.4.2 Operational Feasibility:

Proposed projects are beneficial only if they can be turned out into
information system. That will meet the organizations operating requirements.
Operational feasibility aspects of the project are to be taken as an important part
of the project implementation. Some of the important issues raised are to test the
operational feasibility of a project includes the following: Is there sufficient support for the management from the users?
Will the system be used and work properly if it is being
developed and implemented?
Will there be any resistance from the user that will undermine the
possible application benefits?
This system is targeted to be in accordance with the above-mentioned
issues. Beforehand, the management issues and user requirements have been
taken into consideration. So there is no question of resistance from the users that
can undermine the possible application benefits.

2.4.3 Economical Feasibility:

A system can be developed technically and that will be used if installed must
still be a good investment for the organization. In the economical feasibility, the
development cost in creating the system is evaluated against the ultimate benefit
derived from the new systems. Financial benefits must equal or exceed the costs.

The system is economically feasible. It does not require any addition

hardware or software. There is nominal expenditure and economical feasibility
for certain.

CHAPTER 3
DESIGN

3.1

DATA FLOW DIAGRAM

A System flow is a graphic tool which helps in clearly specifying the steps
towards a problem solution.
System symbols of system flow diagrams are:

FIGURE 2:DATA FLOW DIAGRAM

3.1.1 Context level Diagram

MANAGE DATA (CITY,STATE,SECURITY)
ADD CHART DETAILS
GENERATE REPORTS
LOGIN/
AUTHENTICATION
ACCESS RIGHT
ADD CATEGORY DETAIL
ADD PRODUCT DETAIL
MANAGE PAYMENT DETAIL
MANAGE FEEDBACK
DETAIL

UNIVERSAL
HEALTH BUDDY

SELECT CATAGORY
GET CHART DETAIL
GET VIDEO/EXERCISE
DETAIL
DIET FILL UP FORM

USER

LOGIN
ACCESS RIGHT
GET CHART DETAIL
ASK FEEDBACK
GIVE PAYMENT

FIGURE-3:CONTEXT LEVEL DIAGRAM

10

ADMIN

3.1.2 1 level Diagram

Admin
Id,password
1.0

Login_table

1.0

Login

Login
Homepage

2.0

Enter city

2.0

city

city

View city

ss

id

I
d

city_table

,p

ci

e
m
a

it
y

3.0

Category detail
Category_table

3.0

,c

category

id

category

View category

ca

Admin

diet
_
id,d

iet_

4.0

type

4.0

Enter chart detail

dietician
P

dietician

Id

,
p

Manage chart

na

dieticion_tab
le

Feed
b
a

S
t

ck

te
_

5.0

id

,fe

Enter product detail

Product_tabl
e

5.0

e
d

me

sta
t
e
i
d

product
product

c
k

Manage product

am
e

6.0
6.0

Feedback

View feedback

Feedback_tabl
e

View feedback
acknowledgement

7.0
7.0

state

Enter state

state
View state

FIGURE-4: 1 LEVEL ADMIN DIAGRAM

state_table

11

User
Id,password

Login_tab
le

1.0
Login
Homepage

2.0
Plan
detail
r

diet_tabl
e

Fill plan detail

s
s

,a
I p
d

t
y

View charts

e
p

,p
e
a

n
_
P

id

3.0
categor
y

_
t

a
c
,

e
a

m
n

at

Category detail

Category_ta
ble
View category

user

r_id,p_type

payment detail
4.0

P
_

Id ,

Payment_table
p

payment
a

View payment

F
eedback

_
i
d

fe

ed
b

detail 5.0

ck
_
nam
e

Enter product

Product_ta
ble

product
Manage product

6.0
View
feedback

Feedback
Feedback_Ta
ble
Acknowledgement

FIGURE-5: 1 LEVEL USER DIAGRAM

12

3.1.3 2 level Diagram

User
U_id,name

U_id,name

U_id,name
Registration

Login page

user_Registration

Registration
Login page

Id, password

Id, password
Id, password

Login

Homepage

Login_table

Login
Homepage

Chart_id,Chart_name
Chart_id,Chart_name

chart

View chart

Chart_id,Chart_name

chart_Table

chart

View chart
Excersice_id,video_id
Excersice_id,video_id

Video/excircise

view Video/exercise
detail

Excersice_id,video_id

view Video/exercise
detail

Cat_id,Cat_name
Cat_id,Cat_name

category

View category

Video/exercise table

Video/expiries

Cat_id,Cat_name

category_Table

category

View category
P_id,P_name

P_id,P_name
P_id,P_name

product

View product

product_Table
product
View product

FIGURE-6: 2 LEVEL USER DIAGRAM

13

Admin
Id,password

Id,password

Id,passwo
rd

Login_Tab
le

Login

Login
Homepage

Homepage

Cat_id,Cat_name

Cat_id,Cat_na
me

Add Category

Cat_id,Cat_name

Category_Ta
ble

Add Category

View multiple categories

View multiple
categories

Feedback_id

Feedback_id

Feedback_id

Feedback_name

Feedback_name

Feedback_name

Feedback_Ta
ble

viewfeedback
View Feedback
acknowledgem
ent
acknowledgem
ent

P_id,P_na
me
P_id,P_na
me

Product

P_id,P_name

Product_Tab
le

Produ
ct

View product
View product

FIGURE-7: 2 LEVEL ADMIN DIAGRAM

14

3.2

ER DIAGRAM

Data models are tools used in analysis to describe the data requirements and
assumptions in the system from a top-down perspective. They also set the stage
for the design of databases later on in the SDLC.
There are three basic elements in ER models:
Entities are the "things" about which we seek information.
Attributes are the data we collect about the entities.
Relationships provide the structure needed to draw information
from multiple entities
Relationships
A Relationship is a diamond that contains its name. It touches one
relationship-entity and optionally some attribute-entity connectors. It is linked
with two entities.
Connectors
A relationship-entity connection is a line that touches exactly one text label
(expressing cardinality) and two other regions (rectangle or diamond).
Cardinality is a text string with values chosen from the set.

15

3.2.1 Symbols Used In E-R Model:

An entity set is represented as a rectangle.
A diamond represents the relationship among a number of entities, which
are connected to the diamond by lines.

TABLE-2 SYMBOLS OF ER

16

Mapping Symbols
TABLE-3 MAPPING SYMBOLS
Symbol Name

Symbol

One to One
One to Many
Many to One
Many to Many

17

login

has

manag
es

admin

user

manages
Cat_id

manages
Cat_name

State_id
State_id

date

plan details

State_nam
e

State_nam
e

select

category

P_id

get

state
P_name

has

Shopping bag
P_type

has

r_id

has

Sub_cat_id

Sub_cat_
id

City_id

city
City_name

has

price

price

Sub_cat_na
me

subcategory
chart

Sub_cat_name

Cat_id

Cat_id
P_id

chart_id

has

payment

chart_type

P_id

product

Price

R_id

description

P_type
dat
e

P_name
image

price
states

S_id

Ex_date

M_date

FIGURE-8: ER DIAGRAM

18

CHAPTER 4
SYSTEM MODELLING

4.1

DATABASE DESIGN

4.1.1 Admin Login

TABLE-4: ADMIN LOGIN

Field Name

Data Type

Size

Constraints

Description

Login_id

int

Primary key

This is the ID for the

Admin

Login_Name

varchar

40

NotNull

this is the name for the

Admin

R_id

int

Foreign key

this is the register_id for

the admin

U-Name

varchar

40

NotNull

this is the user_name

Pwd

varchar

40

NotNull

this is the password for the

admin

19

4.1.2 Register
TABLE-5: REGISTER

Field Name

Data Type

Size

Constraints

R_id

int

Primary
Key

F_Name

varchar

40

NotNull

L_Name

varchar

40

NotNull

Address

varchar

40

NotNull

State

int

City

int

Email

varchar

40

Foreign
Key
Foreign
Key
NotNull

ph_no

bigint

10

NotNull

Description
this is the register_id for the
user
this is the frist-name for the
user
this is the last-name for the
user
this is the address for the
user
this is the state for the user
this is the city for the user
this is the email for the user
this is the phone _no for the
user

4.1.3 Category
TABLE-6:CATEGORY

Field Name
cat_id
cat_name

Data Type
int
varchar

Description

varchar

Size
4
40
40

Constraints
Description
Primary key this is the category_id
NotNull
this is the category_name
this is the category
NotNull
description

20

4.1.4 Chart
TABLE-7: CHART

Field Name
chart_id
chart_type
chart_image
chart_date

Data Type
int
varchar
varchar
date

weight_type

varchar

Size
4
40
40
40

Constraints
Primary key
NotNull
NotNull
NotNull
NotNull

Description
this is the chart_id
this is the chart_type
this is the chart_image
this is the chart_date
this is the weight_type for
user

4.1.5 Security
TABLE-8: SECURITY

Field Name
security_id

Data Type
int

security_question varchar

Size
4

Constraints Description
Primary key this is the security_id
this is the
NotNull
security_question

100

4.1.6 Sub-Category
TABLE-9: SUB-CATEGORY

Field Name

Data Type

Size

subcat_id

int

cat_id
subcat_name
subcat_detail
Image

int
varchar
varchar
varchar

4
40
40
40

Constraints
Primary
Key
foreign key
NotNull
NotNull
NotNull

Description

varchar

40

NotNull

Price

bigint

10

NotNull

21

Description
this is the sub_cat _id
this is the cat_name
this is the sub_cat _name
this is the sub_cat _detail
this is the sub_cat _image
this is the description for
the sub_cat
this is the price for the
sub_cat

4.1.7 Cart
TABLE-10: CART

Field Name
cart_id
cart_name
Register_id

Data Type
int
varchar
int

total_price

bigint

Size
4
40
4
10

Constraints
Primary key
NotNull
NotNull
NotNull

Description
this is the cart_id
this is the cart_name
this is the cart register id
this Is the price for cart's
product

4.1.8 Exercise chart

TABLE-11:EXERCISE CHART

Field Name
excersice_id

Data Type
int

Size
4

video_id

int

excersice_type

varchar

40

Constraints Description
Primary key this is the excersice_id
this is the excersice's
NotNull
video_id
NotNull
this is the excersice_type

4.1.9 Feedback
TABLE-12:FEEDBACK

Field Name

Data Type

Size

feedback_id

int

feedback_name
Date

varchar
date

40

Description

varchar

255

Constraints
Primary
Key
NotNull
NotNull
NotNull

22

Description
this is the feedback_id
this is the feedback_name
this is feedback date
this is the feedback
description

4.1.10 Plan details table

TABLE-13:PLAN DETAILS

Field Name
p_name
p_type

Data Type
varchar
varchar

r_id

int

Size
40
40
4

Constraints Description
NotNull
this is the plandetails_name
NotNull
this is the plandetails_type
this is the register_id for the
Primary key
user

4.1.11 Payment
TABLE-14:PAYMENT

Field Name
p_id

Data Type
int

Size
4

r_id

int

p_type

varchar

40

Price

bigint

10

States
Date

varchar
date

40

Constraints Description
primary key this is the payment_id
this is the register_id for
NotNull
the payment
NotNull
this is the payment_type
this is the price for the
NotNull
product
NotNull
this is the state detail
NotNull
this is the date detail

23

4.1.12 Product
TABLE-15:PRODUCT

Field Name

Data Type

Size

Constraints Description

p_id

int

Primary key

this is the product_id

p_name

varchar

40

NotNull

this is the product_name

s_id

int

NotNull

this is the s_id

Price

bigint

10

NotNull

this is the price details

Description

varchar

40

NotNull

m_date

varchar

40

NotNull

e_date

varchar

40

NotNull

this is the product expire

date

Image

varchar

40

NotNull

this is the product image

24

this is the product

description
this is the product
manufacture date

CHAPTER 5
TECHNICAL SPECIFICATION
5.1 Hardware Specification
Processor: Core 2 Duo Processor.
RAM:512 MB RAM or more.
Hard disk Capacity:250 GB Hard Disk Space.

5.2 Additional Hardware Tools

Printer

5.3 Platform
OS: Windows XP or more.
Frontend: PHP.

5.4 Programming Languages Used

Markup Language:HTML
Design Platform:CSS
Scripting Language:Java Script
Front-End :- PHP 5.4
Back-End :- MY SQL 2008

5.5 Software Tools Used

Web Server : Xampp Server
UML:Microsoft Office Visio 2010
IDE:Dreamweaver 8.1
Documenting : Microsoft Word 2013

25

5
0