Online Tour Guide
Part A
Functional Requirements
Registration
To register a person in order to be a member of the website. Visitors use
their e-mails as the sole identifiers to register. Fill in e-mail, password,
and re-enter the password when register. Then the system store the
details and generate a CIN as the output.
Login
Users need the e-mails and passwords to log into their main interfaces.
If the password or e mail is wrong system generate an error message.
Query and Browse Destinations
Visitors can find destinations in the hierarchical structure without
register. Destinations are arranged in a Province – City – A,ractions
structure, in which province, city and a,raction pages are separated.
A,raction is the smallest unit. In the a,raction page, visitors can browse
its general introduction, tra-c information, weather, a,raction
evaluation, a,raction pictures, travel notes and the information of
surrounding commercial facilities
Add / modify Province – City – A,ractions
Information package
Tourist a,ractions are logically organized in Province – City – A,ractions
hierarchy according to geographic location. The administrator is
responsible for maintaining such hierarchy. When new a,raction needs
to be added, the administrator should add introduction, tra-c
information, and weather conditions for the new a,raction on the new
a,raction’s page. When a,raction information is updated, the
administrator can modify the tourist a,raction information page.
Pay for services
This is how the user make the payments. we have to type our email,
credit card details and CIN as the input. In the process the new balance
in the card get update. As the output we get the tour details of our tour
plan.
Part B
Non Functional Requirements
Performance Requirements
As for web-based information systems, performance requirements can
help designers and developers to define system behaviour under
di3erent loads. Performance is often an important criterion to measure
usability of the system. The most important thing of user experience is
often relevant to performance, including waiting time, throughput, and
stability and so on. Tour system should meet the following performance
requirements:
1. Response Time
A more common definition counts from when the user sends a
request to when the last byte reaches the user’s end. Page response
time means the time required to load a page. The time unit is
normally second or millisecond. Average page response time of the
system should be within 3 seconds.
2. System Capacity
Tour system should be able to support many registered users.
suffcient database space is required. In addition, the system should
support simultaneous online users and allow concurrent users
