Ayurveda Report

CHAPTER 1
Synopsis
Page 1
1.1 INTRODUCTION
Ayu means life and Veda means knowledge, and so Ayurveda is often referred to as the "Science of
Life" - however it is more an instruction for enhancing life and is both a living system of medicine
and one of the oldest continuously practiced in the world. Ayurveda is the traditional health system
in India and is more than 5,000 years old. It uses a constitution based model (the doshas) for
determining your state of health.
Thousands of years ago, Indias Rishis and seers observed the rhythms of the universe and the
interaction of the flow of energy throughout the body/mind during deep states of meditation these
insights form the basis of Ayurveda and were documented in ancient Indian texts such as
the Charaka Samhita.
They realized that good health can be maintained through diet and lifestyle, and the use of herbs and
minerals. The principles of Ayurvedic medicine and the harmony between mind and body have been
documented and practiced in India for thousands of years.
Ayurveda is based on the premise that the universe is made up of five elements: air, fire, water, earth
and ether. These elements are represented in humans by three "doshas", or energies: Vata,
Pitta and Kapha. When any of the doshas accumulate in the body beyond the desirable limit, the
body loses its balance. Every individual has a distinct balance, and our health and well-being depend
on getting a right balance of the three doshas ("tridoshas"). Ayurveda suggests specific lifestyle and
nutritional guidelines to help individuals reduce the excess dosha.
Ayurveda emphasizes prevention of disease, rejuvenation of our body systems, and extension of life
span. The profound premise and promise of Ayurveda is that through certain practices, not only can
we prevent heart disease and make our headaches go away, but we can also better understand
ourselves and the world around us, live a long healthy life in balance and harmony, achieve our
fullest potential, and express our true inner nature on a daily basis.
Ayurveda provides an integrated approach to preventing and treating illness through lifestyle
interventions and natural therapies. It is based on the view that the elements, forces, and principles
that comprise all of nature - and that holds it together and make it function - are also seen in human
beings. In Ayurveda, the mind (or consciousness) and the body (or physical mass) not only influence
each other - they are each other. Together they form the mind-body. The universal consciousness is
an intelligent, aware ocean of energy that gives rise to the physical world we perceive through our
five senses. Ayurvedic philosophy and practices link us to every aspect of ourselves and remind us
that we are in union with every aspect of nature, each other, and the entire universe.
There can be no mental health without physical health, and vice versa. In Ayurveda, symptoms and
diseases that could be categorized as mental thoughts or feelings are just as important as symptoms
Page 2
and diseases of the physical body. Both are due to imbalances within a person, and both are treated
by restoring the natural balance mentally and physically. In Ayurveda your whole life and lifestyle
must be in harmony before you can enjoy true wellbeing. Lifestyle interventions are a major
Ayurvedic preventive and therapeutic approach.
The research base is growing concerning the physiological effects of meditative techniques and yoga
postures in Indian medical literature and Western psychological literature. Published studies have
documented reductions in cardiovascular disease risk factors, including blood pressure, cholesterol,
and reaction to stress, in individuals who practice Ayurvedic methods.
1.2 TITLE OF PROJECT

Ihave given title to my project as Ayurveda and Ayurvedic Rasayans because in
todays busy life no one have time to take care of itself and thus suffer from lots of
unwanted diseases. By this website Ayurveda comes to their door steps to give
them natural life with home remedies and herbal products.
1.3 OBJECTIVES
There are many objectives behind the idea of this website:
Create a Web application to be used for online information about Ayurvedic medicines.
Use ASP.NET and SQL Server technology to create strong and secured database connectivity.
Incorporate the server software within the code.
Runtime package and deployment instructions are given.
Page 3
1.4 SCHEDULE OF ACTIVITIES
SNO.
ACTIVITY
DATE SCHEDULED
1.
Research on the project
Aug 1, 2014 Aug 15, 2014
2.
Analyzing and gathering of the
Aug 15, 2014-Aug 20, 2014
data
3.
Designing of modules
Aug 20, 2014- Sept 5, 2014
4.
Database creation and
Sept 5, 2014-Sept 10, 2014
connectivity
5.
Testing
Sept 10, 2014-Sept 20, 2014
6.
Completion of project
Till Sept 30, 2014
7.
Synopsis
Aug. 25, 2014 - Aug. 29, 2014
8.
SRS
Sept. 15, 2014 - Sept. 19, 2014
9.
Report
Oct. 6, 2014 - Oct. 10, 2014
Page 4
1.5 CONCLUSION
I have included the following in my synopsis:
Abstract, Introduction,Revision History, Objectives, Schedule of activities, Conclusion,

Achievement till date, Remaining works
From the above things my project has been approved by my guide
Page 5
1.6 ACHEIVEMENT TILL DATE
SNO.
ACTIVITY
DATE SCHEDULED
1.
Research on the project
Aug 1, 2014 Aug 15, 2014
2.
Analyzing and gathering of the
Aug 15, 2014-Aug 20, 2014
data
3.
Started designing of modules
Aug 20, 2014 - Aug 24, 2014
4.
Synopsis
Aug 25, 2014 - Aug 29, 2014
Page 6
1.7 REMAINING WORKS
SNO.
ACTIVITY
1.
Designing of modules
2.
Database creation and connectivity
3.
Testing
4.
Completion of project
5.
SRS
6.
Report
Page 7
Page 8
CHAPTER 2
Software Requirements
Specification
Page 9
2.1 Introduction
2.1.1 Purpose
The purpose of this SRS document is to specify software requirements of the Ayurvedic Rasayana. It is
intended to be a complete specification of what functionality Ayurvedic Rasayana website provides. The
main purpose of the system is to make people know about Ayurvedic Rasayans, Ayurvedic treatements
and its medical benefits. Specific design and implementation details will be specified in a future
document.
1. Ayurvedic Rasayans help to maintain the health balances.
2. Database maintained by this system usually contains the patients personal and their health
related information. It focuses on storing and processing (insertion, updation) by using web
pages.
3. Generates patients information in formatted html tables, generates the payment invoice.
4. Generate patients Personal Detail Report.
5. Generate patients payment Status Report.
The purpose is Preservation to health of healthy person and treating ailments with breaking causative
factors of pathogenesis. Our main objective of making people happy and healthy through authentic Ayurvedic
treatment delivered at their doorstep is a direct response to the ailments and disorders such as diabetes, arthritis, asthma,
obesity, hypertension, spondilities, piles, skin problems, sexual disorders, etc. - affecting the global community today, most
of which do not have any impactful or sustainable treatment in modern medicine.
2.1.2 Document Conventions

In this document there is different typography for different text including heading and subheading as follows:
Font-type: TIMES NEW ROMAN

Font size for heading: 18
Font size for sub-heading: 14
Font size for text: 12
2.1.3 Intended Audience and Reading Suggestions

The document will also include the specific requirements needed. These will include the functions, performance, design, and
software attributes. This document is organized in a logical manner and is easy to follow. Readers should refer to the table of
contents, appendices, or index if looking for something in specific. Otherwise, reading this document from start to finish will
start with a vague description and get more specific and detailed as changing sections and reading further.
Page 10
2.1.4 Project Scope

This projects aim is to automate the system, pre-checking the inclusion of all required. These criteria
include the ranking of their university, their grade at said university and their language grade Certificate. The data
used by the system is stored in a database that will be the centre of all information held about students and the base
for the remainder of the process after the initial application has been made. This enables things to be simplified and
considerably quickened, making the jobs of the people involved easier. It supports the current process but
centralizes it and makes it possible for decisions to be made earlier and easier way.
2.1.5 References
Diseases Information: www.jiva.com
Medicine information: www.baidyanath.com
Images: www.google.co.in
2.2 Overall Description

2.2.1 Product Perspective
This product is a self-contained product. The project will make use of a database and a web
server that can be accessed with any web browser. There are 3 types of users on the
system: guests, registered users and administrator. Before a user can make use of the full
functionality of the site, the user has to register. The user will have to enter some personal
information in a form in order to do this.
Both guests and users can browse the different auctions, but only registered users can
purchase products or place their order. Users can browse through with categories or tags.
Users can also search for a specified diseases. When a user places an order, he or she also
has to specify payment methods.
One of these methods is through credit/debit card, cash on delivery.
Administrators have some extra functionality, they can manage the users and products.
2.2.2 Product Features

Some of the features are identified for the software. They are listed below:
View Course Informations: The patients must able log as patients and see all details about course without any
constraints.
Apply for Course: The patient can able to purchase products or register them online.
Verification of Marks: The system must allow the student verify marks through online.
Advanced Enquiry support: Enable the patients to ask and clear doubts.
Page 11
Online Counselling: The administrator can able to send the call letters for the short listed patients, if the patient
notable contact directly respective authorized persons, than the system must facilitate the online Counselling.
Report Generation: The system supports generation of reports based on different criteria.
Record maintenance: The system also must keep track the statistical reports of daily activities of the patient Registration
Process.
Online feedback: Enable the patient to write the feedback through online in effective way.
2.2.3 User Classes and Cha-racteristics

User Classes
Some of the users identified for this system through use case analysis are listed below:
Patients
Data entry operators
Consulters
Administrators
Authorities
User Characteristics
The Patient should have the basic idea to operate (use) the system and he already has the experience to work in the internet
(browser). Default Language is English.
This system will be used in Three User Modules which are Administrator, consultants and Patients. As all
of these have different requirements the modules are designed to meet their needs and avoid any type of
confusion. The Uses of all three User Modules have been described below.
1. U s e r
can
do
the
Administrator Module
Add & Edit consultant
Add Receipt for User
Edit User
View Bills
Generate Reports.
following
functions
in
2. U s e r c a n d o t h e f o l l o w i n g f u n c t i o n s i n t h e P a t i e n t M o d u l e
Give Feedback
View Response
Page 12
the
2.2.4 Operating Environment

HARDWARE
Hard disk: 500 GB
RAM: 4 GB
Processor: core i5 3rd generation
SOFTWARE
Operating System: Windows 8.1
DEVELOPMENT TOOLS
Microsoft Asp.NET 2010 Using VB and AJAX
Microsoft SQL Server 2005
DOCUMENTATION AND PRESENTATION TOOLS
Microsoft Word 2013
Microsoft Power Point 2013
2.2.5 Design and Implementation Constraints

Some of the design and implementation constraints identified are listed below:
Patient is not allowed to register for more than one time.
Patient not has any rights to edit any data in the system.
Patient pays the product payment in VPP or COD or MO.
This system is not support distributed database Facility.
System is limited to HTTP/HTTPS Protocols.
2.2.6 User Documentation

Online documentation facility is available for the Patients to assess them for the easy use.
A specific document should be prepared for the maintenance of the system and should say the system in easiest
way.
2.2.7 Assumptions and DependenciesMedicine Courses are already created and informations available for use.
Roles and responsibilities are already established.
Administrator is already created.
Database is created for use.
Page 13
2.3 System Features

The following are the major features provided by the system.
2.3.1 USER REGISTRATION

2.3.1.1 Description and Priority
This allows a user to be a member enables him to purchase of items and participate in
the community forum. This is an essential part of the system of high priority as
it adds new customer.
2.3.1.2 Stimulus/Response Sequences
a.
b.
c.
d.
e.
The user selects the sign up link to get the registration form and after
following the instruction fills in the required information to create his/her profile.
Client side validation will be done for checking provided information.
The user will be asked for a login and password
On activation the user is now registered.
2.3.1.3 Functional Requirements

a.
b.
c.
d.
e.
f.
g.
h.
A unique user ID.

Password.
Name.
Address.
Email.
Contact.
Security Question.
Security Answer.
2.3.2 SEARCHING
2.3.2.1 Description and priority
Any user can search for article based on category, cost and other parameters .This
will be the top priority module as it is very essential for a prospective buyer to find the article
he/she is looking for.
2.3.2.2 Stimulus/Response Sequences (Functional requirement)

a. The user can search for the products from various categories according to the
diseases.
b. There is a particular product for a particular disease with given information so user
cannot be confused from various products.
a. Product knowledge.
Page 14
2.3.3 BUYING
The buyers will be able to buy any item available. This is core part of this web application.
2.3.3.2 Stimulus/Response Sequences(Functional requirement)

a. The buyer searches the item he/she wants to buy.
b. He/She selects the item he wants to buy from the list of items he selected and make
payment.
a. Registration.
2.3.4 FEEDBACK/QUERY
The users will be able to give feedback or can ask any query based on our services.
2.3.3.2 Stimulus/Response Sequences (Functional requirement)

a. The user fill all the field requirements and writes there message in the textbox.
a. Email Address.
b. User ID.
c. Message.
2.4 External Interface Requirements

2.4.1 User Interfaces
Here you can see the Client interface forms:
1. REGISTRATION: Registration form include various fields to be filled by the patients,
registration form include Name, Address, Contact no., User_ID, Password, Security Question,
Security Answer, Email.
2. LOGIN: This is the short form of the registration page. The registration is done once but to
access all the information one need to login. Login includes two fields i.e. User_ID and
Password.
3. PASSWORD: With the help of this page user can change its password.
4. FEEDBACK: Feedback form is used to take feedback from the user for the improvement of
the system, and make user more comfortable to give their views about our services. To give a
feedback user must have to login itself from required User_ID and Password and then he/she
can give their feedback for our services.
Page 15
5. QUERY: Query form is used to solve the different queries of a user so that everyone should
be satisfied and if they have any doubt in their mind, they can ask freely for any support.
Query section includes User_ID, Name, Email, Message subject, Message.
In this website there are three users, first one is the student and the second is the admin and
the third is bill operator. We can say that admin and bill operator are also a user. The pages
where admin will interact are:
1. LOGIN: This is the page where admin will enter his/her user id and password and after that
he can access the website. The login page will permit the admin to make any changes to the
website required. For example, adding Products, deleting Products, etc.
2. USER DETAILS: This will view all the user details to the admin.
3. DELETE PRODUCTS: Through this page admin can delete any Product.
4. VIEW PRODUCTS: This page assures admin to view all the Products therein.
5. ADD PRODUCTS: The admin can add new or more Products to the website.
6. DELETE PRODUCTS: The admin can delete Products through this page.
There is another user which is the Bill Operator, who will manage all the Bills.
1. LOGIN: This is the page where Bill Operator will enter his/her user id and password and
after that he can access the website. The login page will permit the Bill Operator to make
Bills.
2.4.2 Hardware Interfaces
REGISTRATION FORM, LOGIN FORM, FEEDBACK FORM, QUERY FORM

Registration form is to be filled with the help of:
A normal keyboard.
Monitor: SVGA color.
Standard Cabinet Configuration
Touchpad: To navigate from one section to another
MOUSE: P2S/serial
Keyboard: Keyboard is used to write in required fields on the form displayed on the webpage.
Mouse or touchpad: Mouse or touchpad are used to navigate from one place to another and click on
the buttons below the form to submit your entries in the form.
Monitor: Monitor is used to display your page and form on the webpage of your website.
Page 16
2.4.3 Software Interfaces

Front end
Visual Studio .Net 2005 Enterprise Edition, HTML, CSS
Back end
SQL Server 2000 Enterprise Edition.
Middleware/Server
Internet Information Server 5.0 (IIS)
IDE
Visual Studio .Net Framework (Minimal for Deployment)
Browser
Best result on Mozilla or Firefox
Operating System
WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)
2.4.4 Communications Interfaces

The connection between the client and the server uses Connection oriented Communication,
via HTTP-Hyper-text Transfer Protocol, implements reliable delivery of messages.
Connection-oriented communication makes programming easier because the protocol
includes mechanisms for detecting and handling errors and an acknowledgement mechanism
between client and service. Again we assume that the readers is not interested of how that is
implemented into the program at this phase so there will be no more details of this now.
Page 17
2.5 Other Nonfunctional Requirements

2.5.1 Performance Requirements
Some performance requirements identified is listed below:
The database shall be able to accommodate a minimum of 10,000 records of patients.
The software shall support use of multiple users at a time.
There are no other specific performance requirement that will affect development.
2.5.2 Safety Requirements

Some of the attributes identified for the safety is listed below:
All data storage for user variables will be committed to the database at the time of entry.
Data corruption is prevented by applying the possible backup procedures and techniques.
2.5.3 Security Requirements

Some of the factors that are identified to perfect the software from accidental or malicious
access, use, modification, destruction, or disclosure are described below. Specific requirements
in this area could include the need to:
Utilize certain cryptographic techniques.
Keep specific log or history data sets.
Assign certain functions to different modules
Restrict communications between some areas of the programs.
Check data integrity for critical variables.
Later version of the software will incorporate encryption techniques in the user authentication
process.
The software will include an error tracking log that will help the user understand what error
occurred when the application crashed along with suggestions on how to prevent the error from
occurring again.
Communication needs to be restricted when the application is validating the user. (i.e., using
https).
2.5.4 Software Quality Attributes

There are a number of attributes of software that can serve as requirements. It is important that
required attributes by specified so that their achievement can be objectively verified. The
following items will provide a partial list of examples.
The input system will allow for inputting numbers, operands, special symbols and letters of the
alphabets.
Page 18
2.6 Other Requirements

HARDWARE REQUIREMENTS
2.6.1 Development time

Processor (P4 or Advanced)
Keyboard - any
Mouse/Touch pad
Memory minimum 8 GB(Approx.)
Other standard cabinet assembly
2.6.2 Deployment time
Processor (P3 or Advanced)
Keyboard - any
Mouse/Touch pad
Memory minimum 8 GB(Approx.)
Other standard cabinet assembly
Page 19
2.7 SOFTWARE REQUIREMENTS
2.7.1 Development time

Operating system (Windows xp/ Vista/ 7/ 8)
Visual studio 2005/ 2008/ 2010/ 2012
Microsoft Sql server 2005/ 2008/ 2010
Browser any
Microsoft Office (2007 or Advance)
2.7.2 Deployment time
Operating system (any)
Browser (any)
Page 20
CHAPTER 3
Software Design Specification
Page 21
3.1 Introduction
Ayu means life and Veda means knowledge, and so Ayurveda is often referred to as the "Science
of Life" - however it is more an instruction for enhancing life and is both a living system of
medicine and one of the oldest continuously practiced in the world. Ayurveda is the traditional
health system in India and is more than 5,000 years old. It uses a constitution based model (the
doshas) for determining your state of health.
Thousands of years ago, Indias Rishis and seers observed the rhythms of the universe and the
interaction of the flow of energy throughout the body/mind during deep states of meditation
these insights form the basis of Ayurveda and were documented in ancient Indian texts such as
the CharakaSamhita.
They realized that good health can be maintained through diet and lifestyle, and the use of herbs
and minerals. The principles of Ayurvedic medicine and the harmony between mind and body
have been documented and practiced in India for thousands of years.
Ayurveda is based on the premise that the universe is made up of five elements: air, fire, water,
earth and ether. These elements are represented in humans by three "doshas", or energies: Vata,
Pitta and Kapha. When any of the doshas accumulate in the body beyond the desirable limit, the
body loses its balance. Every individual has a distinct balance, and our health and well-being
depend on getting a right balance of the three doshas ("tridoshas"). Ayurveda suggests specific
lifestyle and nutritional guidelines to help individuals reduce the excess dosha.
Ayurveda emphasizes prevention of disease, rejuvenation of our body systems, and extension of
life span. The profound premise and promise of Ayurveda is that through certain practices, not
only can we prevent heart disease and make our headaches go away, but we can also better
understand ourselves and the world around us, live a long healthy life in balance and harmony,
achieve our fullest potential, and express our true inner nature on a daily basis.
Ayurveda provides an integrated approach to preventing and treating illness through lifestyle
interventions and natural therapies. It is based on the view that the elements, forces, and
principles that comprise all of nature - and that holds it together and make it function - are also
seen in human beings. In Ayurveda, the mind (or consciousness) and the body (or physical mass)
not only influence each other - they are each other. Together they form the mind-body. The
universal consciousness is an intelligent, aware ocean of energy that gives rise to the physical
world we perceive through our five senses. Ayurvedic philosophy and practices link us to every
aspect of ourselves and remind us that we are in union with every aspect of nature, each other,
and the entire universe.
There can be no mental health without physical health, and vice versa. In Ayurveda, symptoms
and diseases that could be categorized as mental thoughts or feelings are just as important as
symptoms and diseases of the physical body. Both are due to imbalances within a person, and
both are treated by restoring the natural balance mentally and physically. In Ayurveda your
whole life and lifestyle must be in harmony before you can enjoy true wellbeing. Lifestyle
interventions are a major Ayurvedic preventive and therapeutic approach.
Page 22
The research base is growing concerning the physiological effects of meditative techniques
and yoga postures in Indian medical literature and Western psychological literature.
Published studies have documented reductions in cardiovascular disease risk factors,
including blood pressure, cholesterol, and reaction to stress, in individuals who practice
Ayurvedic methods.
3.2 Document Description
3.2.1
Introduction
3.2.1.1 Purpose :
The purpose of this SRS document is to specify software requirements of the Ayurvedic
Rasayana. It is intended to be a complete specification of what functionality Ayurvedic Rasayana
website provides. The main purpose of the system is to make people know about
AyurvedicRasayans, Ayurvedictreatements and its medical benefits. Specific design and
implementation details will be specified in a future document.
6. AyurvedicRasayans help to maintain the health balances .
7. Database maintained by this system usually contains the patients personal and their health
related information. It focuses on storing and processing (insertion, updation) by using web
pages.
8. Generates patients information in formatted html tables, generates the payment invoice.
9. Generate patients Personal Detail Report.
10. Generate patients payment Status Report.
The purpose is Preservation to health of healthy person and treating ailments with breaking
causative factors of pathogenesis. Our main objective of making people happy and healthy through authentic
Ayurvedic treatment delivered at their doorstep is a direct response to the ailments and disorders such as diabetes,
arthritis, asthma, obesity, hypertension, spondilities, piles, skin problems, sexual disorders, etc. - affecting the global
community today, most of which do not have any impactful or sustainable treatment in modern medicine.
3.2.1.2 SCOPE:
This projects aim is to automate the system, pre-checking the inclusion of all required. These
criteria include the ranking of their university, their grade at said university and their language grade
Certificate. The data used by the system is stored in a database that will be the centre of all information held
about students and the base for the remainder of the process after the initial application has been made. This
enables things to be simplified and considerably quickened, making the jobs of the people involved easier. It
supports the current process but centralizes it and makes it possible for decisions to be made earlier and easier
way.
This website is for every human reach and any human who does or does not feel comfortable with allopathic
or homeopathic can take advantage of ayurvedic products
Page 23
3.2.1.3 Intended Audience:

This document is intended for any individual user, developer, tester, project manager or
documentation writer that needs to understand the basic system architecture and its
specifications.
Here are the potential uses for each one of the reader types:
Developer: This document is also intended for the developers of the project so that
they can check and modify the contents of the project.
User: This project is for the persons who want to lodge their complaint. They can
also view the different services provided by the developers of the website.
Tester: The tester needs this document to validate that the initial requirements of this
Program actually corresponds to the executable program correctly.
This project has 1.0 version i.e., it is self-contained project and not the expansion of
any other project.
Pre requisite documents to this document are as :
Synopsis
SRS
3.2.2 System Overview

Ayurveda Rasayana is built on Asp.NET, Crystal Reports and SQL Server 2005. The Web
application is built to serve the following areas.
To make treasury of Indias own Ayurvedic products consume by people who consume them as
a medicine fast, reliable, and freely.
Hosting on the Intranet can provide a approach to natural products and acts as a channel for any
individual.
Registration of users can be used to generate revenue and thus can be profited form the system.
The database is self explanatory as the code.
3.3 Design Considerations

3.3.1 Assumptions and Dependencies
These may assumptions such as:
Prepared in ECLIPSE and ORACLE.
Run in any operating system.
End user who is most benefitted by the site is the victim of the indifferent behavior of the
department.
Page 24
3.3.2 General Constraints

Oracle 9.0.1.1.1 server is used as database as this software is developed for general use in a
variety of information management applications. It is not developed or intended for use in
any inherently dangerous applications, including applications which may create a risk of
personal injury. If you use this software in dangerous applications, then you shall be
responsible to take all appropriate fail-safe, backup, redundancy, and other measures to
ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability
for any damages caused by use of this software in dangerous applications. Oracle is a
registered trademark of Oracle Corporation and/or its affiliates.
The following are the advantages of choosing Oracle Database.
Portability
Oracle is ported to more platforms than any of its competition, running on more than 100
hardware platforms and 20 networking protocols. This makes writing an Oracle application
fairly safe from changes of direction in hardware and operating system, and therefore a safe
bet. One caveat, however, is that applications using some constructs (such as field level
triggers) may have to be reworked when porting them to a block mode environment. You
can also develop a fairly fully featured application with little knowledge of the underlying
OS. Personally, I have developed applications on OS systems barely knowing how to copy
and edit text files.
Market Presence
Oracle is by far the largest RDBMS Vendor, and spends more on R&D than most of its
competitors earn in total revenue. Oracle has the largest independent RDBMS market share
in VMS, UNIX and OS/2 Server fields. This market clout means that you are unlikely to be
left in the lurch by Oracle and there are always lots of third party interfaces supported and
also, proficient staff are relatively easy to get.
Version Changes
Oracle seem very good at informing you in detail as to what is not going to be supported in
the next major release and usually have some knob you can twiddle for good backward
compatibility, or simply leave it working, but with "don't use this, use xxxx instead" warnings
in the manual. Backward compatibility is very good meaning you will not be in for an
application re-write when you upgrade the DBMS. [Compare this with the Ingres v5->6
OSQL upgrade from hell.] I've worked with Oracle since V4 Beta and have never been in for
nasty surprises as far as syntax goes. However, see "Version Changes" under disadvantages.
Backup and Recovery
Oracle provides industrial strength support for on-line backup and recovery and good
software fault tolerance to disk failure. You can also do point-in-time recovery. Of course,
you need the archive mechanisms and storage space to do this, but Oracle supports
continuous archiving to tape devices spanning multiple volumes.
Page 25
Performance
Speed of a *tuned* Oracle database and application is quite good, even with large databases.
Oracle refer to >100 GB databases and have personal experience administering 10 GB
databases. The performance is not only "raw", but includes consideration of performance
with locking and transaction control.
Server used to support to run website:
1. HTML/DHTML: As an essence to give pages dynamic look, feel and appeal.

Interface/protocol requirements
For the communication protocol the program needs these protocols to be installed:
Tcp for the client to connect to the server in online mode.
Storing devices (flash, optical disks etc.) for the buyer to take a test in offline mode.
Also in case that the website Server runs behind a firewall the appropriate ports must be port
forwarded or port triggered for the buyer to connect.
Interoperability Requirements
It is effort to require modifying operational program. The whole website should be
made using independent modules so that any changes done in 1 module should not be
effected the other one and new modules can be added easily to increase functionality.
Data repository and distribution requirements

This website will help the person , admin to view forward complaint. Only authorized
person can access related details. The organization will register themselves on the
website for view complaint. Organizations can change their information regarding
themselves. The user can login through their ID and PASSWORD and buy property.
Admin will be responsible for updating the site.
Network communications
Setting up the server into server mode requires that there will be open ports for
accepting connections from the clients. The connection between the client and the
server uses Connection oriented Communication, via TCP/IP-Transfer Control
Protocol/Internet Protocol, implements reliable delivery of messages . Connectionoriented communication makes programming easier because the protocol includes
mechanisms for detecting and handling errors and an acknowledgement mechanism
between client and service. Again we assume that the readers is not interested of how
that is implemented into the program at this phase so there will be no more details of
this now.
Page 26
Verification and validation requirements (testing)

The basic objective in verification and validation of software requirements and design
specifications are to identify and resolve software problems and high risk issues early
in he software life-cycle. There is very little agreement in the software field on the
definitions of the terms verification and validation. Therefore, this paper begins by
defining these terms rather carefully, and by explaining how each one fits into the
software life-cycle. It then discusses the basic V & V criteria for software requirements
and design specifications: completeness, consistency, feasibility, and testability.
Other means of addressing quality goals

Availability: Checking that the system always has something to function and always
pop up error messages in case of component failure. In that case the error messages
appear when something goes wrong so to prevail availability problems. Usability:
Checking that the system is easy to handle and navigates in the most expected way
with no delays. In that case the system program reacts accordingly and transverses
quickly between its states. Functionality: Checking that the system provides the right
tools for editing question databases, creating session tests and analyzing the test
sessions. In that case the tools that the Database editor provides are the ones that
provide that attribute. Other requirements described in the requirements specification.
3.3.3 Goals and Guidelines

The main goal of the system is to automate the process carried out in the organization with
improved performance and realize the vision of paperless work. Some of the goals of the
system are listed below:
Manage all details of users or patients who registered for the Ayurvedic medicine course and
send appropriate details about the course to the patients.
Create users or patients accounts and maintain the datas effectively.
View all the details of the patients.
Create the statistical reports to facilitate the finance department work.
Manage the details of hospitality.
Activities like updating, modification, deletion of records should be easier.
The System must support Undo the Previous activities if any Problem Occurs.
3.3.4 Development Methods

The establishment and use of sound engineering principles in order to obtain economically
developed software that is reliable and works efficiently on real machines is called software
engineering.
Software engineering is the discipline whose aim is:
1. Production of quality software
2. Software that is delivered on time
Page 27
3. Cost within the budget

4. Satisfies all requirements
Software process is the way in which we produce the software. Apart from hiring smart,
knowledgeable engineers and buying the latest development tools, effective software
development process is also needed, so that engineers can systematically use the best
technical and managerial practices to successfully complete their projects.
A software life cycle is the series of identifiable stages that a software product undergoes
during its lifetime. A software lifecycle model is a descriptive and diagrammatic
representation of the software life cycle. A life cycle model represents all the activities
required to make a software product transit through its lifecycle phases. It also captures the
order in which these activities are to be taken.
LIFE CYCLE MODELS
There are various life cycle models to improve the software processes.
WATERFALL MODEL
PROTOTYPE MODEL
ITERATIVE ENHANCEMENT MODEL
EVOLUTIONARY MODEL
SPIRAL MODEL
Our Project Follows the Waterfall Model

THE WATERFALL MODEL
The steps of the typical Waterfall Model are:
Requirement Definition
System & Software Design
Implementation
I n t e g r a t i o n & S ys t e m T e s t i n g
Operation and Maintenance
Page 28
Figure 3.3.3.1
1.1 The Waterfall Model
There have been some variations from the typical waterfall model for this project lifecycle. They are:
1. Maintenance has been omitted from the current project.
2. Not all testing methods which are present in theoretical model are implemented.
Waterfall Model is the simplest model with each phase having a well defined starting and ending
point, with identifiable deliveries to the next phase.
The model consists of six distinct stages, namely:
Requirement Analysis Phase:

The problem is specified along with the desired service objective (goals) also the constraints are
identified.
Specification Phase:
The system specification is produced from the detailed definitions requirement analysis phase.
This document should clearly define the product to dos.
System and Software design Phase:

The system specifications are translated into a software representation.
The software engineer at this stage is concerned with:
Page 29
Data structure
Software architecture
Algorithmic detail, and
Interface representations
The hardware requirements are also determined at this stage along with a picture of the overall
system architecture. By the end of this stage the software engineer should be able to identify the
relationship between the hardware, software and the associated interfaces. Any faults in the
specification should ideally not be passed Down stream.
Implementation and Testing Phase:

The designs are translated into the software domain also detailed documentation from the design
phase can significantly reduce the coding effort. Testing at this stage focused on making sure
that any errors are identified and that the software meets its required specification.
Integration and System Testing Phase:

All the program units are integrated and tested to ensure that the complete system meets the
software requirements. After this stage the Software is delivered to the customer. The software
product is delivered to the client for acceptance testing.
Maintenance Phase:
This is usually the longest and the last stage of the software. In this phase the software is updated
to meet the changing customer needs, ability to accommodate changes in the external
environment, correct errors and oversights previously undetected in the testing phases, enhancing
the efficiently of the software.
REASONS FOR CHOOSING WATERFALL MODEL:
In this model, a detailed checking is done at each and every step by software quality assurance
(SQA) group and also by the clients. That is why it involves less risk of rejection by clients.
It is very easy to understand and implement.
It is documentation driven, that is, documentation is produced at every stage.
Testing is inherent to every phase of the waterfall model. So there is no need for a separate
testing phase.
Good progress tracking due to clear development stages.
Getting the requirements and design out of the way first also improves quality; it's much easier to
catch and correct possible flaws at the design stage.
Finally, the first two phases end in the production of a formal specification, the waterfall
model can aid efficient knowledge transfer when team members are dispersed in different
locations.
3.4 Architectural Strategies

Module design: The system design shows how Software will be structured to satisfy the
requirements identified during the analysis phase. The design process is a translation of
requirements into a description of the software structure, software components, interfaces and
data necessary for the implementation phase. The design phase provides a complete blueprint
for the implementation activity.
Page 30
System analysis begins by identifying the reports and the other outputs the system will
produce. Then the specific on each are pin pointed. Usually, designers sketch the form or
display as they expect it to appear when the system is complete. This may be done, on a paper
or computer display, using one of the automated tools available. The system design also
describes the data to be the input, calculated or stored. Individual data items and calculation
procedures are written in detail. The procedures tell how to process the data and produce the
output. The user, admin, auditor, services & complaint registration and login.
This process has different faces when its come to registration for user, complaint, authority
& auditor. Registration is needed for the user and authority to react on the complaint and get
the information about the complaint. This registration is being done by the user directly from
the website. After the registration process a unique login id will be given to the user. Admin
registration is previously from the database at the time of the creation of the site. The
proposed system contains the following main module processes:-
Registration
The simple registration are being done for user. The user has to provide all the information
that is being demanded in the registration form. All the fields given are mandatory to be
filled by the person who find the need to register himself/herself at the site. At the end when
user click on the submit button,if all the information are fine then he/she then is registered to
the site.
Login
Separate login table are maintained for auditor, administrator and user.
As the system is client dependent so proper user id and password based client system
is necessary to accomplish the fact. Whatever and however the system is to maintain
the client status and specific user enabled services as well as to track the clients
surfing for security and privacy reason.
Based on the login and the access rights granted by the administrator he is linked to
the appropriate page. If the user is not registered on the site, he is linked to the
Registration page.
A login status and log is maintained to find who and from where login-id for which
purpose.
Uploading The Updated Information

The site mentions about the details of the services provided in the site, which is being update
through specific services handling process by the authorized auditor of the site. Uploading
process is login based process. Details about different services and their respective
departments will be displayed on site and any person can search different services.
Page 31
Query register
This module is dedicated to register any query from the customers whenever they come to
compliant. The process of this module is divided into two sub processes in which one
registers the complete details of the customer who wants to submit the compliant, other
registers the complete details of the compliant
Monitoring Module
This module is dedicated to monitoring the complaints by searching the complaints and
updating the status of complaints at any time. The process of this module is divided into two
sub processes in which one searches for complaints and other updates the status..
Testing Method
System testing is done to find discrepancies between the system and its original objective,
current specifications and system documentation. For each project, testing is done at every
stage. Testing need is where errors remaining from all the previous phase must be detected.
Hence testing performs a very critical role for quality assurance and for ensuring the
reliability of software. During testing, the program to be tested is executed with a set of test
cases and is evaluated to determine if the program performs as expected.
Unit testing
Module
testing
Subsystem
testing
System
testing
Final
Testing
Figure 3.5.1
Page 32
Some of the commonly used terms associated with testing are explained briefly in following
lines:
a. Error=Error refers to the difference between actual output of software and the
correct output. In this interpretation, error is essentially a measure of the
difference between the actual and the ideal.
b. Fault=Fault is a condition that causes a system to perform a required function.
A fault is the basic reason for software malfunction and is synonymous with
the commonly used term bug.
c. Failure: Failure is inability of a system to perform a required function
according to its specifications. A software failure occurs if the behavior of the
software is different from specified behavior.
3.5 System Architecture

About System Architecture
Examination system was helpful to separate teaching and testing. It promoted teacher to make
the lesson planning and teach into class carefully it was also an important means of
evaluating the teaching effect otherwise its stimulated student to conscientiously study and
attend a lecture , to do their homework independently therefore the Online examination
system could improve teaching level by providing better technical support the online
examination system also provide online testing capability for student students could log in the
system any time , test themselves , understand their learning level ,adjust their learning
progress.
DATA FLOW DIAGRAM
A DFD also known as bubble chart , has the purpose of clarifying system requirements and
identifying major transformations. It shows the flow of data through a system. It is a
graphical tool because it presents a picture. The DFD may be partitioned into levels that
represent increasing information flow and functional detail. Four simple notations are used to
complete a DFD. These notations are given below:-
DATA FLOW
The data flow is used to describe the movement of information from one part of the system to
another part. Flows represent data in motion. It is a pipe line through which information
flows. Data flow is represented by an arrow.
DATA FLOW
PROCESS
A circle or bubble represents a process that transforms incoming data to outgoing data.
Process shows a part of the system that transforms inputs to outputs.
PROCESS
Page 33
EXTERNAL ENTITY
A square defines a source or destination of system data. External entities represent any entity
that supplies or receives information from the system but is not a part of the system.
EXTERNAL ENTITY
ENTITY
DATA STORE
The data store represents a logical file. A logical file can represent either a data store symbol
which can represent either a data structure or physical file on disk. The data store is used to
collect data at rest or a temporary repository of data. It is represented by open rectangle.
DATA STORE
OUTPUT
The output symbol is used when a hard copy is produced and the user of the copies cannot be
clearly specified or there are several users of the output.
OUTPUT
3.6 Policies and Tactics

Describe any design policies and/or tactics that do not have sweeping architectural implications
(meaning they would not significantly affect the overall organization of the system and its highlevel structures), but which nonetheless affect the details of the interface and/or implementation
of various aspects of the system. Such decisions might concern (but are not limited to) things like
the following:
Choice of which specific product to use (compiler, interpreter, database, library, etc. ...)
It will be coded in ASP .Net Framework 3.5 with Visual Basic. Visual Studio 2012 will
be required to compile.
Engineering trade-offs
None.
Coding guidelines and conventions
Page 34
Design Patterns will be used in the development. Visitor and State Desing patterns will
be applied on some of the modules.
The protocol of one or more subsystems, modules, or subroutines
TCP/IP network communication needs to be established for network module design. It

will be an online application where internet connection will be required.
The choice of a particular algorithm or programming idiom (or design pattern) to implement
portions of the system's functionality
Visitor and State Desing patterns will be applied on some of the modules. Strategy
desing pattern can also be used.
Plans for ensuring requirements traceability
SRS document was provided and all the requirements specified in the document have
been applied in the design. Also use cases are created to make sure that all the
functionality will be defined in the functions according to the requirements.
Plans for testing the software
All the feature set and needed requirements need to be tested with the scenarios
created. An additional test document will be provided.
Plans for maintaining the software
Every Quarter bugs will be reviewed. Any reported problems will be fixed. This
document will need to be updated if there are any new additional requirements
involved.
Interfaces for end-users, software, hardware, and communications
Online Gas Services system will require end-users to have internet access, user login
credentials, PC and a browser.
Hierarchical organization of the source code into its physical components (files and
directories).
How to build and/or generate the system's deliverables (how to compile, link, load, etc. ...)
Program will be compiled from the development machine and placed into the web server.
Visual Studio 2012, SQL Server 2010 are the two main server application required to be able
to run this web site.
Page 35
3.7 Detailed System Design
3.7.1
DFDs
ZERO LEVEL DFD
Login
Insert/Update
ExistingUse
r
Visiting
User
Information/Make
Payment
View
Give Feedback
Admin
Ayurveda &
Ayurvedic
Rasayans
Get User Condition Details

Insert/Delete
Bills
Makes Payment
Login
Report Generator
Figure 3.7.1.1
Page 36
Billing Operator
Figure 3.7.1.2
Page 37
Figure 3.7.1.3
Page 38
Figure 3.7.1.4
Page 39
Figure 3.7.1.5
Page 40
Figure 3.7.1.6
Page 41
3.7.2
ER DIAGRAM
Email
Address
Address
Contact
Name
Contact
User_Id
Name
User_Id
Makes
Login Type
Email
Bill Operator
Admin
Makes
Feedback
Gives
Login
Security answer
Thought
Login_Id
Password
User_Id
Security Question
Makes
Email
Name
User_Id
Name
Address
Ask
Users
Email
Query
User_Id
Contact
Message
Figure 3.7.2.1
Page 42
Message
Subject
3.7.3 Table schemas

The complete (compliable) set of CREATE TABLE statements (and other SQL statements) that
declare the database schema, including integrity constraints, domain specifications, assertions,
and access privileges -- documented in a template with the intended use of each table and column.
This is a suggested template you may use1:
Admin
Description
This table describes login information and personal information of

admin
Attribute
Description
Type
Email
EMAIL Id of admin
Varchar
Examples of values
id@address.com
Login_id
Login id of admin
Varchar
id@address.com
Name
Name of admin
Varchar
amit
Address
Address of admin
Varchar
28, ashok vihar
Contact
Contact
admin
Varchar
9999999999
Primary Key
Foreign Keys
SQL Code
number
of
Email
Login_id
CREATETABLE [dbo].[Admin](
[Email] VARCHAR (50)NULL,
[Login_id]
VARCHAR (50)NULL,
[Name] VARCHAR (50)NULL,
[Address] VARCHAR (50)NULL,
[Contact]
VARCHAR (50)NULL,
PRIMARYKEYCLUSTERED ([Email] ASC)
);
TABLE 3.7.3.1
Page 43
Billoperator
Description

Bill Operator
Attribute
Description
Email
EMAIL
Id
Operator
Login_id
Type
Varchar
Examples of values
id@address.com
Login id of Bill Operator
Varchar
id@address.com
Name
Name of Bill Operator
Varchar
amit
Address
Address of Bill Operator
Varchar
28, ashok vihar
Contact
Contact number of Bill

Operator
Varchar
9999999999
Primary Key
Foreign Keys
SQL Code
of
Bill
Login_id
Email
CREATETABLE [dbo].[ Billoperator](

[Login_id]
VARCHAR (50)NULL,
[Contact]
VARCHAR (50)NULL,
);
TABLE 3.7.3.2
Login
Description

admin
Attribute
Description
Type
Login_id
Login id of user
Varchar
Examples of values
id@address.com
Password
Password of user
Varchar
Amit123
Login_type
Type of login
Varchar
Username
password
Security_question
Security
user
of
Varchar
What is
name?
Security_answer
Security
answer
security question
of
Varchar
Prince
question
Page 44
and
your
pet
Primary Key
Login_id
Foreign Keys
SQL Code
CREATETABLE [dbo].[Login](
[Login_id] VARCHAR (50)NULL,
[Password]
VARCHAR (50)NULL,
[Login_type] VARCHAR (50)NULL,
[Security_question] VARCHAR (50)NULL,
[Security_answer]
VARCHAR (50)NULL,
PRIMARYKEYCLUSTERED ([Login_id] ASC)
);
TABLE 3.7.3.3
Query
Description
This table describes any query asked by the user.
Attribute
Description
Type
Name
Name of user or visitor
Varchar
Examples of values
Amit
Email_address
Email address of user or

visitor
Varchar
id@address.com
Message_subject
Subject of message
Varchar
Cold
Message
Query by the user or

visitor
Varchar
Have a cold & dont

know what to do
Login_id
Login id by the user for

answer of query
Varchar
id@address.com
Primary Key
Foreign Keys
SQL Code
Email_address
Login_id
CREATETABLE [dbo].[Query](
[Email_address]
VARCHAR (50)NULL,
[Message_subject] VARCHAR (50)NULL,
[Message] VARCHAR (50)NULL,
[Login_id]
VARCHAR (50)NULL,
PRIMARYKEYCLUSTERED ([Email_address] ASC)
);
TABLE 3.7.3.4
Page 45
User
Description
Have personal details of every user.
Attribute
Description
Type
Email
Email id of user.
Varchar
Examples of values
id@address.com
Login_id
Login_id of user.
Varchar
id@address.com
Name
Name of the user.
Varchar
Amit
Address
Address of the user
Varchar
28, ashok vihar
Contact
Contact details of the

user.
Varchar
9999999999
Primary Key
Foreign Keys
SQL Code
Email
Login_id
CREATETABLE [dbo].[ User](

[Login_id]
VARCHAR (50)NULL,
[Contact]
VARCHAR (50)NULL,
);
TABLE 3.7.3.5
Feedback
Description
Feedback of existing user.
Attribute
Description
Type
Login_id
Login_id of user.
Varchar
Thought
Any type of suggestion

or any thought to
share.
Varchar
Page 46
Examples of values
id@address.com
Its
very
website.
good
Primary Key
Foreign Keys
SQL Code
Login_id
CREATETABLE [dbo].[Feedback](
[Login_id]
VARCHAR (50)NULL,
[Thought] VARCHAR (50)NULL,
);
TABLE 3.7.3.6
Tables data:
The tables have to be populated by you and your client. Each table must contain an appropriate
number of data.
SQL queries:
FEEDBACK
insert into Feedback values('" + TextBox3.Text + "','" + TextBox4.Text + "','" +
TextBox5.Text + "','" + TextBox6.Text + "')
REGISTRATION
insert into Registration values('" + TextBox3.Text + "','" + TextBox4.Text + "','" +
TextBox5.Text + "','" + TextBox6.Text + "', '" + TextBox7.Text + "')
LOGIN
select * from LogIn where Username =@username and Password=@password
QUERY
insert into Query values('" + TextBox3.Text + "','" + TextBox4.Text + "','" +
TextBox5.Text + "','" + TextBox6.Text + "')
Page 47
3.8. Source Code Details

SLOC: Source Lines of Code. Use the free software sloc to calculate the SLOC
S.No
Filename
SLOC
1.
Masterpage.master
320
2.
Ayurveda_Diet.aspx
99
3.
Ayurveda_in_Daily_Life.aspx
109
4.
Contact_Us.aspx
150
5.
Feedback.aspx
135
6.
Home.aspx
92
7.
Know_Ayurveda.aspx
80
8.
Know_Thyself.aspx
89
9.
Panchkarma.aspx
97
10.
Registration.aspx
192
11.
Ayu_Prod.aspx
177
12.
Ayurvedic.master
419
13.
Ayurvedic_Diet.aspx
180
14.
Ayurvedic_Diet_Consultation.aspx
50
15.
Ayurvedic_Essential_Oils.aspx
69
16.
Ayurvedic_Herbal_Teas.aspx
123
17.
Ayurvedic_Intestinal_Cleanse.aspx
75
18.
Ayurvedic_Massage_Oils.aspx
96
19.
Ayurvedic_Rasayana.aspx
160
20.
Ayurvedic_Rasayana.master
319
21.
Ayurvedic_Skin_Cream .aspx
55
22.
Ayurvedic_Spice_Masala.aspx
103
23.
Billing_Process.aspx
160
Page 48
24.
Skin_Cream_Product_Details.aspx
126
25.
ViewCart.aspx
145
26.
User_LogIn.aspx
26
TABLE 3.8.1
FEEDBACK FORM
<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"
AutoEventWireup="true" CodeFile="Feedback.aspx.cs" Inherits="Ayurveda_Feedback" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
<style type="text/css">
.style6
{
color: #800000;
}
.style7
{
color: #800000;
font-size: large;
}
.style8
{
height: 25px;
text-align: justify;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
<asp:Panel ID="Panel5" runat="server" BackColor="#CCFFFF" BorderStyle="Ridge"
Width="730px">
<table bgcolor="#CCFFFF" class="style1"
style="background-color: #EEEEEE; border-style: ridge; width: 78%">
<tr>
<td bgcolor="#CCFFFF" class="style6" colspan="2">
<asp:ScriptManager ID="ScriptManager1" runat="server">
</asp:ScriptManager>
</td>
</tr>
<tr>
<td bgcolor="#CCFFFF" class="style7" colspan="2">
<strong>FEEDBACK</strong></td>
</tr>
<tr>
<td bgcolor="#CCFFFF" class="style8">
Your Name:</td>
<asp:TextBox ID="TextBox3" runat="server"
ontextchanged="TextBox3_TextChanged"
Width="190px"></asp:TextBox>
</td>
</tr>
<tr>
Page 49
Email ID:</td>
<asp:TextBox ID="TextBox4" runat="server" TextMode="Email"
</td>
</tr>
<tr>
Mobile Number:</td>
<asp:TextBox ID="TextBox5" runat="server" TextMode="Number"
</td>
</tr>
<tr>
Your Thought:</td>
<asp:TextBox ID="TextBox6" runat="server" TextMode="MultiLine"
</td>
</tr>
<tr>
</td>
<asp:Button ID="Button2" runat="server" Font-Names="Georgia"
onclick="Button2_Click" style="height: 26px" Text="Submit" />
<asp:Button ID="Button3" runat="server" Font-Names="georgia"
onclick="Button3_Click" Text="Clear" />
</td>
</tr>
<tr>
</td>
<asp:SqlDataSource ID="SqlDataSource2"
runat="server"></asp:SqlDataSource>
</td>
</tr>
</table>
<br />
</asp:Panel>
</asp:Content>
KNOW AYURVEDA
AutoEventWireup="true" CodeFile="Know_Ayurveda.aspx.cs"
Inherits="Ayurveda_Know_Ayurveda" %>
.style4
{
}
.style5
{
font-size: large;
color: #800000;
Page 50
font-weight: bold;
}
.style6
{
}
.style7
{
font-size: large;
color: #800000;
}
</style>
</asp:Content>
Height="351px" Width="708px" style="text-align: left">
<table class="style1">
<tr>
<td class="style7">
<strong>KNOW AYURVEDA</strong></td>
<td>
</td>
</tr>
<tr>
<td>
<asp:Image ID="Image1" runat="server" Height="141px"
ImageUrl="~/Images/under_back.gif" Width="174px" />
</td>
<td class="style6">
AYURVEDA is the oldest surviving complete medical system in the
world. Derived
from its ancient Sanskrit roots - 'ayus' (life) and
'ved' (knowledge) - and
offering a rich, comprehensive outlook to a healthy life, its
origins go back
nearly 5000 years. To when it was expounded and practiced by the
same spiritual
rishis, who laid the foundations of the Vedic civilisation in
India, by
organising the fundamentals of life into proper systems.</td>
</tr>
<tr>
<td class="style6" colspan="2">
The main source of knowledge in this field therefore remain the
Vedas, the
divine books of knowledge they propounded, and more specifically
the fourth of
the series, namely Atharvaveda that dates back to around 1000 BC.
Of the few
other treatises on AYURVEDA that have survived from around the
same time, the
most famous are Charaka Samhita and the Sushruta Samhita which
concentrate on
internal medicine and surgery respectively. The Astanga Hridayam
is a more
concise compilation of earlier texts that was created about a
thousand years
ago. These between them forming a greater part of the knowledge
base on AYURVEDA
as it is practiced today.</td>
</tr>
Page 51
</table>
<br />
</asp:Panel>
</asp:Content>
CONTACT US
AutoEventWireup="true" CodeFile="Contact_Us.aspx.cs" Inherits="Ayurveda_Contact_Us" %>
.style5
{
font-size: large;
color: #800000;
text-align: left;
}
.style6
{
text-align: left;
}
.style7
{
text-align: left;
height: 26px;
}
</style>
</asp:Content>
Width="730px">
<table class="style1"
style="border-style: ridge; background-color: #EEEEEE; width: 74%;"
bgcolor="#CCFFFF">
<tr>
<td class="style5" bgcolor="#CCFFFF">
<strong>AYURVEDA AND AYURVEDIC RASAYANA</strong></td>
</tr>
<tr>
Telephone No. +91 9717972346</td>
</tr>
<tr>
Information: Hours of Operation: 11 A.M to 7 P.M Pacific Standard
Time 7 days a
week</td>
</tr>
<tr>
</td>
</tr>
</table>
<br />
style="background-color: #EEEEEE; border-style: ridge; width: 74%"
bgcolor="#CCFFFF">
Page 52
<tr>
Enter Your Name:</td>
<asp:TextBox ID="TextBox3" runat="server" Width="210px"
ontextchanged="TextBox3_TextChanged"></asp:TextBox>
</td>
</tr>
<tr>
Email Address:</td>
<asp:TextBox ID="TextBox4" runat="server" Width="210px"
TextMode="Email"></asp:TextBox>
</td>
</tr>
<tr>
Message Subject:</td>
</td>
</tr>
<tr>
Enter Your Message:</td>
<asp:TextBox ID="TextBox6" runat="server" TextMode="MultiLine"
</td>
</tr>
<tr>
</td>
</td>
</tr>
<tr>
</td>
Text="Submit"
onclick="Button2_Click" />
onclick="Button3_Click" Text="Clear" />
</td>
</tr>
</table>
<br />
</asp:Panel>
</asp:Content>
Page 53
HOME PAGE
AutoEventWireup="true" CodeFile="Home.aspx.cs" Inherits="Ayurveda_Home" %>
<%@ Register assembly="AjaxControlToolkit" namespace="AjaxControlToolkit"
tagprefix="asp" %>
<%@ Register namespace="AjaxControlToolkit" tagprefix="AjaxControlToolkit" %>
</asp:Content>
              &n
bsp;             &nbs
p;
              &n
bsp;
<asp:ToolkitScriptManager ID="ToolkitScriptManager1" runat="server">
</asp:ToolkitScriptManager>
<table border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<asp:Button ID="btnPrevious" runat="server" Font-Size="20"
Text="<<" />
</td>
<td>
<asp:Image ID="Image1" runat="server" Height="300" Width="300" />
<asp:SlideShowExtender ID="SlideShowExtender" runat="server"
AutoPlay="true" ImageDescriptionLabelID="lblImageDescription"
ImageTitleLabelID="lblImageTitle" Loop="true"
NextButtonID="btnNext"
PlayButtonID="btnPlay" PlayButtonText="Play"
PreviousButtonID="btnPrevious"
SlideShowServiceMethod="GetImages" StopButtonText="Stop"
TargetControlID="Image1">
</asp:SlideShowExtender>
</td>
<td>
<asp:Button ID="btnNext" runat="server" Font-Size="20" Text=">>"
/>
</td>
</tr>
<tr>
<td align="center" colspan="3">
<asp:Button ID="btnPlay" runat="server" Font-Size="20" Text="Play" />
</td>
</tr>
<tr>
<td align="center" colspan="3">
<br />
<b>Name:</b>
<asp:Label ID="lblImageTitle" runat="server" Text="Label" />
<br />
<b>Description:</b>
<asp:Label ID="lblImageDescription" runat="server" Text="Label" />
</td>
</tr>
</table>

</asp:Content>
Page 54
AYURVEDIC MASTER PAGE

<%@ Master Language="C#" AutoEventWireup="true" CodeFile="Ayurvedic.master.cs"
Inherits="Ayurvedic_Rasayana_Ayurvedic" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
<asp:ContentPlaceHolder id="head" runat="server">
</asp:ContentPlaceHolder>
.style1
{
width: 100%;
}
.style2
{
height: 32px;
text-align: left;
}
.style3
{
background-color: #F2DFC2;
}
.style4
{
color: #333333;
}
</style>
</head>
<body>
<form id="form1" runat="server">
<div>
<asp:Panel ID="Panel1" runat="server"
BackImageUrl="~/Images/Background Image.jpg" BorderStyle="Ridge">
<table bgcolor="White" border="1"
style="border-color: #FFFFFF; width: 55%; margin-left: 10%;"
width="800">
<tr>
<td align="center" style="border-color: #FFFFFF" valign="top">
<asp:ImageButton ID="ImageButton4" runat="server"
ImageUrl="~/Images/temple-header.png" />
</td>
</tr>
<tr>
<td align="center" valign="top">
<asp:Menu ID="Menu4" runat="server" BackColor="#EEC450"
BorderColor="#FF6666"
BorderStyle="Inset" DynamicHorizontalOffset="2" FontBold="True"
Font-Size="Large" ForeColor="#890000" Height="30px"
Orientation="Horizontal"
style="text-align: center" Width="100%"
onmenuitemclick="Menu4_MenuItemClick">
Page 55
<StaticMenuItemStyle BorderColor="Transparent"
BorderStyle="Inset"
HorizontalPadding="38px" />
<DynamicHoverStyle BackColor="Black" BorderColor="Silver"
BorderStyle="Outset"
ForeColor="White" />
<DynamicMenuItemStyle HorizontalPadding="3px"
VerticalPadding="3px" />
<DynamicMenuStyle BackColor="#B5C7DE"
HorizontalPadding="15px" />
<DynamicSelectedStyle BackColor="Black"
BorderColor="Silver"
BorderStyle="Ridge" />
<Items>
<asp:MenuItem NavigateUrl="~/Ayurvedic
Rasayana/Home.aspx" Text="Home"
Value="Home"></asp:MenuItem>
<asp:MenuItem NavigateUrl="~/Ayurvedic
Rasayana/Ayurvedic_Diet.aspx"
Text="Ayurvedic Diet" Value="Ayurvedic
Diet"></asp:MenuItem>
<asp:MenuItem Text="Know About Diseases" Value="Know
About Diseases">
</asp:MenuItem>
<asp:MenuItem Text="Ayurvedic Products"
Value="Ayurvedic Products"
NavigateUrl="~/Ayurvedic Rasayana/Ayu_Prod.aspx">
</asp:MenuItem>
<asp:MenuItem Text="Feedback" Value="Feedback"
NavigateUrl="~/Ayurvedic
Rasayana/Feedback.aspx"></asp:MenuItem>
</Items>
<StaticHoverStyle BackColor="White" BorderColor="White"
BorderStyle="Outset"
BorderWidth="1px" Font-Bold="True" Font-Size="Medium"
ForeColor="Maroon" />
</asp:Menu>
</td>
</tr>
<tr>
<td align="center" bgcolor="White"
style="width: 795px; background-color: white;" valign="top">
<asp:SiteMapDataSource ID="SiteMapDataSource1" runat="server"
/>
<table border="1" style="border-color: #FFFFFF" width="100%">
<tr>
<td bgcolor="#F2DFC2" style="border-color: #FFFFFF;
width: 100px">
<asp:Panel ID="Panel3" runat="server">
<tr>
<td class="style2">
<asp:Panel ID="Panel4"
runat="server" BorderStyle="Ridge">
<table bgcolor="#F2DFC2"
class="style1">
<tr>
<td bgcolor="#F2DFC2"
colspan="2">
Page 56
<strong><span
class="style3">           &nbsp
;      <span class="style4">LOGIN</span></span></strong></td>
</tr>
<tr>
class="style4">
Username</td>
<td bgcolor="#F2DFC2">
<asp:TextBox
ID="TextBox1" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
class="style4">
Password</td>
<td bgcolor="#F2DFC2">
<asp:TextBox
ID="TextBox2" runat="server" CssClass="style4"></asp:TextBox>
</td>
</tr>
<tr>
colspan="2" style="text-align: left">
<asp:CheckBox
ID="CheckBox1" runat="server" CssClass="style4"
style="textalign: left" Text="Remember me next time" />
</td>
</tr>
<tr>
class="style2" colspan="2">
<span
class="style4">           &nbsp
;         </span>
<asp:Button
ID="Button1" runat="server" CssClass="style4" Font-Bold="False"
FontNames="Georgia" Font-Size="Medium" style="text-align: center"
Text="LogIn"
onclick="Button1_Click" />
</td>
</tr>
<tr>
<asp:HyperLink
ID="HyperLink1" runat="server" ForeColor="#FF9933"
NavigateUrl="~/Ayurvedic Rasayana/Registration.aspx">New User SignUp</asp:HyperLink>
</td>
</tr>
<tr>
<asp:SqlDataSource
ID="SqlDataSource1" runat="server"></asp:SqlDataSource>
</td>
</tr>
Page 57
</table>
</asp:Panel>
</td>
</tr>
<tr>
<td class="style2">
<asp:HyperLink ID="HyperLink2"
runat="server" Font-Bold="False"
Font-Names="georgia" FontSize="Small" Font-Underline="True"
ForeColor="#333333"
style="text-align: justify">Learn which dosha you are and get a raw-foods chart for
your body type! Click to order our personalized, ayurvedic diet
consultation.</asp:HyperLink>
</td>
</tr>
<tr>
<td class="style2">

<asp:ImageButton ID="ImageButton2"
runat="server" Height="49px"
ImageUrl="~/Images/fb.png"
style="text-align: left" Width="52px" />

<asp:ImageButton ID="ImageButton3"
runat="server" Height="48px"
ImageUrl="~/Images/twitter.png" Width="55px" />
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
Page 58
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
Page 59
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
Page 60
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
<tr>
<td class="style2">
</td>
</tr>
</table>
</asp:Panel>
</td>
<td align="center" style="width: 554px" valign="top">
<asp:ContentPlaceHolder ID="ContentPlaceHolder1"
runat="server">
</asp:ContentPlaceHolder>
</td>
</tr>
</table>

</td>
</tr>
Page 61
<tr>
<td align="center" style="width: 795px; background-color: white;"
valign="top">
</td>
</tr>
</table>
</asp:Panel>
<br />
</div>
</form>
</body>
</html>
REGISTRATION PAGE
AutoEventWireup="true" CodeFile="Registration.aspx.cs"
Inherits="Ayurveda_Registration" %>
.style4
{
text-align: left;
}
.style5
{
text-align: center;
font-size: large;
color: #800000;
}
.style6
{
text-align: left;
color: #800000;
}
.style7
{
text-align: left;
width: 219px;
color: #800000;
}
.style8
{
text-align: left;
width: 214px;
}
.style9
{
}
</style>
</asp:Content>
Width="730px">
style="border-style: ridge; width: 74%; background-color: #EEEEEE;"
Page 62
bgcolor="#CCFFFF">
<tr>
<td class="style4" colspan="3" bgcolor="#CCFFFF">
<asp:ScriptManager ID="ScriptManager1" runat="server">
</asp:ScriptManager>
</td>
</tr>
<tr>
<strong>REGISTRATION</strong></td>
</tr>
<tr>
Name:</td>
<asp:UpdatePanel ID="UpdatePanel1" runat="server">
<ContentTemplate>
<tr>
<td class="style11">
ontextchanged="TextBox3_TextChanged1"
</td>
<td>
  <asp:Label ID="Label1" runat="server"
ForeColor="Maroon" Text="*"></asp:Label>
</td>
</tr>
</table>
</ContentTemplate>
</asp:UpdatePanel>
</td>
</tr>
<tr>
Username:</td>
<asp:TextBox ID="TextBox4" runat="server" Width="195px"></asp:TextBox>
</td>
*</td>
</tr>
<tr>
Email:</td>
<asp:TextBox ID="TextBox5" runat="server" TextMode="Email"
</td>
*</td>
</tr>
<tr>
Password:</td>
<asp:TextBox ID="TextBox6" runat="server" TextMode="Password"
</td>
Page 63
*</td>
</tr>
<tr>
Confirm Password:</td>
<asp:TextBox ID="TextBox7" runat="server" TextMode="Password"
</td>
*</td>
</tr>
<tr>
Fields marked with an asterisk (<span class="style7">*</span>) are
required</td>
</td>
</td>
</tr>
<tr>
</td>
onclick="Button2_Click" Text="Register" />
</td>
</td>
</tr>
</table>
</asp:Panel>
</asp:Content>
BILLING PROCESS PAGE

<%@ Page Title="" Language="C#" MasterPageFile="~/Ayurvedic Rasayana/Ayurvedic.master"
AutoEventWireup="true" CodeFile="Billing_Process.aspx.cs"
Inherits="Ayurvedic_Rasayana_Billing_Process" %>
.style5
{
text-align: left;
}
.style6
{
text-align: left;
width: 128px;
}
</style>
</asp:Content>
<asp:Panel ID="Panel5" runat="server" BackColor="#EEEEEE" BorderStyle="Ridge"
Height="537px" Width="730px">
<asp:Panel ID="Panel6" runat="server" Height="53px" Width="78%">
Page 64
<table class="style1" style="background-color: #EEEEEE; border-style:

ridge;">
<tr>
CUSTOMER INFORMATION</td>
</tr>
<tr>
<td class="style5">
Username:</td>
<td class="style5">
</td>
</tr>
<tr>
<td class="style5">
Email</td>
<td class="style5">
</td>
</tr>
<tr>
<td class="style5">
</td>
<td class="style5">
<asp:Button ID="Button2" runat="server"
onclick="Button2_Click" Text="Submit" />
<asp:Button ID="Button3" runat="server" Text="Back" />
</td>
</tr>
<tr>
<td class="style5">
</td>
<td class="style5">
</td>
</tr>
</table>
<asp:Panel ID="Panel7" runat="server" BackColor="#EEEEEE" Height="50px"
Visible="False">
<table class="style1" style="background-color: #EEEEEE; border-style:
ridge">
<tr>
BILL TO INFORMATION</td>
</tr>
<tr>
<td class="style6">
First Name:</td>
<td class="style5">
</td>
</tr>
<tr>
<td class="style6">
Last Name:</td>
<td class="style5">
</td>
Page 65
</tr>
<tr>
<td class="style6">
Address1:</td>
<td class="style5">
</td>
</tr>
<tr>
<td class="style6">
Address2:</td>
<td class="style5">
</td>
</tr>
<tr>
<td class="style6">
City:</td>
<td class="style5">
</td>
</tr>
<tr>
<td class="style6">
State:</td>
<td class="style5">
</td>
</tr>
<tr>
<td class="style6">
Zip/Postal Code:</td>
<td class="style5">
</td>
</tr>
<tr>
<td class="style6">
Telephone No:</td>
<td class="style5">
</td>
</tr>
<tr>
<td class="style6">
</td>
<td class="style5">
<asp:Button ID="Button4" runat="server" Text="Submit" />
</td>
</tr>
<tr>
<td class="style6">
</td>
<td class="style5">
</td>
Page 66
</tr>
</table>
</asp:Panel>
</asp:Panel>
</asp:Panel>
</asp:Content>
3.9. Output.
FEEDBACK
Figure 3.9.1
Page 67
CONTACT US
Figure 3.9.2
AYURVEDIC PRODUCTS
Figure 3.9.3
Page 68
AYURVEDA IN OUR DAILY LIFE
Figure 3.9.4
AYURVEDA DIET
Figure 3.9.5
Page 69
PANCH KARMA
Figure 3.9.6
AYURVEDA DIET CONCELTATION
Figure 3.9.7
Page 70
AYURVEDIC HERBEL TEAS
Figure 3.9.8
Page 71
CHAPTER 4
Page 72
4.1. Glossary
ABBREVATION
TERM DEFINITION
QA
Quality assurance
SCMP
Software Configuration Management Plan
SDD
Software Design Document
SQAP
Software Quality Assurance Plan
SRS
Software Requirements Specification
TBD
To be decided
TBN
To be named
XHTML
Extensible hypertext markup language
HTML
hypertext markup language
CSS
cascading style sheets
HTTPS
hypertext transfer protocolsecure
CAPTCHA
completely automated public turing test to tell

computers and humans apart
ASPX
Active Server Pages Extended
CS
C Sharp
Page 73
CHAPTER 5
Page 74
5.1. Bibliography
http://www.devaaya.com/ayurveda-therapies.php
http://www.baidyanath.com/know_ayurveda.php
http://ojaminherbal.com/ojamin-herbal-ayurvedic-medicine.html
http://ayurveda-foryou.com/treat/diabetes.html
http://www.kairaliproducts.in/cataract-medicine.html
http://www.jiva.com/ayurveda/treatment/problems-we-treat/415.html?task=view
http://www.prokerala.com/health/ayurveda/diabetes-treatment.htm
Page 75

Ayurveda Report

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Ayurveda Report

Caricato da

Copyright:

Formati disponibili

CHAPTER 1

1.2 TITLE OF PROJECT

1.4 SCHEDULE OF ACTIVITIES

Research on the project

Aug 1, 2014 Aug 15, 2014

Analyzing and gathering of the

Aug 15, 2014-Aug 20, 2014

Aug 20, 2014- Sept 5, 2014

Database creation and

Sept 5, 2014-Sept 10, 2014

Sept 10, 2014-Sept 20, 2014

Till Sept 30, 2014

Aug. 25, 2014 - Aug. 29, 2014

Sept. 15, 2014 - Sept. 19, 2014

Oct. 6, 2014 - Oct. 10, 2014

Abstract, Introduction,Revision History, Objectives, Schedule of activities, Conclusion,

From the above things my project has been approved by my guide

1.6 ACHEIVEMENT TILL DATE

Research on the project

Aug 1, 2014 Aug 15, 2014

Analyzing and gathering of the

Aug 15, 2014-Aug 20, 2014

Started designing of modules

Aug 20, 2014 - Aug 24, 2014

Aug 25, 2014 - Aug 29, 2014

1.7 REMAINING WORKS

Database creation and connectivity

2.1.2 Document Conventions

Font-type: TIMES NEW ROMAN

2.1.3 Intended Audience and Reading Suggestions

2.1.4 Project Scope

2.2 Overall Description

2.2.2 Product Features

2.2.3 User Classes and Cha-racteristics

2.2.4 Operating Environment

2.2.5 Design and Implementation Constraints

2.2.6 User Documentation

2.3 System Features

2.3.1 USER REGISTRATION

2.3.1.3 Functional Requirements

A unique user ID.

2.3.2.2 Stimulus/Response Sequences (Functional requirement)

2.3.3.2 Stimulus/Response Sequences(Functional requirement)

2.3.3.2 Stimulus/Response Sequences (Functional requirement)

2.4 External Interface Requirements

2.4.2 Hardware Interfaces

REGISTRATION FORM, LOGIN FORM, FEEDBACK FORM, QUERY FORM

2.4.3 Software Interfaces

2.4.4 Communications Interfaces

2.5 Other Nonfunctional Requirements

2.5.2 Safety Requirements

2.5.3 Security Requirements

2.5.4 Software Quality Attributes

2.6 Other Requirements

2.6.1 Development time

2.7 SOFTWARE REQUIREMENTS

2.7.1 Development time

3.2.1.3 Intended Audience:

3.2.2 System Overview

3.3 Design Considerations

3.3.2 General Constraints

Server used to support to run website:

1. HTML/DHTML: As an essence to give pages dynamic look, feel and appeal.

Data repository and distribution requirements