Software Requirements Specification about Tour guidance

1. Software Requirement Specification for Framework for generating
tour plans for adaptively guiding a tourist
Faculty of Applied sciences
Rajarata University of Sri Lanka
2016
Name Index No
L.D.A.P.M. LIYANAGE 3068
H.M.S.U.WIJEBANDARA 3103
H.N.S. HEWASINGHE 3057
W.S.D. HANSIMA 3054
M.T. P. BHANUKA 3043
H.W.M.C.S.B.W.HERATH 3056

2. ii
Software Requirement Specification for Framework for generating
tour plans for adaptively guiding a tourist
Faculty of Applied sciences
Rajarata University of Sri Lanka
2016

3. iii
Contents
Page
1. Introduction 4
2. Overall description 5
3. Functional requirements 5
4. Nonfunctional Requirements 15
5. ER diagramand Classdiagramfor Businessdomain. 18

4. 4
1. Introduction
1.1.Purpose of this Document
This document focuses on describing the software requirements of project, a Mobile
framework for generating tour plans. This project would be carried out to meet the
software development requirements of the ICT-3411 module conducted by the
Faculty of Applied Sciences Rajarata University of Sri Lanka. The document focuses
on all the functional, non-functional, performance and security requirements of the
project.
1.2.Scope
Mobile framework for generating tour plans is developing a framework for generating
tour plans for adaptively guiding a tourist.
The develop framework for developing an application that is in full compliance with
the business rules, that is structured, optimizing, and that is both maintainable and
upgradable.
The generating trip suggestion for given condition & generating the plan is collect the
entire tourist relating preferences as the route and the budget optimization and these
gathered data are stored in the framework and implemented as a mobile app that takes
into account the interests and trip constraints of the user and matches these to a
database of locations in order to predict personal interests.
Optimizing the generated plan is planning algorithm provides the suggestion of a trip
for a requested minimum budget of the customer, the critical shortest routes
Providing the navigation with information support is how to reach preferred places
can be got through the Google map and Google Street- view and usage statistics and
user feedback demonstrate that it is highly appreciated by tourists.

5. 5
2. Overall description
2.1. Product Perspective
This project is to plan the overall trip according to budget and route preferences of
tourist which will give more competitive advantages. And make them satisfy with the
Sri Lankan culture. Therefore the tourist who visits Sri Lanka can manage their
valuable time as well as the money in the way of effectively as well as efficiency.

6. 6
3. Functional Requirements
3.1. Use case diagram

7. 7
3.2. Actors and Use cases
Admin and Users are the main actors according to the use case
̵ Admin:
The user and the system which gives trip suggestions, update the tour, manage the
cost, and manage the route is managed by the Admin.
̵ User:
User can give the preferences, get the optimal plan and can view the trip plan and
booking. Visitors are one category under users. The site can be viewed by victors
and feedback can be given.
Admin
Use case no 01
Use case name Login
Actor Admin
Pre-condition Display the main screen
Description 1. User enter the password and username and press the submit button.
1.1.Does not enter the username
1.2.Does not enter the password
1.3.Enter the incorrect username
1.4..Enter the incorrect password
2. System verifies the user name, password, user type.
2.1. Fail the verification
Post condition User redirects the relevant interface.
Flow of events 1. System display login interface.
2. Enter username and password.
3. System validates username and Password.
4. System determines user type.
5. Direct to the relevant interface.
Alternatives A1. User does not enter the login button.
A2. User submits the form with empty field.
Exceptions E.1.User submit the empty field

8. 8
Description :- If checks the emptiness.
Post-condition :- Display error message.
“Fill the form properly”
E.2.Fail the verification
Pre-condition:- Display the main screen with user name and password.
Description :- System checks the user name, password and user type.
Use case no 02
Use case Registration
Actor Admin
Description Cannot be registering the new admin.
Use case no 03
Use case Manage user
Actor Admin
Description View the details of the user
Pre-Condition Display the main menu of the admin
Flow of events 1) Admin click ‘manage user’ button.
2) Displays for user detail in database.(request and cancel trip details)
3) Enter the name of user to be Manage.
4) Check for user detail in database
Alternative 1) User clicks manage user button
2) Enter the name of the user to be managed
3)Check for user detail in database
4) Unavailability of user information in the database
5) Displaying ‘no such user’
Post-Condition Display the user Details
Assumption Administrator can checks all existing user
Use case no 04
Use case View feedback

9. 9
Actor Admin
Description View feedback of users about the mobile app and view comments about trip
planner service
Pre-condition Admin should view feedback from the user.
Flow of events 1. click a link name as “feedback”
2.After click the link can go to the place that stored those feedback
3. View all feedback and save them.
Post-condition View the user comments.
User
Use case no 05
Use case name Login
Actor User
Pre-condition Display the main screen
Description 1. User enter the password and username and press the submit button.
1.1.Does not enter the username
1.2.Does not enter the password
1.3.Enter the incorrect username
1.4..Enter the incorrect password
2. System verifies the user name, password, user type.
2.1. Fail the verification
Post condition User redirects the relevant interface.
Flow of events 1. System display login interface.
2. Enter username and password.
3. System validates username and Password.
4. System determines user type.
5. Direct to the relevant interface.
Alternatives A1. User does not enter the login button.
A2. User submits the form with empty field.
Exceptions E.1.User submit the empty field
Description :-“If checks the emptiness”

10. 10
Post-condition :- Display error message.
“Fill the form properly”
E.2.Fail the verification
Pre-condition:- Display the main screen with user name and password.
Description: - System checks the user name, password and user type.
Use case no 06
Use case Registration
Actor User
Description 1. User enters the username, password, and contact no and E-mail address.
Then press the submit button.
1.1.Does not enter the username
1.2.Does not enter the password
1.3.Does not enter the E-mail address
2. System verifies the user name, password and E-mail Address.
2.1. Fail the verification
Pre-condition Display the main screen of the user
Flow of events 1. Display the registration interface.
2. Enter username, password and E-mail Address.
3. System validates username, Password and E-mail.
4. System determines user type.
5. Direct to the relevant interface.
Alternatives A1. User does not enter the submit button.
A2. User submits the form with empty field
Exceptions E.1.User submit the empty field
Description :-“If checks the emptiness”
Post-condition :- Display error message.
“Fill the form properly”
E.2.Fail the verification
Pre-condition:- Display the main screen with user name and password.
Description: - System checks the user name, password and user type.
Assumption 1.Requesting membership:
Should be unregistered before.

11. 11
2.Registering user:
Should be a new user.
Should undergo the customs and rules of the system.
Use case no 07
Use case Give The Preferences
Actor User
Description Give the preferences for the trip planner to plan the trip.
Pre-condition User should log or register in the system
Flow of events 1. Give the form for fill the user.
2. Enter the submit button.
3. Direct to the relevant interface.
Use case no 08
Use case Get the trip suggestions
Actor User
Description Get the trip suggestions form the trip planner.
Pre-condition User should give the preferences to the trip planner.
Flow of events 1. Display the existing trip suggestions.
2. Select one or more you want to visit.
3. Enter the submit button.
Use case no 09
Use case Give Payments
Actor User
Description User can pay credit for the requested trip plan
Pre-condition User should have request a trip and should have confirm it
Flow of events 1. After confirm the trip plan click button “payments”
2. System asks the way (credit card/debit card) paying for the trip plan.
3. Give feedback for questions ask by the system
4.Give the payments
Use case no 10
Use case Cancel the requested trip
Actor User
Description User can cancel the trip before attend it
Pre-condition User should have request a trip and confirm it

12. 12
Flow of events 1. Click a button called “cancel trip”.
2. System asks reasons for cancelling trip through a form.
3. Give reasons.
4.Cancel the payments
5.Cancel the trip
Use case no 11
Use case Give feedback
Actor User
Description Give feedback about the mobile app and give comments about trip planner
service
Pre-condition Display the interface for enters the comments.
Flow of events 1. Display the form to give feedback
2. Comment on that form.
3. Enter the submit button.

13. 13
3.3Activity diagrams
Admin

14. 14
User

15. 15
4. Non - functional Requirements
4.1. Product Requirements
4.1.1. Usability Requirements
 A user interface for updating tour information would also be
useful in allowing the system to be adapted for different
situations.
4.1.2. Efficiency requirement
 The application should be able to maintain all the data files
stored in the system.
 The application should be able to provide quick response to the
users’ requests.
4.1.3. Performance Requirements
 The application should be able to respond to the queries
submitted by the customer without delay. When a user searches
for a tour location, the application should not take much time to
return the results.
4.1.3.1. Space requirement
 The system should be able to handle large amount of data.
4.1.3.2. Reliability Requirements
 The application should under normal conditions, perform the
required functions successfully.
4.1.4. Portability requirement
 The application will be user friendly.

16. 16
 The system should be able to be handled from any place
without barrier.
4.2. Organizational Requirements
4.2.1. Delivery requirement
 The Application must be delivered within eight months.
4.2.2. Implementation requirement
 The system can be used by all kind of users who are familiar
with the mobile.
 System shall provide help desk supporting to solve the
technical problems of the users.
4.2.3. Standard requirement
 The system should comprise of the standard requirements for
the users and the content of the framework.
4.3. External requirements
4.3.1. Interoperability requirement
 External database provides a single point of update to the
system and reduces the size of the application. Having a light
weight application increases the systems usability and
reliability.
 There should be a separate account for admin.
4.3.2. Ethical requirement

17. 17
 The main ethical problem we faced is the problem of tourist
protection. The design of the device in generating tour plans for
adaptively guiding a tourist and travel to safe journey.
4.3.3. Legislative requirements
4.3.3.1. Privacy requirements
 Normal users can just read information but they cannot edit or
modify anything except their personal and some other
information.
 Different access levels will be implemented so that some actions
are prohibited to some users.
4.3.3.2. Safety requirements
 Use unique member id to prove user authentication and
validation of members.
 Personal information should be protected.
 There are no perceived risks for any external party or to the
property.

18. 18
5.1. ER Diagram

19. 19
5.2.Class Diagram
1
1
1
1 1
1
Admin
-User_name
- password
-
+manage ()
+view profile
()
Customer
-Customer_id: int
-name: int
-Address: char
-email: char
-phone: num
+Registration ()
+view ()
Trip plan
-Trip_id: int
-Trip name: char
+Registration ()
+Manage ()
Payment
-Payment_id: int
-type: char
-Trip_id: int
+Manage ()
Feedback
-feedback_id: int
-Date:date
-C_name: char
+Manage ()
Feedback