Voice based autometedtransport enquiry system in #c by Rohit malav
final doc
1. A PROJECT REPORT ON
Voice Based Application in Vxml on Restaurants
Submitted to Jawaharlal Nehru Technological University
For the partial fulfillment of the
Requirement for the
Award of Bachelors in Technology
for Mini project
Done by
R.Neha-07L51A1231
Syeda Ghazala Nawaz-07L51A1251
Zoha Khan-07L51A1261
Department of Information Technology
Shadan Women’s College of Engineering and Technology,
Khairatabad, Hyderabad, 500008
August 2010
2. ACKNOWLEDGMENT
My express thanks and gratitude and thanks to Almighty God, my parents and other
family members and friends without whose unsustained support, I could not have made this
career in B.Tech-IT 3rd year.
I wish to place on my record my deep sense of gratitude to my project guide, Mr.
Santosh, Rensissance Softlabs, Hyderabad for his constant motivation and valuable help
through the project work. Express my gratitude to Mrs. Afreen Fatima ,Head of Department
for her valuable suggestions and advices throughout the course. I also extend my thanks to other
Faculties for their Cooperation during my Course.
Finally I would like to thank my friends for their cooperation to complete this project.
3. PREFACE
In the Current Scenario Work flow/Project Management has become very hectic.
So to contain all this we need to integrate the whole architecture so that the system and the flow
should move simultaneously.
There is improved efficiency and the automation of the business process takes place resulting in
elimination of unnecessary steps.
This volume presents the manner in which the software was developed and how the
various problems are tackled at the different levels for the convenience of the user.
We hope that this package would prove to be an excellent tool for exporting and
importing of Data Flow with in a local network.
`
4. 1)Abstract:
Overview -
Voice XML (VXML) is the standard XML format for an interactive voice dialogues between a
human and a computer. The introduction of voicexml can help in changing the entire scenario of
restaurant industry. Voicexml in restaurants can be very convenient and helpful to the customers
as well as to the restaurateurs. It can be the most comfortable way for dealing with the customers
and also reduces labor cost. Voicexml is very advantageous as the customer needs will be satisfied
as they will not have to wait in long queues or spend time listening to the IVR’s (Interactive Voice
Response).
Current scenario-
The present restaurant industry still has human interface to a larger extent when compared to
voice interface. Due to lack of awareness it is not widely used and is uncommon. Another factor
affecting the usage is the cost of installing. At present people have to wait in long queues because
there are a lot of customers to attend to and the restaurants have limited labour and this causes
inconvenience to both the customers and the restaurateurs.
Failures-
Usually people are used to human interaction and the automated voice response is tough for
them to handle. For example, when customers call the toll free numbers, they have to wait for
long in order to speak to an agent. Also due to the difference in languages and accents the voice
machine doesn’t receive the proper data and as a result the customer doesn’t get what he wants.
Also at times due to the server failures the system fails. Another reason for the failure of the voice
machine can be improper implementation and lack of knowledge of VoiceXML.
How Voice XML can be helpful in restaurants? (Proposed features)
There can be many advantages when VoiceXML is introduced in restaurants. The objective is to
propose an idea on how VoiceXML can be effectively used in this area. The basic concept of using
this in restaurants is to give the customers a good overall experience. Human interaction can be
reduced which can also serve as a commercial purpose. With the use of voicexml we can place
orders, book banquet halls, plan parties. Special numbers can be given to the customers through
5. which they can get the information about any restaurant, its location, menu and further more
details.
CONTENTS
Certificate
Acknowledgement
Preface
Abstract
1. Introduction
1.1 Purpose…………………………………………………………...10
1.2 Problem Statement……………………………………………….11
1.3 Scope……………………………………………………………....11
2. Software Requirements Specification
7. Introduction
VoiceXML is the HTML of the voice web, the open standard markup language for
voice applications. VoiceXML harnesses the massive web infrastructure
developed for HTML to make it easy to create and deploy voice applications. Like
HTML, VoiceXML has opened up huge business opportunities: the Economist even
says that "VoiceXML could yet rescue telecoms carriers from their folly in
stringing so much optical fibre around the world."
VoiceXML 1.0 was published by the VoiceXML Forum, a consortium of over 500
companies, in March 2000. The Forum then gave control of the standard to the
World Wide Web Consortium (W3C), and now concentrates on conformance,
education, and marketing. The W3C has just published VoiceXML 2.0 as a
Candidate Recommendation. Products based on VoiceXML 2.0 are already widely
available.
While HTML assumes a graphical web browser with display, keyboard, and
mouse, VoiceXML assumes a voice browser with audio output, audio input, and
keypad input. Audio input is handled by the voice browser's speech recognizer.
Audio output consists both of recordings and speech synthesized by the voice
browser's text-to-speech system.
A voice browser typically runs on a specialized voice gateway node that is
connected both to the Internet and to the public switched telephone network (see
Figure 1). The voice gateway can support hundreds or thousands of
simultaneous callers, and be accessed by any one of the world's estimated
1,500,000,000 phones, from antique black candlestick phones up to the very latest
mobiles.
8. VoiceXML takes advantage of several trends:
The growth of the World-Wide Web and of its capabilities.
Improvements in computer-based speech recognition and text-to-
speech synthesis.
The spread of the WWW beyond the desktop computer.
The World Wide Web
The Web's capabilities have grown rapidly since its inception:
Web servers once delivered only static content, but now generate it
dynamically using scripts, server pages, servlets and other
technologies. They also provide access to databases and legacy
systems. VoiceXML takes advantage of all these generation
technologies.
Web data representation has advanced. XML is a general, flexible
data representation with transformation technologies that make it
easy to convert one XML structure into another, or into a non-XML
format. VoiceXML is based on XML.
The Internet is improving in performance, bandwidth, and quality of
service. These improvements lead to new types of web applications
and services, which in turn spur more improvements. VoiceXML
strongly benefits from the ability to move audio data efficiently
across the web.
9. Web application development tools are becoming more powerful.
Some of these, such as XML-sensitive editors, can be used to ease
VoiceXML development
Speech Technology
Automated speech recognition (ASR) systems have greatly improved in recent years as better
algorithms and acoustic models are developed, and as more computer power can be brought to
bear on the task. An ASR system running on an inexpensive home or office computer with a
good microphone can take free-form dictation, as long as it has been pre-trained for the speaker's
voice. Over the phone, and with no speaker training, a speech recognition system needs to be
given a set of speech grammars that tell it what words and phrases it should expect. Within these
constraints a surprisingly large set possible utterances can be recognized (e.g., a particular
mutual fund name out of thousands). Recognition over mobile phones in noisy environments,
while problematic, can be improved with a new technology called distributed speech recognition,
where the early analysis is done on the handset. Speech recognition is used today in large
numbers of commercial applications.
Advances are also being made in speech synthesis, or text-to-speech (TTS). Older TTS systems
generate speech completely from scratch, and tend to sound like "drunken robots". They can be
hard to listen to, and at times even incomprehensible. But newer TTS systems are much more
lifelike - they use a technique called waveform concatenation, in which speech is generated from
libraries of pre-recorded waveforms.
It is important to note here that VoiceXML can be used even in environments lacking speech
technology. Audio output can consist entirely of pre-recorded prompts, and input can be
exclusively from the keypad. While speech technology makes applications much more powerful
and pleasant to use, VoiceXML also brings the advantages of web development and deployment
to older styles of computer telephony applications.
The Ubiquitous Web
The Internet extends to more devices than personal computers. Some examples are personal
organizers with wireless data connections, mobile phones supporting the Wireless Application
Protocol (WAP), and NTT Docomo's i-mode phones. The future will bring more web-enabled
devices: overnight delivery drop off boxes that schedule pickups and record their contents,
networked MP3 portables, vending machines that reorder supplies when running low, wall
displays that download artwork, web-based stereo receivers and televisions, and many others.
Speech technology is a very natural and powerful interface for ubiquitous web devices.
Microphones are much smaller than keyboards and keypads, and speakers smaller than screens.
So it seems quite likely that many future web devices will have on-board speech recognition (as
do some mobile phones today).
10. Bringing It All Together
Why is the VoiceXML approach important? First, the phone is important. There
are over 1.5 billion phones in use, far more than there are Internet-connected
computers. Phones are easy to use and don't need to be booted up. Telephone
networks are much more reliable than data networks.
Mobile phones are achieving large penetration rates too: unlike notebook
computers and many PDAs, mobile phones are highly portable, inexpensive, and
have long battery lives. Mobiles are a natural match for location-based
applications. They can be used while driving (though not always safely).
Second, voice is important on the phone. Voice has always been the natural
mode of communication for phones. Even though some mobiles have
WAP/XHTML browsers, their small screens and keypads make micro browsers
hard to use, especially while driving. The i-mode system is more compelling,
though shares the same limitations.
But there are advantages to combining visual browsing and voice browsing. For
instance, complex information is hard to remember when spoken to the user, but
easy to remember if it is presented in a persistent visual form. And some
misrecognitions of spoken input are easy to correct with keypad entry. Therefore,
we should soon begin to see multi-modal applications deployed alongside pure
visual applications and pure voice applications.
Third, the Internet is important to voice applications:
Voice application development is easier because VoiceXML is a high-
level, domain-specific markup language, and because voice
applications can now be constructed with plentiful, inexpensive, and
powerful web application development tools.
Voice applications are now far easier to deploy. No longer must they
reside on a special-purpose voice server in a proprietary "walled
garden": they can be placed anywhere on the Internet and accessed
from any VoiceXML-compliant voice server.
Applications can be cleanly structured into service logic on the web
server, and presentation logic, in VoiceXML pages delivered to the
voice browser. This has many advantages, not the least of which is
that a common application back end on the web server can serve up
different types of presentation logic based on the user's device. This
factoring leads to huge savings.
Finally, voice, and therefore VoiceXML, is important for web devices other than
the phone. For example, a voice actuated "universal remote" could have an on-
11. board voice browser and VoiceXML content generated from all the devices in its
vicinity. You could walk into your family room, pull the remote from your shirt
pocket, press its push-to-talk button and say "stereo: off; television: what action
movies are playing?"
Voice Services
What sorts of voice applications are best suited for VoiceXML? Here are a few ideas.
Information retrieval (IR) is a good match for VoiceXML. In an IR application, audio output tends
to be pre-recorded information. Voice input can be highly constrained (e.g., a few browsing
commands and limited data entry), or it can be quite rich (e.g., arbitrary street addresses). A good
example of an IR application is one where the user first designs a personal voice newsletter at a
web site, and then calls in periodically to browser through the newsletter. The newsletter may
contain news, sports, traffic, weather, and stock information, as well as more specialized
information such as intranet-based company news. This service can be funded by subscription,
advertisement, or connect time.
Directory assistance applications work well in VoiceXML. AT&T's has a new VoiceXML toll-free
directory assistance service, powered by TellMe, which you can try out in the United States by
calling 800.555.1212. It is so incredibly effective that the automation rate climbed from 8% to
55%, saving AT&T $20 million a year. Remarkably, customer satisfaction has risen by over a
third along with this increased automation.
Electronic commerce is another area. Customer service applications such as package tracking,
account status, and support are well suited to VoiceXML. Financial applications like banking,
stock quotes, and portfolio management are another good match. Catalog applications have to be
done right, because voice conveys much less information than graphics. Catalog applications
work if the customer is looking at a printed catalog (e.g., clothing), or knows the exact product
already (e.g., a book, CD, or DVD title).
Telephone services like personal voice dialing, one-number "find-me" services, voice mail
management, and teleconferencing can easily be voice-enabled through VoiceXML. Personal
voice applications attached to individual phone lines can be very important sources of revenue.
Because standard Web security features apply to the voice web, intranet applications can also be
written in VoiceXML for inventory control, ordering supplies, providing human resource
services, and for corporate portals.
Unified messaging applications can leverage voice. E-mail messages can be read over the phone,
outgoing e-mail can be recorded (and in the future transcribed) over the phone, and voice-
oriented address information can be synchronized with personal organizers and e-mail systems.
Pager messages can be originated from the phone, or routed to the phone.
There are many other areas where voice services can be used, such as checking the status of bids
at an electronic auction site, authorizing bill payments, scheduling pickups of charitable
12. donations, ordering a wake up call at a hotel. Doubtless there are many services not yet
conceived of.
VoiceXML's History
VoiceXML traces its lineage back to several informal gatherings in 1995 by Dave
Ladd, Chris Ramming, Ken Rehor, and Curt Tuckey of AT&T Research. They were
brainstorming ideas about how the Internet would affect telephony applications,
when all the pieces fit into place: why not have a gateway system running a voice
browser interpreting a voice dialog markup language, which delivers web content
and services to ordinary phones? Thus began the AT&T Phone Web project.
When AT&T spun off Lucent, a separate Phone Web project continued on there as
well. Chris remained at AT&T, Ken went with Lucent, and Dave and Curt moved
on to Motorola.
By early 1999 AT&T and Lucent had incompatible dialects of the Phone Markup
Language (PML), Motorola had its new VoxML, and other companies were also
experimenting with these ideas, in particular IBM with SpeechML. A standard
language had to be designed to enable the voice web. The original Phone Web
people remained close friends, so AT&T, Lucent, and Motorola began the
organization of the VoiceXML Forum. IBM joined as a founder soon afterwards.
From March to August of 1999 a small team of Forum technologists worked
together to produce a new language, VoiceXML 0.9, combining the best features
of the earlier languages and pushing on into new areas, especially DTMF (touch-
tone key) support and mixed-initiative dialogs. After 0.9 was published, there
began an extensive period of comment from the growing VoiceXML Forum
community. These comments resulted in huge improvements to the language,
including client-side scripting, properties, and subdialogs. VoiceXML 1.0 came
out in March 2000, and almost overnight fifteen or twenty different
implementations sprang up.
The following month, the VoiceXML Forum submitted the 1.0 language to the
World Wide Web Consortium (W3C) for consideration. In May, the W3C
"accepted" VoiceXML, an event that generated a lot of press coverage, but which
merely acknowledged receipt of the submission. But the W3C's Voice Browser
Working Group eagerly took on the job of the next revision.
The W3C process has taken more time than any of us expected, but the emphasis
on consensus among the many participating companies has led to a strong
standard. The first public Working Draft of VoiceXML 2.0 was published in
October 2001, the Last Call Working Draft came out in April 2002, and VoiceXML
2.0 became a Candidate Recommendation in January 2003.
The changes from VoiceXML 1.0 to 2.0 were fairly conservative. Much thought
and effort went into clarifying expected behaviors, and correcting a few errors in
the specification. Another large amount of work was spent in developing and
13. weaving in new standards for speech recognition grammars and text-to-speech
markup. There were a few extensions, such as the new element, but overall there
is a high degree of similarity between 1.0 and 2.0.
VoiceXML's Future
The W3C is now completing the Implementation Report, part of which consists of
hundreds of interoperability tests to ensure that the VoiceXML standard is
implementable, and that different implementations of VoiceXML can execute the
same content in the same way. The VoiceXML Forum's Conformance Committee
will then round these tests out into a complete conformance suite, which will be a
powerful tool to ensure interoperability between VoiceXML implementations.
Beginning in 2003, the W3C's Voice Browser Working Group will start work on
VoiceXML 3.0. Some suggestions that were too large to incorporate in 2.0 will be
addressed, as well as other new extensions. Some of the improvements being
discussed are:
Using the proposed W3C Natural Language Semantics Markup
Language to represent recognition results.
Currently the <form> ties together the notions of input tasks and the
data filled by those input tasks. Should a new high level task-
oriented dialog construct parallel to <form> and <menu> be defined?
In some cases, the FIA does not provide application developers
close enough control. Should a new low level procedural dialog
construct parallel to <form> and <menu> be defined?
Should grammar and audio resources be defined centrally and then
referenced by "id" attributes elsewhere?
What about standardized audio playback controls for changing the
speed and volume of the audio, and for moving back and forward in
the audio stream? These would be analogous to CD player controls.
Should standard speaker verification features be added to VoiceXML
for additional security? What about enabling the generation of
speaker-trained grammars, for use in personal address books and
similar applications?
There will also likely be changes to VoiceXML to support new multimodal markup
standards. The conceptually cleanest approaches to multimodal use XHTML as a
container for mode-specific markup (XHTML for visual, VoiceXML for voice,
InkXML for ink, etc.), and then define how the modes interact using XML Events.
As part of this effort, a modularization of VoiceXML would be defined such that
one subset could be used for multimodal markup.
14. The final official act of the original VoiceXML 1.0 language design team was to
sign the Taylor Brewing Company Accord. The TBCA sought to rectify the chief
imperfection of the VoiceXML 1.0 standard: its lack of author names. Here they
are, for posterity: Linda Boyer, IBM; Peter Danielsen, Lucent; Jim Ferrans,
Motorola; Gerald Karam, AT&T; David Ladd, Motorola; Bruce Lucas, IBM; and
Kenneth Rehor, Lucent. We hope you have as much fun learning and using
VoiceXML as we did putting it together. Enjoy!
Author Bios
Eric Tober is the Curriculum Developer at Nuance Communications. He joined Nuance in 1999
after performing postdoctoral reseach at the Lawrence Berkeley National Laboratory and the
IBM Almaden Research Center. Among his responsibilities, Eric creates Nuance's technical
courses taught at Speech University (www.nuance.com). In particular, he has recently developed
Nuance's VoiceXML application development course entitled "VoiceXML Voice Site
Development." Eric is a member of the VoiceXML Forum's Education Committee and sits on the
editorial board of the VoiceXML on-line magazine, "VoiceXML Review"
(www.voicexmlreview.org). Nuance Communications is a Promoter member of the VoiceXML
Forum.
Rob Marchand is the Director, Products and Services Development at VoiceGenie Technologies
Inc. Rob has been with VoiceGenie Technologies since 1999, and has worked in advanced
computing and telecommunications since 1985. At VoiceGenie, Rob is responsible for the
VoiceGenie Developer Workshop (http://developer.voicegenie.com), and new products and
services development. Rob is a member of the VoiceXML Education Committee, and of
USENIX and SAGE, and a regular contributor to SANS. VoiceGenie is a Promoter Member of
the VoiceXML Forum.
Jim Ferrans has worked at Motorola since 1999 on the VoxGateway, an advanced VoiceXML 2.0
system that is source-licensed to voice platform vendors, voice hosting companies, and voice
application companies. Jim was on the VoiceXML 1.0 design team, and is an editor of the
VoiceXML 2.0 specification. He began his career at Lucent, where he was lead architect and
language designer for an SQL-based database system. After a stint at Gould Research, he co-
founded Vista Technologies in 1986, where he led the development of various software and
hardware design tools. In 1996 Vista sold itself to Peritus, where Jim managed the development
of several successful Y2K remediation tools.
15. 1.1 Purpose of this project
We no more have to wait in the long queues to wait in long queues to get our tables
reserved. These days we see lots of people standing in the queue waiting to get
there reservation done for enjoying their food at the restaurants but our application
makes the restaurant reservations so easy that people no more have to stand in the
queues to get tables booked.
We can just call on the number which is specified for the application and then take
any information that we would like on the restaurant. After taking down the
requirements what you need! we have to just bookor reserve the table. This saves
the time of the customer also doesn’thave to wait for a table for a long time
waiting for the table outside the restaurant with the families. You can just sit at
home and bookor reserve your table. This enables the customer to utilize their
time in a much efficient and better way.
1.2 Problem Statement:
Before people used to wait for long hours in order to have moments of enjoyment
with their families. When they had some work they couldn’t take time for family
because they had to wait for a long time in the queue. Moreover when people had
work they used to leave there children or wife to wait and go deal with their work
and came back but if they used to be absent at the time when the their turn used to
come the family wouldn’t go as the father was not present at that time and by the
time the father used to come back their turn would have already been gone. This
problem can be over come through our application.
16. 1.3 Scope and proposed Statement:
VoiceXML is the HTML of the voice web, the open standard markup
language for voice applications. While HTML assumes a graphical web
browser with display, keyboard, and mouse, VoiceXML assumes a voice
browser with audio output, audio input, and keypad input. Audio input is
handled by the voice browser's speech recognizer. Audio output consists
both of recordings and speech synthesized by the voice browser's text-to-
speech system. This technology also gives a hike to the speech technology.
An Automated speech recognition (ASR) system running on an inexpensive
home or office computer with a good microphone can take free-form
dictation, as long as it has been pre-trained for the speaker's voice. Over the
phone, and with no speaker training, a speech recognition system needs to
be given a set of speech grammars that tell it what words and phrases it
should expect. Within these constraints a surprisingly large set possible
utterances can be recognized
A voice browser typically runs on a specialized voice gateway node that is
connected both to the Internet and to the public switched telephone
network. The voice gateway can support hundreds or thousands of
simultaneous callers, and be accessed by any one of the world's estimated
1,500,000,000 phones, from antique black candlestick phones up to the very
latest phones
The advantages of using voiceXML are
The growth of the World-Wide Web and of its capabilities.
Improvements in computer-based speech recognition and text-
to-speech synthesis.
The spread of the WWW beyond the desktop computer.
17. SRS(system requirement specification):
A full-service restaurant is generally characterized by two main concepts. First, main-course
items are featured on the menu. Also, food is cooked to order and not chosen from a cafeteria
line, for example. Full service restaurants can by categorized in terms of price, menu, or
atmosphere. They can be formal or casual. Many full-service restaurants can fit into more than
one category.
The different modules that have been used in this project are
Modules:
1) Administration module
2) Reservation module
3) Feedback and complain module
1)Administration Module:
In the administration module the basic things that will be included are
Provisioning:
Restaurant Information:
Name
Location
Contact number
E-mail
Type of the restaurant
Restaurant Facilities:
Facility name
Description of the facility
Cost
Restaurant Timings:
Weekday
Opening Time
Closing Time
Functionality:
Restaurant can update basic restaurant information.
Restaurants can add more facilities or change the existing facilities.
Restaurants can update the working days or hours of the restaurant.
Customers can get the information about the restaurant.
Customer can enquire about the different facilities available in restaurant.
Customers can get the restaurant working days and hours.
18. Queries :
The customer can enquire for the information of any restaurant within a particular area
The customer can also enquire for the information of a specific restaurant
The customer can also know about the timings of the restaurants
The customers can also be provided with various facilities when required
2)Reservationmodule:
In this module the reservation management is done and the respective information is provided.
Provisioning:
Menu Categories
Name
Description
Menu Item
Item name
Cost
Quantity
Customer Information
Customer name
Address
Contact number
Tables
Table Number
Capacity
Table Type
Banquet halls
Marriage
Conference
Birthday parties
Cost
Functionality:
The customer can get the menu information.
The customer can also order items for home delivery.
Customer can also call up for booking tables and banquet halls.
Queries:
The customer can enquire about the different menu categories that the present on the list
19. Cost and quantity related queries can be answered
Size and description of the Banquet halls and the tables can be retrieved by the customer
3)Feedback andcomplaints:
In this module the customer can provide feedback when asked for and can also give in complaints.
Provisioning:
Feedback Query
Query
Feedback Options
Option Name
Score
Customer Feedback Criteria
Customer id
Feedback Date
Description
Complaints
Complaint number
Complaint date
Status of the complaint
Description of the complaint
Resolution
Resolution Date
Functionality:
It is given for the improvement of a restaurants.
Customer can provide the feedback when requested for and can also ask for queries.
The restaurant has to be provided with the customer feedback criteria like the customer id, feedback date
and the description.
The complaints can consist of the complaint number, complaint date, status, description, resolution e.t.c.
The feedback can have options like
1. Satisfactory
2. Good
3. Excellent
This helps us to know how much the customer likes the restaurant.
Queries:
20. The customer is asked for the feedback through queries
Softwarerequirements:
1. Oracle 10g
2. Tomcat 5.0
3. Voxeo prophecy 8.0
4. Java 5.0
5. Voicexml 2.1
Hardwarerequirements:
1. System configuration
2. Processor
3. 1GB ram
4. 40GB hard disk
5. VOIP phones
design:
Er-design:
In software engineering, an entity-relationship model is an abstract and conceptual
representation of data. Entity-relationship modeling is a database modeling method, used to
produce a type of conceptual schema or semantic data model of a system, often a relational
database, and its requirements in a top-down fashion. Diagrams created by this process are
called entity-relationship diagrams,ER diagrams
Below drawn is the er-diagram of restaurant
21. ENTITIES & Attributes :
1)Restaurant
Rest_id
Name
Location
Contact no
Restaurants
PK rest_id
name
location
contact_no
email
type_of_rest
Facility
PK facility_id
name
desp
cost
FK rest_id
Schedule
PK Schd_id
opening_time
closing_time
FK rest_id
Menu_cat
PK cat_id
name
desp
PF rest_id
Menu_item
PK item_id
name
cost
quantity
FK cat_id
PF rest_id
Customer
PK cust_id
name
addr
contact_no
Tables
PK table_id
no_of_tables
capacity
type
FK rest_id
FK cust_id
Banquet_Halls
PK hall_id
cost
type
FK rest_id
Feedback_Query
PK fbquery_id
query
feedback_option
PK option_id
options
score
FK fbquery_id
Complaint
PK compaint_id
comp date
status
desp
resolution
FK cust_id
Cust_Tables
PF cust_id
PF table_id
resv_date
time
PK rest_id
BH_resv
PF cust_id
PF hall_id
resv_date
PK rest_id
Cust_FbQuery
PF cust_id
PF fbquery_id
Feedback
PF cust_id
PF fbquery_id
PF option_id
fb date
25. cust_id
fbquery_id
15)feedback
cust_id
option_id
fbquery_id
fb_date
RELATIONSHIPS:
One-to-many relationship
The one to many relationship between restaurant and facility show us how they are related to each oth
Restuarant
PK rest_id
name
location
contact no
e-mail
type of rest
Facility
PK facility_id
name
desp
cost
PF rest_id
26. One-to-many relationship
The one to many relationship between restaurant and schedule show us how they are related
One-to-many relationship
The one to many relationship between restaurant and menu category shows us the relation between them
One-to-many relationship
The one to many relationship between restaurant and tables shows us how they relate each other
One-to-many relationship
Restaurant
PK rest_id
name
location
contact no
e-mail
type of rest
Schedule
PK schd_id
opening time
closing time
w orking days
PF rest_id
Restaurants
PK rest_id
name
location
contact no
e-mail
type of rest
Menu_cat
PK cat_id
name
desp
PF rest_id
Restaurants
PK rest_id
name
location
contact no
type of rest
e-mail
Tables
PK table_id
no of tables
capacity
type
PF rest_id
27. The one to many relationship between restaurant and banquet halls show us the relation between them
One-to-many relationship
The one to many relationship between menu category and menu item shows the relation between them
Many-to-many relationship
The many to many relation between customer and tables generates another class which is cust_table
Many-to-many relationship
The many to one relation between customer and banquet halls generates the class cust_resv
One-to-many relationship
Restaurants
PK rest_id
name
location
contact no
e-mail
type of rest
Banquet halls
PK hall_id
cost
type
PF rest_id
Menu_cat
PK cat_id
name
desp
Menu item
PK item_id
name
cost
quantity
PF cat_id
Customer
PK cust_id
name
addr
contact no
Tables
PK table_id
no of tables
capacity
type
Cust_Tables
PF cust_id
PF table_id
resv date
time
Customer
PK cust_id
name
addr
contact no
Banquet halls
PK hall_id
cost
type
Cust_resv
PF cust_id
PF hall_id
resv date
28. The one to many relationship between feedback query and feedback option shows how they relate
Many-to-many relationship
The many to many relation between customer and feedback query generates the class cust_fbquery which is
inturn again related to feedback option and this generates the class feedback
One-to-many relationship
The one to many relationship between customer and complaint shows the relation between them
Feedback query
PK fbquery_id
query
Feedback option
PK option_id
options
score
PF fbquery_id
Customer
PK cust_id
name
addr
contact no
Feedback query
PK fbquery_id
query
Cust_Fbquery
PF cust_id
PF fbquery_id
Feedback option
PK option_id
options
score
Feedback
PF cust_id
PF fbquery_id
PF option_id
fb date
Customer
PK cust_id
name
addr
contact no
Complaint
PK complaint_id
comp date
status
desp
resolution
PF cust_id
29. 3.2 UML DIAGRAM
USECASE DIAGRAM
A use case is a set of scenarios that describing an interaction between a user and a system. A use
case diagram displays the relationship among actors and use cases. The two main components of
a use case diagram are use cases and actors.
An actor is represents a user or another system that will interact with the system you are
modeling. A use case is an external view of the system that represents some action the user
might perform in order to complete a task.
30. When to Use: Use Cases Diagrams
Use cases are used in almost every project. They are helpful in exposing requirements and
planning the project. During the initial stage of a project most use cases should be defined, but as
the project continues more might become visible.
31. CLASS DIAGRAM
Class diagrams are widely used to describe the types of objects in a system and their
relationships. Class diagrams model class structure and contents using design elements such as
classes, packages and objects. Class diagrams describe three different perspectives when
designing a system, conceptual, specification, and implementation. These perspectives become
evident as the diagram is created and help solidify the design. This example is only meant as an
introduction to the UML and class diagrams. If you would like to learn more see the Resources
page for more detailed resources on UML.
Classes are composed of three things: a name, attributes, and operations. Below is an example of
a class.
32.
33. SEQUENTIAL DIAGRAM
UML sequence diagrams are used to represent or model the flow of messages, events and actions
between the objects or components of a system. Time is represented in the vertical direction
showing the sequence of interactions of the header elements, which are displayed horizontally at
the top of the diagram.
Sequence Diagrams are used primarily to design, document and validate the architecture,
interfaces and logic of the system by describing the sequence of actions that need to be
performed to complete a task or scenario. UML sequence diagrams are useful design tools
because they provide a dynamic view of the system behavior which can be difficult to extract
from static diagrams or specifications.
Although UML sequence diagrams are typically used to describe object-oriented software
systems, they are also extremely useful as system engineering tools to design system
architectures, in business process engineering as process flow diagrams, as message sequence
charts and call flows for telecom/wireless system design, and for protocol stack design and
analysis.
34. TEST CASES
Module 1: Administration
TEST CASE No. INPUT EXPECTED
BEHAVIOUR
OBSERVED
BEHAVIOUR
Status
1 Press the button to go
to get the information
about Restaurants.
please select from the
following choices
anytime during this
--processing-- Done
35. message
2 Press the button to get
the information about
Facilities.
please select from the
following choices
anytime during this
message
-- processing -- Done
3 Press the button to get
the information about
Schedules.
please select from the
following choices
anytime during this
message
-- processing -- Done
4 Press the button to get
the information about
More Restaurants.
please select from the
following choices
anytime during this
message
-- processing -- Done
Module2: Registration
TEST CASE No. INPUT EXPECTED
BEHAVIOUR
OBSERVED
BEHAVIOUR
Status
1 Press the button to
know about the
address of the
Restaurant ,
Contact-no e.t.c
Please select any
of the option from
the following.
--Processing-- Done
2 Press the button to
know about the
Menu categories
Please select any
of the option from
the following.
-- Processing -- Done
3 Press the button to
know about the
Menu items
Please select any
of the option from
the following.
-- Processing -- Done
4 Press the button to
know about the
Tables or Table
reservations.
Please select any
of the option from
the following.
-- Processing -- Done
5 Press the button to
select the capacity
for Table
reservation.
Please select the
option from the
following.
-- Processing -- Done
6 Press the button to
know about the
Banquet hall or
Banquet hall
reservations.
Please select any
of the option from
the following.
-- Processing -- Done
36. Module3: Feedback & Complaints
TEST CASE No. INPUT EXPECTED
BEHAVIOUR
OBSERVED
BEHAVIOUR
Status
1 Can you provide
us the feedback
Poor
Satisfactory
Good
Very good
excellent
- Processing -- Done
2 Do you have any
complaints
Yes
No
-- Processing -- Done
64. conclusion
All the users in the organization have appreciated the project.
It is easy to use, since it uses the GUI provided in the user dialog.
User-friendly screens are provided.
The usage of software increases the efficiency, decreases the effort.
It has been thoroughly tested and implemented.
futurescope:
VoiceXML (VXML) is the W3C's standard XML format for specifying interactive voice
dialogues between a human and a computer. It allows voice applications to be developed and
deployed in an analogous way to HTML for visual applications. Just as HTML documents are
interpreted by a visual web browser, VoiceXML documents are interpreted by a voice browser.
XML-based programming language for voice applications
Need to describe
System prompt
Expected user response
Action on expected response
Action on inexpected response
Form-filling/Menu metaphor
65. Techniquesto ImproveUserInterface
"Barge-In": User can interupt prompt with answer
Alternate prompts: Vary prompt for input
"Mixed Dialogue": User can give response that does not answer question
Browser: When will you arrive at the hotel ?
User: I need to rent a car
Browser: Which company do you prefer ?
Future versions of the standard
VoiceXML 3.0 will be the next major release of VoiceXML, with new major features. It
includes a new XML statechart description language called SCXML.
APPENDIX
java:
Java is a programming language which derives much of its syntax from C and C++ but has a
simple object model and fewer low-level facilities, java applications are typically complied to
bytecode that run on any Java Virtual Machine(JVM) regardless of computer architecture. Java is
general purpose, concurrent, class-based, and object-oriented, and is specifically designed to
have as few implementation dependencies as possible. It is intended to let application developers
"write once, run anywhere".
JDBC:
Java Database Connectivity is the general way to connect to an external database from Java, it
uses SQL to access and update the database. The benefits of this are that the access to the
66. database is incredibly quick. Its ease of use, standards compliance, full feature set, and small
footprint make it the ideal database for Java developers. Java DB is written in the Java
programming language, providing "write once, run anywhere" portability. It can be embedded in
Java applications, requiring zero administration by the developer or user. It can also be used in
client server mode. JDBC has a set of drivers which allow it to connect with the DBMS.
There are four types of JDBC drivers known as:
JDBC-ODBC Bridge plus ODBC driver, also called Type 1.
Native-API, partly Java driver, also called Type 2.
JDBC-Net, pure Java driver, also called Type 3.
Native-protocol, pure Java driver, also called Type 4.
Tomcat5.0:
Tomcat is written entirely in Java, you have access to the entire code if you want to make
changes. Tomcat is an open source, Java-based Web application container that runs servlet and
JSP Web applications. Tomcat is supported and maintained under the Apache-Jakarta subproject
by volunteers from the open source Java community. Tomcat Server is the reference
implementation for the servlet and JSP specifications, so it's probably safe to say that Tomcat
Server implements the Apache-Jakarta specifications as well or better than most commercial
application servers.
myeclipse:
It's the basic graphical interface you work with when you use Eclipse. It's got all kinds of
toolbars and menus for you to use, and its job is to present those items and the internal windows
One huge feature of Eclipse is that it automatically compiles your code in the background. You
no longer need to go to the command prompt and compile code directly.This means that errors
can be corrected when made.
oracle10g:
Within Oracle there are a set of tables and views that are able to give you information on the
objects that you create. These sets of tables and views are called the data dictionary. All you
need to do is query these views with simple SQL statements and you can see how you have defined
the objects and the relationships between objects you might have defined.
svn:
In software development, Apache Subversion (command name svn) is a revision control system
Developers use Subversion to maintain current and historical versions of files such as source
code, web pages, and documentation. Its goal is to be a mostly-compatible successor to the
67. widely used Concurrent Versions System (CVS).The corporate world has also started to adopt
Subversion. SVNRepository provides an interface for protocol specific drivers used for direct
working with a Subversion repository. SVNRepository joins all low-level API methods needed for
repository access operations. In particular this low-level protocol driver is used by the high-level
API when an access to a repository is needed.
Differencebetweenwebserverand applicationserver:
a)Webserver serves pages for viewing in web browser, application server provides exposes
businness logic for client applications through various protocols
b)Webserver exclusively handles http requests.application server serves bussiness logic to
application programs through any number of protocols.
c)Webserver delegation model is fairly simple,when the request comes into the webserver,it
simply passes the request to the program best able to handle it(Server side program). It may not
support transactions and database connection pooling.
d)Application server is more capable of dynamic behaviour than webserver. We can also
configure application server to work as a webserver.Simply applic! ation server is a superset of
webserver.
e)An Application server has a 'built-in' web server, in addition to that it supports other modules
or features like e-business integration, independent management and security module, portlets
etc.
68. BIBLIOGRAPHY
References
The primary references of this project are
http://www.google.com
http://msdn.microsoft.com
Wrox Publications (BOOK: Professional SQL Server 2005 Programming ISBN: 0-7645-
8434-0 )
