Beruflich Dokumente
Kultur Dokumente
ONLINE AYURVEDIC
SOLUTION
PROJECT CATEGORY:RDBMS stands for Relation Database Management System. The RDBMS is responsible
for:
4
2. Medicine master:This module is designed for the purpose of storing all information of ayurvedic medicines,
which is available with our system. A registered user, see the entire available product and
give an order (if he she want to purchase). The system give this order to our registered
vender and make payment. The customer pay amount of product by our system through
credit card, prepaid card and internet banking.
3. Course master:This module is designed for the purpose of storing the information of different course like
Ayurveda and panchakarma therapy, Ayurveda and beauty care, Ayurveda ways of life
style management, training program in yoga.
4. Expert for Ayurveda:This module is designed for the purpose of storing the information of experts. A valid user
can consult to expert for appropriate consultation and appointment. . The consultation can
be done in two ways-on line and off-line also. Through online a registered customer
6
5. Payment gateway:This module is design for the purpose of storing the information about payment can be
done by different mode like credit card, prepaid card and internet banking.
6. Vendor master:-
1. User master:This module is designed for the purpose of storing all the information related to user. If a
user is registered then he/she have a valid ID and password and if a user is not registered
then first he perform registration. A registered user can see product details, book the
product and make payment as well as consult to expert.
2. Medicine master:This module is designed for the purpose of storing all information of ayurvedic medicines,
which is available with our system. A registered user, see the entire available product and
give an order (if he she want to purchase). The system give this order to our registered
vender and make payment. The customer pay amount of product by our system through
credit card, prepaid card and internet banking.
3. Course master:This module is designed for the purpose of storing the information of different course like
Ayurveda and panchakarma therapy, Ayurveda and beauty care, Ayurveda ways of life
style management, training program in yoga.
4. Expert for Ayurveda:This module is designed for the purpose of storing the information of experts. A valid user
can consult to expert for appropriate consultation and appointment. . The consultation can
be done in two ways-on line and off-line also. Through online a registered customer
8
5. Payment gateway:This module is design for the purpose of storing the information about payment can be
done by different mode like credit card, prepaid card and internet banking.
6. Vendor master:-
7. E books :In this module there are so many types of books available this module is access by expert
and user as well as vendor also.
8. Staff Master :This module is design for the purpose of storing all the information related to staff of our
organisation. The work for staff is as follows:He/she delivered the product to customer and he/she also manage for consultation between
user and our experts.
10
9. E books :In this module there are so many types of books available this module is access by expert
and user as well as vendor also.
10.
Staff Master :-
This module is design for the purpose of storing all the information related to staff of our
organisation. The work for staff is as follows:He/she delivered the product to customer and he/she also manage for consultation between
user and our experts.
11
11.
E books :-
In this module there are so many types of books available this module is access by expert
and user as well as vendor also.
12.
Staff Master :-
This module is design for the purpose of storing all the information related to staff of our
organisation. The work for staff is as follows:He/she delivered the product to customer and he/she also manage for consultation between
user and our experts.
12
DATA FLOW DIAGRAM (DFD):Graphical description of a systems data and how the processes transform the data is
known as Data Flow Diagram.
DFD do not supply detailed descriptions of modules but graphically describe a systems
data and how the data internet with the system. The constant data flow diagrams. We use:
i.)
Arrows
ii.)
Circles
iii.)
iv.)
Square
or
13
0 Level DFD:-
Medicine Master
Vendor Master
Staff Master
ONLINE
AYURVEDIC 14
SOLUTION
Course Master
E-Books
User Master
Payment Gateway
User
Medicin
e
Master
retrieve
Course
Master
access
retrieve
retrieve
access
Vendor_Master_Details
User
interact
Vendor
Master
15
retreive
Payme
nt
Gatewa
y
make
Payment_Mas
ter
acess
Medicine_Booking_Details
acess
E_Books_Mast
EBooks
read
put
Expert
for
Ayurved
a
manage
retreive
retreive
Appoint_Details
Doctor_Master
Staff
Master
staff
store
1. User Master
User_Master_Details
access
User
Master
check
Valid ID
and
Password
No
User
Inform to
User
Yes
Generate a
welcome
message
you see
fill
Make Payment
Book Product
E - Books
New User
Sign up
Page
16
Product Details
submit
give to
Generate
ID and
store into
User_Master_Details
2. Medicine Master
Medicine_Master_Details
Medicine
Master
see
Available
Product
Book the
Product
through
interact
Vendor
User
Give vendor
address
17
through
Through
website
Ve _Booking_Details
send to
Generate
booking ID/send
vendor ID
Medicine_Booking_Details
3. Course master
Course_Master_Details
access
Course
Master
see
The
available
course
interact
show
Different
courses & its
duration
User
18
Expert for
Ayurveda
take
check
Available
doctors
Appointme
nt
through
interact
On line
consultatio
n
User
through
Off line
consultation
store
store
Send to
Appointment_Details
Inform to User
ENTITY RELATIONSHIP DIAGRAM(ERD):It is the Logical Representation of System. It has three main components:
i.
ii.
iii.
Data entities
Relationship
Attributes
19
User_Name
man
age
User_ID
Medicine_
No
A_ID
Medicine_na
me
A_ID
User Master
Medicine Master
See
&bo
ok
Take
produ
ct
Take
appoint
Purchase
Doctor_
ID
Put
details
product
A_ID
departm
ent
Vendor Master
make
Vendor_na
me
A_I
D
20
Interac
t
Vendor_
ID
Emp_I
D
A_ID
Payment Gateway
Emp_na
me
Staff Master
take
Amou
nt
Payment
_Mode
Addre
ss
User_ID
city
uplo
ad
lear
n
uplo
ad
Edition_
no
A_ID
C_ID
Institute_na
me
Course Master
Course_na
me
Benefits
Date of
publication
DATA
STRUCTURE:Book_Nam
e
Course_Dura
tion
E -Books
Book_ID
s
e
e
A_ID
A_ID
1. User_Master_Details
S.no
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Attributes
A_ID
User_ID
User_Name
User_Gender
User_DoB
User_Address
User_Mobile_No
User_Ph_No
City
Email_ID
Data Type
Int
Int
Varchar
Varchar
date time
Varchar
Bigint
Bigint
Varchar
Varchar
Size
50
50
255
50
150
21
2.
a.) Medicine_Master_Details
S.no
1.
2
3
4.
5.
6.
7.
8.
9
10
Attributes
A_ID
Medicine_no
Medicine_Name
Medicine_Batch_No
Manufacturer_Name
Manufacturer_Address
Vendor_ID
User_ID
Date _of_ mfd
Date_of_exp
Data Type
Int
Int
varchar
numeric
varchar
varchar
int
Int
datetime
datetime
Size
50
100
255
b.) Medicine_Booking_Details
S.no
Attributes
1. A_ID
Data Type
Int
22
Size
Medicine No.
Booking_ID
Booking Date
Payment Mode
User_ID
V_ID
numeric
Int
datetime
varchar
Int
Int
50
c.) Vendor_Booking_Details
S.no
1.
2.
3.
4.
5.
6.
Attributes
A_ID
Medicine No.
Booking_ID
Booking Date
V_ID
Payment Mode
Data Type
Int
numeric
Int
datetime
Int
varchar
Size
50
3. Course_Master_Details
S.no
1.
2
2.
3.
4.
5.
6.
7.
8.
Attributes
A_ID
C_ID
Course Name
Course Duration
Course _fee_struc
Benefits
Institute Name
Institute Address
Institute Contact No
Data Type
Int
Int
varchar
varchar
int
varchar
varchar
varchar
numeric
23
Size
50
50
500
255
255
4.
a.) Doctor_Master
S.no
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Attributes
A_ID
Doctor_ID
Doctor Name
Email_ID
Contact No
Department
Appointment_ID
Appointment Date
Appointment Time
Consultation_ Fees
Data Type
Size
Int
int
Varchar
Varchar
numeric
varchar
Int
Datetime
Datetime
Int
50
150
50
b.) Appointment_Details
S.no
1.
2.
3.
4.
5.
6.
Attributes
A_ID
Doctor_ID
User_ID
Appointment Date
Appointment Date
Consultation Fee
Data Type
Size
Int
Int
Int
Datetime
Datetime
Numeric
5. Payment_Master
S.no
1.
2.
3.
4.
5.
6.
Attributes
A_ID
User_ID
Payment Mode
Amount
Credit card_ID
Prepaid card_ID
Data Type
Int
Int
Varchar
Numeric
bigint
Bigint
Size
50
24
i.
Payment date
Internet Banking
Receipt no
Datetime
varchar
Numeric
255
Credit Card_Transaction_Details
S.no
Attributes
Data type
.
1.
2.
3.
A_ID
User_ID
Payment
Int
Int
Longint
4.
amount
Date of
datetime
5.
6.
payment
Credit card_ID
Card Holder
Int
Varchar
7.
Name
Card date
datetime
Size
50
Prepaid Card_Transaction_Details
ii.
S.n
Attributes
Data type
o
1
2
3.
4.
A_ID
User_ID
Prepaid card_ID
Payment
Int
Int
Int
Varchar
5.
amount
Date of
datetime
6.
payment
Card Holder
Varchar
Name
25
Size
50
50
Card date
datetime
iii. Internet_banking_Detail
S.n
Attributes
Data type
o.
1.
2.
3.
4.
5.
6.
7.
A_ID
User_ID
Account no
Bank Name
Bank Branch
IFSC _Code
IT_ID
Int
Int
Longint
Varchar
Varchar
Varchar
Int
size
255
255
50
6. Vendor_Master_Details
S.no
1.
2.
3.
4.
5.
6.
7.
8.
Attributes
A_ID
Vendor_ID
Vendor Name
Email_ID
Address
Contact No
Registration No
Fax No
Data Type
Int
Int
Varchar
Varchar
varchar
Numeric
Numeric
Numeric
Size
50
150
255
7. E_Books_Master
S.no
1.
2.
3.
4.
5.
6.
Attributes
A_ID
Book_ID
Book Name
Author Name
Edition No
Date of publication
Data Type
Int
Int
Varchar
Varchar
Numeric
Datetime
Size
50
50
26
Attributes
A_ID
Emp_ID
Emp_First_Name
Emp_Middle_Name
Emp_Last_Name
Sex
Address
City
State
Contact No.
Emp_D.O.B
D of Joining
Salary
Data Type
Int
int
Varchar
Varchar
Varchar
Bool
Varchar
Varchar
Varchar
Int
datetime
datetime
Numeric
Size
50
50
50
50
50
50
Process Logic:This page is design for the purpose of describing module graphically. At presently we
describe only one module but at the time of report submission, we describe all modules.
Start
27
User
No
Existin
g
Yes
Do login
No
correc
t
Yes
Stop
Testing Objectives:
1. Testing is the process of executing the program to find errors.
28
Testing Principles:
1. The test should be according to the customers requirement.
2. There should be a planning for testing before it starts.
3. The Pareto principle implies that 80 percent of all errors uncovered during testing
will likely be traceable to 20 percent of all program components.
4. Testing should begin in the small and progress toward testing in the large.
5. Exhaustive testing is not possible. It is impossible to execute every combination of
paths during testing. It is possible however, to adequately cover program logic and
to ensure that all conditions in the component level design have been exercised.
6. To be most effective, testing should be conducted by an independent third party.
Advantages:
1. It guarantees that all independent paths have been checked at least once.
2. It checks all logical errors that cannot be found by black box.
3. Typographical errors are random. The black box testing can find out typing error but
typing errors are rare in the program.
29
30
LOGIN PAGE
31
Software
i.
ii.
iii.
iv.
Future Scope:-
33
34
REPORT
35
User master
Medicine master
Course master
Expert for Ayurveda
Payment Gateway
Vendor master
E-books
Staff Master
37
User master:-
This module is designed for the purpose of storing all the information related to user. If a
user is registered then he/she have a valid ID and password and if a user is not registered
then first he perform registration. A registered user can see product details, book the
product and make payment as well as consult to expert.
14.
Medicine master:-
This module is designed for the purpose of storing all information of ayurvedic medicines,
which is available with our system. A registered user, see the entire available product and
give an order (if he she want to purchase). The system give this order to our registered
vender and make payment. The customer pay amount of product by our system through
credit card, prepaid card and internet banking.
15.
Course master:-
This module is designed for the purpose of storing the information of different course like
Ayurveda and panchakarma therapy, Ayurveda and beauty care, Ayurveda ways of life
style management, training program in yoga.
16.
This module is designed for the purpose of storing the information of experts. A valid user
can consult to expert for appropriate consultation and appointment. . The consultation can
be done in two ways-on line and off-line also. Through online a registered customer
38
17.
Payment gateway:-
This module is design for the purpose of storing the information about payment can be
done by different mode like credit card, prepaid card and internet banking.
18.
Vendor master:-
This module is design for the purpose of storing vendor information. If any vendor
registered with our website, first of all it fills the registration form and get a valid vender
I.D and after that the vender the vendor creates its own profile.
13.
E books :-
In this module there are so many types of books available this module is access by expert
and user as well as vendor also.
14.
Staff Master :-
This module is design for the purpose of storing all the information related to staff of our
organisation. The work for staff is as follows:He/she delivered the product to customer and he/she also manage for consultation between
user and our experts.
39
40
Software
v.
vi.
vii.
viii.
41
System Analysis
System Analysis by definition is a process of systematic investigation for the purpose of
gathering data, interpreting the facts, diagnosing the problem and using this information to
either build a completely new system or to recommend the improvements to the existing
system.
A satisfactory system analysis involves the process of examining a business situation with
the intent of improving it through better methods and procedures. In its core sense, the
analysis phase defines the requirements of the system and the problems which user is
trying to solve irrespective of how the requirements would be accomplished.
System development can generally be thought of having two major components: systems
analysis and systems design. In System Analysis more emphasis is given to understanding
the details of an existing system or a proposed one and then deciding whether the proposed
system is desirable or not and whether the existing system needs improvements. Thus,
system analysis is the process of investigating a system, identifying problems, and using
the information to recommend improvements to the system.
42
43
Feasibility Study
Feasibility is the determination of whether or not a project is worth doing. The process
followed in making this determination is called a feasibility study.
Types of feasibility
I.
II.
III.
solution?
Economic Feasibility: - It is the measure of cost effectiveness of the project. The
economic feasibility is nothing but judging whether the possible benefit of solving
IV.
V.
VI.
one.
Legal Feasibility: - Legal feasibility studies issues arising out of the need to the
development of the system. The possible consideration might include copyright law,
VII.
45
more
than
one
technique
for
investigation.
Interview
This method is used to collect the information from groups or individuals. Analyst selects
the people who are related with the system for the interview. In this method the analyst sits
face to face with the people and records their responses. The interviewer must plan in
advance the type of questions he/ she is going to ask and should be ready to answer any
type of question. He should also choose a suitable place and time which will be
comfortable
for
the
respondent.
The information collected is quite accurate and reliable as the interviewer can clear and
cross check the doubts there itself. This method also helps gap the areas of
misunderstandings and help to discuss about the future problems. Structured and
unstructured are the two sub categories of Interview. Structured interview is more formal
interview where fixed questions are asked and specific information is collected whereas
unstructured interview is more or less like a casual conversation where in-depth areas
topics are covered and other information apart from the topic may also be obtained.
46
Record
View
The information related to the system is published in the sources like newspapers,
magazines, journals, documents etc. This record review helps the analyst to get valuable
information
On-Site
about
the
system
and
the
organization.
Observation
Unlike the other fact finding techniques, in this method the analyst himself visits the
organization and observes and understand the flow of documents, working of the existing
system, the users of the system etc. For this method to be adopted it takes an analyst to
perform this job as he knows which points should be noticed and highlighted. In analyst
may observe the unwanted things as well and simply cause delay in the development of
the new system.
47
Scheduling
Gantt chart:
Gantt chart is a project control technique that can be used for several purposes including
scheduling and planning. Gantt chart is also known bar chart with each box representing
an activity.
We estimated the no. of weeks required for each as follows :
Wee
k1
Week
2
Wee
k3
TASKS
Requirements
Gathering
SRS Creation
Low Level Design
High Level Design
(Interface, Data
Design)
Procedural Design
Coding
Testing(Module and
Integrated)
Implementation
48
Days 1-6
Require
Days 9-12
Days 6-9
ments
Low Level
Design
SRS
Creation
Gatherin
g
Days 12-16
High Level Design
(Interface, Data
design)
Procedural
Days 16-23
Design
Coding
Days 23-48
Implementatio
n
Days 54-56
Testing (Module
and Integrated)
Days 48-54
Requirements of SRS: - The SRS should specify only the external system
behavior and not the internal details. It also specifies any constraints imposed on
implementation. A good SRS is flexible to change and acts as a reference tool for
system developer, administrator and maintainer.
Characteristics of a SRS
a.
b.
c.
d.
e.
f.
51
2. Information Description: - With the help of this website we can avail the ayurvedic
treatment very easily. People can easily take the knowledge of Ayurveda from this website.
They can also get knowledge on home remedies. They can read E- books related to
52
2. Function Description: - This system works with the help of following modules
User master
Medicine master
Course master
Expert for Ayurveda
Payment Gateway
Vendor master
E-books
Staff Master
53
User master:-
This module is designed for the purpose of storing all the information related to user. If a
user is registered then he/she have a valid ID and password and if a user is not registered
then first he perform registration. A registered user can see product details, book the
product and make payment as well as consult to expert.
2. Medicine master:This module is designed for the purpose of storing all information of ayurvedic medicines,
which is available with our system. A registered user, see the entire available product and
give an order (if he she want to purchase). The system give this order to our registered
vender and make payment. The customer pay amount of product by our system through
credit card, prepaid card and internet banking.
3. Course master:This module is designed for the purpose of storing the information of different course like
Ayurveda and panchakarma therapy, Ayurveda and beauty care, Ayurveda ways of life
style management, training program in yoga.
4. Expert for Ayurveda:This module is designed for the purpose of storing the information of experts. A valid user
can consult to expert for appropriate consultation and appointment. . The consultation can
be done in two ways-on line and off-line also. Through online a registered customer
54
7. E books :In this module there are so many types of books available this module is access by expert
and user as well as vendor also.
8.
Staff Master :-
This module is design for the purpose of storing all the information related to staff of our
organisation. The work for staff is as follows:He/she delivered the product to customer and he/she also manage for consultation between
user and our experts.
55