Professional Documents
Culture Documents
Tourist Buddy
Version: [1]
Project Code C 01
Supervisor Sir Abul-Rahman
Co Supervisor Sir Muhammad Nadeem
Submission Date
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
[Instructions]
- No section of template should be deleted. You can write ‘Not applicable’ if a
section is not applicable to your project. But all sections must exist in the final
document.
- All comments/examples mentioned in square brackets ([]) are in the template for
explanation purposes and must be replaced / removed in final document.
- This’ Instruction’ section should also be removed in final document.
- MS-Word Reviewing feature must be used to get the document reviewed by
supervisors or co-supervisors.
Page 2 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Document History
[Revision history will be maintained to keep a track of changes done by anyone in the document.]
Version Name of Person Date Description of change
Yousuf 22/09/2017 Document Created
Yousuf 22/10/2017 Document Revised
Ammar,Yousuf 23/10/2017 Document Edited
Ammar,Junaid 24/10/2017 Document Revised
Junaid 24/10/2017 Use cases added and Document
Revised.
Page 3 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Distribution List
[Following table will contain list of people whom the document will be distributed after every sign-off]
Name Role
Sir Abul-Rahman Supervisor
Sir Muhammad Nadeem Co- Supervisor
Page 4 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Document Sign-Off
[Following table will contain sign-off details of document. Once the document is prepared and revised, this
should be signed-off by the sign-off authority.
Any subsequent changes in the document after the first sign-off should again get a formal sign-off by the
authorities.]
Page 5 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Table of Contents
1. INTRODUCTION ...................................................................................................................................... 7
1.1. Purpose of Document .............................................................................................................. 7
1.2. Intended Audience .................................................................................................................. 7
1.3 Abbreviations ………………………………………………………………………………………...7
1.4. Document Convention ............................................................................................................. 7
2. OVERALL SYSTEM DESCRIPTION ............................................................................................................ 8
2.1. Project Background ................................................................................................................. 8
2.2. Project Scope .......................................................................................................................... 8
2.3. Not In Scope ............................................................................................................................ 8
2.4. Project Objectives ................................................................................................................... 8
2.5. Stakeholders............................................................................................................................ 8
2.6. Operating Environment ........................................................................................................... 8
2.7. System Constraints ................................................................................................................. 9
2.8. Assumptions & Dependencies ................................................................................................ 9
3. EXTERNAL INTERFACE REQUIREMENTS ................................................................................................. 10
3.1. Hardware Interfaces .............................................................................................................. 10
3.2. Software Interfaces ............................................................................................................... 10
3.3. Communications Interfaces ..................................................... Error! Bookmark not defined.
4. FUNCTIONAL REQUIREMENTS ............................................................................................................... 11
4.1. FUNCTIONAL HIERARCHY .............................................................................................................. 11
4.2. Use Cases ............................................................................................................................. 13
4.2.1. [Title of use case] .................................................................... Error! Bookmark not defined.
5. NON-FUNCTIONAL REQUIREMENTS ....................................................................................................... 21
5.1. Performance Requirements .................................................................................................. 21
5.2. Safety Requirements ............................................................................................................. 21
5.3. Security Requirements .......................................................................................................... 21
5.4. User Documentation .............................................................................................................. 21
6. REFERENCES ...................................................................................................................................... 22
7. APPENDICES ....................................................................................................................................... 23
Page 6 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
1. Introduction
1.1 Purpose of Document
This SRS is for our project Tourist Management system version 1.0. This SRS shall discuss
about all the major and minor system requirements. Software requirements specification permits
a rigorous assessment of requirements before design can begin and reduces later redesign. It also
provides a realistic basis for estimating product costs, risks, and schedules. Used appropriately,
software requirements specifications can help prevent software project failure.
1.3 Abbreviations
ML=Machine Learning
Strax = Swift Transaction.
Page 7 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
2.5 Stakeholders
Primary: Developers of the system, the tourist company and the customers.
Secondary: Administrator, Income Tax(on the firm).
Page 8 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Hardware constraints
Programmer must at least have a normal usage pc for the main desktop app and a android
smartphone for the standalone app.
Cultural constraints (includes language etc.)
N/A.
Legal constraints
Tourist’s personal information should be handled carefully without any leaks
User constraints
The user should have basic knowledge of how to use the system’s database and knowledge
on how to use smartphone for the standalone app.
Page 9 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Page 10 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
4 Functional Requirements
4.1 Functional Hierarchy
The Tourist Buddy system is decomposed into main three modules/components.
a. Customer Side (User Application)
b. Administration Side
c. Stand-Alone mobile app
Following part of the section briefly describe the above listed modules.
Customer Side - Friendly Environment (Android App):
Login (User Authentication)
After booking for the tour the tour buddy will provide them an account for signing into the
App. After user Authentication user can have multiple options for checking their trip, places
etc.
Sign In to Application
User will be able to sign in to the application via authorized User ID and Password provided
given by Administration of Tour Buddy.
Status of My Trip
User will be able to view the of his trip after login into the application provided by the tour
buddy. User can check their Hotels reservation, next spot to visits and can be able to edit the
trip.
Packages/Promotions
User can be able to view all the packages provided by the tour buddy and also different
promotions on the Visa cards so that Customer can have a Trip at a low price.
Views
User can be able to see the different views.
Reviews, Facilities provided, Tour Availability, locations etc.
Others
User will be able to view other details containing Reviews aboyt Tour Buddy, complain,
Reviews and Ratings etc.
Page 11 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Administration Side:
Management
Admin will manage everything for the Customer Records. Admin will also take care of the
reservations, Add or delete Trips, FAQ’s etc.
Add Trip
Once Customer want to have a tour. Admin will Add a trip for him according to the Customers
demand and plan the whole trip according to their requirements.
Add Hotel
Once Adding the trip, Admin will Add the hotel to Customers Trip. And later on Admin can
also update the list according to the Customers requirement.
View Trips
Admin can manage and view the whole trip of the Customer. Admin use View trip for the
updates about the trip.
Add new Service
Admin has the option to add the new services for the customers. And to manage their trips
providing the new Services about the Query’s, Help, Receiving complains etc.
Mobile App:
This part is basically machine learning part and it is somewhat new because we are
providing some tools or services to our booked customers so that they could enjoy
their Traveling with free mind. Which includes
Page 12 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Page 13 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Alternate Scenarios:
1a: User will asked to re-enter fields.
Post Conditions
Step# Description
01 After successfully login to the system user will be able to use application.
Page 14 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Scenarios
Step# Action Software Reaction
1. User ask about information
regarding booking
2. User enter information regarding
customer
3. system shows booking types
4. Customer select booking type
Post Conditions
Step# Description
01 Customer will be able to access mobile app.
Page 15 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Post Conditions
Step# Description
01 New trip successfully added
Page 16 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Alternate Scenarios:
1a: if user don’t have any pictures in gallery, open camera.
2a:if style takes too much time, then terminate the process
Post Conditions
Step# Description
01 A style will successfully apply on picture
Page 17 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Post Conditions
Step# Description
01 Information related images shown to images
Page 18 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Alternate Scenarios
1a: if system does not find any information related customer ,show Customer does not exist
2a:
Post Conditions
Step# Description
01 User check previous records and current statistics of customer
Page 19 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
Post Conditions
Step# Description
01 A new booking package will successfully add
Page 20 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
5 Non-functional Requirements
5.1 Performance Requirements
The desktop app shall take initial load time depending on the hardware of the laptop/pc.
The performance of the android application shall also depend upon the hardware of the smartphone.
Page 21 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
6 References
[1]. https://www.qt.io/
[2]. https://www.tensorflow.org/
[3]. http://pandas.pydata.org/pandas-docs/stable/cookbook.html
Page 22 of 23
<CS491 Project-I> Software Requirements Specifications <Version 1.5>
6 Appendices
Appendix A: Project proposal (signed by supervisor)
Page 23 of 23