Srs Final

SOFTWARE REQUIREMENTS
SPECIFICATION
Travel Freak
IS-14
Software Requirements Specification for TravelFreak
Travel Freak
Group project (IS-14)
Supervisor:
Mr. Viraj Welgama
Mentor:
Ms. Nimali Wasana Hettiarachchi
Ms. Hamsavasani
Group members
Name Index Number Registration Signature

Number
S Thirumalan 17020875 2017/IS/087
J P E Dilshani 17020247 2017/IS/024
P B Wimalasooriya 17021006 2017/IS/100
I Thanabalasingam 17020859 2017/IS/085
2 | Page
Table of Contents
1. Introduction
1.1 Purpose
1.2 Document Conventions
1.3 Problem Domain
1.4 Proposed Solution
1.5 Vision
1.6 Goals and Objectives
1.7 Project Scope
1.8 References
2. Overall Description
2.1 Product Perspective

2.2 Product Features
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Design and Implementation Constraints
2.6 Assumptions and Dependencies
3. Feasibility Study
3.1 Operational Feasibility

3.2 Technical Feasibility
3.3 Economic Feasibility
3.4 Legal and Ethical Feasibility
3.5 Schedule Feasibility
4. Requirements
4.1 Stakeholders
4.2 Use Cases and Use Case Diagrams
4.3 Use Case Narratives
4.4 Functional Requirements
4.5 Non-functional Requirements
3 | Page
5. Proposed System Architecture
5.1 High-Level Architecture

5.2 Components and Their Responsibilities
5.3 Component Interactions
6. System Design
6.1 Class Diagram

6.2 Sequence Diagram
6.3 Activity Diagram
7. User Interface Flow Diagram
8. User Interface Mockups
4 | Page
1 Introduction
1.1 Purpose
The purpose of this document is to give a detailed description for the system “Travel Freak”.
It will illustrates the complete declaration for the development of system. It will explain the
system interfaces, related diagrams, functions and expectations of the system.
1.2 Document Conventions

SRS- Software Requirement Specification
1.3 Problem Domain

Most of the people who are involving in tourism in Sri Lanka such as guides, drivers and
equipment providers are not get much customers. Also most of the tourism businesses are in
the big companies’ hands. So tourists who visit Sri Lanka face many difficulties when they find a
good service. Sometimes they pay too much and not get a satisfying service. Sometimes they
visit some places and miss some attracting places near that area. Also they find difficulties while
their search for directions. All these are happening because service providers mainly who work
as individuals haven’t platform to connect with tourists directly.
1.4 Proposed Solution

We propose a web based platform- “TravelFreak” to bridge the gap between tourist, guides,
drivers and equipment providers in Sri Lanka. Using this system tourists can connect with the
service providers who are in the area he or she going to visit. At the same time, service
providers can connect with the tourists and give their service for the affordable prices.
5 | Page
1.5 Vision
Our vision is to make every tourist who visit Sri Lanka use TravelFreak for connect with service
Providers and be the most trusted and innovative travel management system in Sri Lanka.
1.6 Goals and objectives

Our primary goal is to provide the best travelling experience to the tourists through our online
travel and tourist management system. It will provide a search platform where a tourists
can find their preferable places to travel and search for service providers near to that
area. Our intend is to achieve this through following objectives.
● Providing a online platform to connect tourists and service providers

● Creating a open market for tourism industry in Sri Lanka
● Encouraging people who are doing tourism as a part time job
● Encouraging tourists to visit Sri Lanka
1.7 Project Scope

In-bound scope
• Connect the tourists and tourist service providers like guides, drivers and equipment
providers.
• Payment handling for the equipment providers.
• Provide tips and announcements on tourism.
• Tourists map and image gallery. When click on a district in map we can show tourist
attraction places and details
• Forum chat
• User rating system
• Advertisements on tourism
Out-bound scope
• Mobile app
• Publicity of the site
• Multiple languages
6 | Page
1.8 References
System Analysis and Design Methods - Jeffrey L Whitten and Lonnie D Bentley
(Chapter 11 - Feasibility Analysis and the System Proposal)
2 Overall Description
2.1 Product Perspective

• TravelFreak is a platform which connects service providers with tourists. It will reduce
the communication barriers among them. They can interact with each other and get a
service as they wish. TravelFreak will be available as a web application. Therefore our
system will be accessible through desktop tablets and mobile phones.
2.2 Product Features

● Allows tourists to connect with service providers.
● Allows service providers to post their advertisements
● User rating system for both service providers and tourists
● Forum chat for tourists and customers
● Payment system for equipment providers to get advance payments
2.3 User classes and characteristics
Three types of users will use our system
● System administrator
● Registered user
● Unregistered user
System Administrator
System Administer has the highest power over the system management. He or she can add or
remove any user, news, advertisement or any other thing which posted in the system. Also they
can controlling the community inside the system.
Registered User
7 | Page
Both registered tourists and service providers will be concerned as registered users. Mainly
there are three types of service providers in the systems, drivers, guides and equipment
providers.
Unregistered Users
People who visit the website are concerned as unregistered users. They can view limited
information of the system.
2.4 Operating Environment

TravelFreak will be operated as a website. It will be accessible through any internet enabled
mobile tablet or PC. Since we are dealing with tourists it will be offered only in English.
2.5 Design and Implementation Constraints and Limitations
● TravelFreak is not concerned with the money transactions among service providers and
customers.
● Users should have proper internet connection to access the system
● System is only responsible for connect the service providers with tourists.
2.6 Assumptions
Assumptions
● Users have proper internet connection to access the system

● Users are providing their true information. In case of the information provided is
proved to be false, the user will be removed from the site.
● Users would have enough literacy to use the website.
● Tourists rate service providers and give feedback honestly.
● Users are not share their passwords among others
● Users will act responsibly when posting advertisements and chat in the forum
● Service providers update their availability on time
8 | Page
3 Feasibility Study
3.1 Operational feasibility
TravelFreak will really benefit to the people who are in tourism industry.
● We have surveyed over 100 people who are in Sri Lanka as well as in other countries
about the travel and tourism in Sri Lanka. Most of the people said there is no proper
website to connect with guides and drivers with tourists and they interested in our idea
● The system will be easy enough to handle.
● The proposed system has user friendly GUI
3.2 Technical feasibility
● TravelFreak is a web-based platform will be developed using Angular, HTML, CSS and
Javascript as the front end and using mysql database for the backend. These
technologies are available for develop freely and the team members are familiar with
this technologies we have choose them for implementation process.
● The Internet Facilities are currently available, most of the people and more people are
interested in website, so there is no technical issue occurred from users.
● The proposed System is completely liable with proper backup and security.
● The proposed system is capable of holding data to be used securely.
3.3 Economical Feasibility
● In our system no registration fee would be charged when a new user creates an
account.
● The development tools can be used free of charge.
● We use xamp server. Therefore we will not be charge for the web server
● We are not publishing the app. So publicity chargers will not applicable
9 | Page
● since this is a university project there is no cost for developers
3.4 Legal & ethical feasibility
● We are protecting privacy of all users. But we are not responsible for the information
given as users.
● Contact details and other private details of users allowed to view only for registered
users of the system. They stored in the database and if there will be any legal or ethical
issue, system administrator have the authority to remove user from the system. The
system administrator should be granted permission to delete any feedbacks, are
unethical. This should if any unethical behavior happens that user have to inform the
admin and admin will get the action.
3.5 Schedule feasibility
● We are developing this system using incremental development methodology. Therefore

rather than delivering a system as a single delivery, we broken down development and
delivery into increments and prioritized them. Then highest priority increment is tackled
first. Our project delivery timeline is as follows.
Project delivery timeline: Gantt chart
10 | Page
4 Requirements
4.1 Stakeholders
Stakeholders are the people who interact with the system. Tourists, service providers and
administrators are stakeholders of this system.
● Tourist
Tourist is a user of the system whose objective is to find service providers. They can search for
service providers according to places they are going to visit and get connected with
them.
● Service provider
Service provider is a user of the system whose objective is to post their details and connect with
the tourists. In here we’re defined guides, drivers and equipment providers as service
providers. Equipment providers are the people who provide tents, barbecue sets and
other equipment related to the trips.
● Administrator
Admin is a user of the system whose objective is to manage users and control the system.
11 | Page
4.2 Use cases and Use case diagrams
Tourist
12 | Page
Guide
13 | Page
Equipment provider
14 | Page
Driver
15 | Page
Admin
16 | Page
4.3 Use Case Narratives
Use case name: Creating account
Use case Id: O1
Priority: High
Primary business actors: Tourists, Service providers
Other participating actors:
Description: ● User visit travel freak.

● Click Sign up button.
● Select the user type (tourist or service provider)
● Add details to the registration form
● Submit the form
● Admin approve the form
Pre-condition: Actor have stable internet connection and device to access
internet
Actor should visit travel freak
Post-condition: Check all the fields of the form are filled.
Use case name: Login
Use case Id: O2
Priority: High
Primary business actors: Admin, Tourists, Service providers
Description: ● Primary actors visit to the travel freak

● Click sign in button
● Enter username and password
● System check Username and password
● If username and password is valid and matched then
system give access to related profile page.
17 | Page
internet
Post-condition: Check all the fields of the form are filled.
Use case name: Add service provider details
Use case Id: O3
Priority: High
Primary business actors: Service providers(Drivers, guides, equipment providers)
Description: ● User login to the system

● Visit own profile page
● Add or edit details
internet
Post-condition:
Use case name: View service provider’s details
Use case Id: O4
Priority: High
18 | Page
Primary business actors: Tourists
Other participating actors: Service providers
Description: ● Tourists visit travel freak

● Log in to the system
● Select a category Driver , guide or equipment provider
● Search for available service providers
● View details of services and products
internet
Post-condition:
Use case name: Contact service provider
Use case Id: O5
Priority: High
Primary business actors: tourists
Description: Tourists log in and view service providers
Drivers & guides
● Chose a driver or guide

● Send a request to connect.
Equipment providers
● Choose a suitable package for rent

● Choose suitable items for rent
● Add to cart
19 | Page
internet
Post-condition: Tourist can see all the information about service providers after
service providers accept their requests
Use case name: View own profile
Use case Id: 06
Priority: low
Other participating actors: none
Description: ● Actor login to the system

● Click my profile
internet
Actor should be logged into the system
Post-condition:
Use case name: Update own profile
20 | Page
Use case Id: 07
Priority: medium
Description: Actor login to the system
Click my profile
Edit details
internet
Actor do not need to login to system to view forum.
Post-condition:
Use case name: Tourists search for service providers
Use case Id: 08
Priority: medium

● Select service providers type from the navigation bar
internet
Actor should logged into the system
21 | Page
Post-condition:
Use case name: Add availability
Use case Id: 09
Priority: High
Primary business actors: Service providers
Other participating actors: none

● Click my profile
● Select availability on/off
● Select available time period
internet
Actor should logged into the system
Post-condition:
Use case name: Accept/ reject user requests
Use case Id: 10
Priority: low
Primary business actors: Admin

● When service provider/ tourist send a request admin can
add /delete request
internet
22 | Page
Post-condition:
Use case name: Add/ reject user requests(by tourists)
Use case Id: 11
Priority: low
Other participating actors: tourists

● View user requests
● Click confirm or delete
internet
Post-condition:
Use case name: Remove user
Use case Id: 12
Priority: medium

● Select service providers on navigation bar
● Select user
● Click remove user
23 | Page
● confirm
internet
Post-condition:
Use case name: Edit/ delete posts
Use case Id: 13
Priority: low

● Click home
● Click news and announcements
● Click edit or delete for updates
● Click save
internet
Post-condition:
Use case name: View posts
Use case Id: 14
Priority: low
24 | Page

● Click home
● View posts
internet
Post-condition:
Use case name: Rate posts
Use case Id: 15
Priority: low

● Click home
● Select up vote or down vote
internet
Post-condition:
25 | Page
Use case name: Payment to service providers
Use case Id: 16
Priority: medium
Primary business actors: Tourist, equipment providers
Other participating actors: admin
Description: ● Tourist login and chose item and packages from

equipment providers
● Items are on the cart
● Tourists pay advance
● System send notification for request.
internet
Post-condition:
Use case name: Rate and give feedback for service providers
Use case Id: 17
Priority: medium
Description: ● Tourist log in to travel freak

● Select rate service providers.
● The list of the service providers whom tourist have got the
service will be shown
● Select one service provider
● Rate the user using star rating.
● System record the rate
● System calculate average rate and display on the website.
● Give feedback about the service provider
26 | Page
● Feedback will show on service providers details
internet
Actor should take the service of the service provider. otherwise he

can’t rate
Post-condition:
Use case name: Rate users (tourists)
Use case Id: 18
Priority: medium
Other participating actors: tourists
Description: ● Service provider log in to travel freak

● Select users
● The list of the tourists whom service providers have got
the service will be shown
● Select one of the tourists
● Rate the tourists using star rating
● System record the rate
● System calculate average rate and display on the website
● Give feedback about the tourists
● Feedback will show on service providers details
internet
Actor should take the service of the service provider. otherwise he

can’t rate
Post-condition:
27 | Page
Use case name: View feedback
Use case Id: 19
Priority: low

● Click feedbacks
● Click view feedbacks
internet
Post-condition:
Use case name: Forum chat
Use case Id: 20
Priority: medium

● Click Forum button and go to Forum page.
● Add any question
● Answer that questions if user know the answer.
28 | Page
internet
Post-condition:
Use case name: View Map & image gallery
Use case Id: 21
Priority: high
Primary business actors: Tourist ,Admin
Description: ● Tourist visit to travel freak

● Click on view map
● Tourists attraction placers will be shown according to
province
● Click on a province will show places to visit with the images
internet
No need to log in
Post-condition:
Use case name: Post Announcements & advertisements
29 | Page
Use case Id: 22
Priority: medium
Primary business actors: Tourists, admin
Description: ● Admin log into system

● Put announcements and advertisements regarding tourism
internet
No need to log in
Post-condition:
Use case name: Report users
Use case Id: 23
Priority: low
Primary business actors: tourist

● Click on service providers on navigation bar
● Select service provider whom got the service before
● Report user
● System stores the complaint
30 | Page
internet
Post-condition:
4,4 Functional Requirements

This chapter contains information about the functional requirements according to different
users of the system Travelfreak.
Service providers
31 | Page
Edit their own profile
In Travelfreak all the types of service providers have to create a profile to join the
system. So they have to add their some personal details such as name and age and
contact details like email address and contact number and other details like working
experiences. After that if they need to change or modify their information they can edit
their profile. Service providers can change their availability when they’re available. So it
will be appear when customers search for services.
Accept or reject tourists requests

Tourists can send requests to service providers. Then service providers can accept them
and get connected with them through web site.
View user ratings and feedback

Travelfreak has a rating system that users can rate and give feedbacks on service provider’s
services after getting it. Then service providers can view them. With this rating
system highly rated service providers are more recognize when tourist searching for
them.
Tourists
Contact service providers

Tourists can contact service providers by sending requests to them.
Rate service providers and give feedback

Tourists can rate service providers and give feedbacks on them after getting the service
View service providers and other details

Tourists can view service provider’s details such as their availability and they can view site
announcements.
Administrator
32 | Page
Add users and delete users

Admin can approve users to the system by accepting their requests. They have given
unrestricted access for the system for take immediate actions such as delete users if
required.
Contact users
Admins can contact users via messenger through the system.
Post site announcements and add site details

Admin can post tourists tips and site announcements to the site. Also they can add new places
and images for the tourist map and image gallery.
4.5 Non- functional requirements

User friendliness
▪ System is easy to use for all users. Icons and images used in the system should be
visible and discernible regardless of the device used. Users can easily search for
locations using tourist map we provided.
Portability
▪ The web platform is available in any devices whether it is mobile phone, pc or tablet
Privacy & Security

▪ Users have control on their personal details such as their pictures, email address and
contact details. The system ensures that the identities of all users are secured.
Availability
▪ Website is available in 24x7. Users can get interact with the system at any time as
they wish.
33 | Page
5 Proposed System Architecture

5.1 High level Architecture
5.2 Components and their responsibilities
Hardware components
Hardware components help users to interact with the system.
All the users (service provider, clients, admin) can interact with system using different
device such as desktop, laptop, mobile phones and tabs.
Web Server
Web server store our webpages and provide relevant web pages to relevant user.
Web server get request from the user and send it to the system as well as get response
from system and send it to the user devices.
34 | Page
Travel Freak System

Travel Freak system is the main component which involve all the activities that user
done by the system.
If the user want some data from the database that user request go through this
Travel Freak system.
Database server
When user want some data from our system and user request it from the system, the
system is request that data from database through database server.
Database server helps to get correct data from database.
Database
Database is storing all the data of the system and users.
Those data store in different tables in database.
5.4 System Architecture
Presentation tier
User of Travel Freak system directly interact with the tier.
All type of users (Clients, Service provider, Admin) have their own profiles pages in this layer. This layer
will consist of all static web pages and other user interfaces.
35 | Page
Anyone can access the static web pages.
Those are
● About us
● Contact us
● Site map
● Blog
When user login to system he/she can access his/her own profile page.
There are many pages that can access more than one user so he/she also can access all of it.
Application tier
Application tier controls application functionality by performing detailed processing.
The diagram in upside describe the application tire of our systems.
Data tier
Data tier include the database of the system. All the details and information of the system are store in
this tier and retrieve it to other tiers.
5.3 Component Interactions
36 | Page
1 System Design
6.1 ER diagram
37 | Page
6.2 Class Diagram
38 | Page
6.3 Sequence Diagram
1.Sequence Diagram for signup process TravelFreak
39 | Page
This represents how an unregistered user can go through the signup process to
enter
in to the TravelFreak community.
2.Sequence Diagram for login process in TravelFreak
40 | Page
This diagram represents the login procedure for a user who wish to sign in to
TravelFreak.This procedure is common for all registered users including Admin.
3.Sequence Diagram for accepting a listed order in TravelFreak.
41 | Page
This represents a process where have seen a listing they like and they send a
request for the Service provider (which is also another user) to make an agreement
to that listing. This request is sent to the lister where the service provider can accept
or reject according to their preference.
4.Sequence Diagram for tourists function requirements in TravelFreak.
42 | Page
5.Sequence Diagram Admin functions in TravelFreak.
43 | Page
6.4 Activity Diagrams
44 | Page
45 | Page
46 | Page
47 | Page
2 User Interface Flow Diagram
48 | Page
49 | Page
3 User Interface Mockups
50 | Page
51 | Page
52 | Page
53 | Page
54 | Page
55 | Page
56 | Page
57 | Page
58 | Page
59 | Page
60 | Page
*************************************************************************************
61 | Page

Srs Final

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Srs Final

Încărcat de

Drepturi de autor:

Formate disponibile

SOFTWARE REQUIREMENTS

Mr. Viraj Welgama

Ms. Nimali Wasana Hettiarachchi

Name Index Number Registration Signature

2.1 Product Perspective

3.1 Operational Feasibility

5. Proposed System Architecture

5.1 High-Level Architecture

6.1 Class Diagram

7. User Interface Flow Diagram

8. User Interface Mockups

1.2 Document Conventions

1.3 Problem Domain

1.4 Proposed Solution

1.6 Goals and objectives

● Providing a online platform to connect tourists and service providers

1.7 Project Scope

(Chapter 11 - Feasibility Analysis and the System Proposal)

2.1 Product Perspective

2.2 Product Features

2.3 User classes and characteristics

Three types of users will use our system

2.4 Operating Environment

2.5 Design and Implementation Constraints and Limitations

● Users have proper internet connection to access the system

3.1 Operational feasibility

● The system will be easy enough to handle.

● The proposed system has user friendly GUI

3.2 Technical feasibility

● The proposed system is capable of holding data to be used securely.

3.3 Economical Feasibility

● The development tools can be used free of charge.

● since this is a university project there is no cost for developers

3.4 Legal & ethical feasibility

3.5 Schedule feasibility

● We are developing this system using incremental development methodology. Therefore

Project delivery timeline: Gantt chart

4.2 Use cases and Use case diagrams

4.3 Use Case Narratives

Use case name: Creating account

Use case Id: O1

Primary business actors: Tourists, Service providers

Other participating actors:

Description: ● User visit travel freak.

Pre-condition: Actor have stable internet connection and device to access

Actor should visit travel freak

Post-condition: Check all the fields of the form are filled.

Use case name: Login

Use case Id: O2

Primary business actors: Admin, Tourists, Service providers

Other participating actors:

Description: ● Primary actors visit to the travel freak

Pre-condition: Actor have stable internet connection and device to access

Actor should visit travel freak

Post-condition: Check all the fields of the form are filled.

Use case name: Add service provider details

Use case Id: O3

Primary business actors: Service providers(Drivers, guides, equipment providers)

Other participating actors:

Description: ● User login to the system

Pre-condition: Actor have stable internet connection and device to access

Actor should visit travel freak

Use case name: View service provider’s details

Use case Id: O4