FlyIn: Exclusive Web Portal for Booking of Charter Flights

Business Requirements Document (BRD)

Version 1.0

VERSION AND APPROVALS

VERSION HISTORY

Version # Date Description

1.0 09/12/2020 Initial Draft

This document has been approved as the official Business Requirements Document for FLYIN, and
accurately reflects the current understanding of business requirements. Following approval of this
document, requirement changes will be governed by the project’s change management process,
including impact analysis, appropriate reviews and approvals.
Business Requirements Document (BRD)
PROJECT DETAILS

Project Name FLYIN

Project Type Web Portal for Booking of Charter Flights
Project Start Date
Project End Date
Project Timeline 6 Weeks
Front End Technology HTML,BOOTSTRAP, Jquery
Backend Technology Laravel, SQL
Project Resources UI Developer, Lavarel Developer, Tester

OVERVIEW

This document defines the high level requirements FLYIN. It will be used as the basis for the following
activities:

 Creating solution designs

 Developing test plans, test scripts, and test cases
 Determining project completion
 Assessing project success

DOCUMENT RESOURCES

Name Business Unit Role

FlyIn Buddy Stakeholder Technology Inputs/Mockups

GLOSSARY OF TERMS

Term/Acronym Definition
MVC Model-View-Controller (MVC) framework is an architectural pattern
that separates an application into three main logical components
Model, View, and Controller
API Acronym for Application Programming Interface, which is a software
intermediary that allows two applications to talk to each other
SSL Stands for secure sockets layer. Protocol for web browsers and
servers that allows for the authentication, encryption and decryption of
data sent over the Internet.
SQL Injection SQL injection is one of the most common web hacking techniques.
PROJECT OVERVIEW

4.1 Project Overview and Background

Web based portal built to address niche market wherein we cater to the requirement(s) of HNI for
their travel needs through Charter/Private flights, initially addressing the needs of domestic audience
in current phase of the project.

4.2 Project Dependencies

Third Party Payment Gateway with PHP API support web services enabled, domain & server side
installation of SSL certificate

4.3 Stakeholders
The following comprises the internal and external stakeholders whose requirements are represented
by this document:

Stakeholders
1. FlyIn Buddy

2.

3.

KEY ASSUMPTIONS AND CONSTRAINTS

5.1 Key Assumptions and Constraints

# Assumptions
1 Assuming the portal to have additional functionalities in later phases and API integrations
required
2 Payment Gateway, Hosting , Domain/IP to be provided
3 Search Algorithm to be implemented in later phases

# Constraints
BUSINESS REQUIREMENTS

The following sections document the various business requirements of this project.
ID – Prefix ??
Requirement

ID – Number

Comments
Reference
Use Case

Required
Type

Function – Feature - Requirement

Non Functional User Requirements
F 0001 Design & Develop web pages
optimized for all devices & browsers
F 0002 Optimize Pages for loading time
Functional & Non Functional User Requirements- USER CASE(S)
F 0001 Creation of informative pages (Home,
About Us, Terms & Conditions,
Contact Us
F 0002 Enable User to Login/Sign Up
F 0003 Enable User to submit query with
following parameters Destination
From, To, Departure & Return Date,
No Of Passengers, Travel Time Slots,
Preference of Sharing the flight
F 0004 Enable user to submit following
details for registration i.e Name,
Gender, Date of Birth, Passport
number, Nationality, Unique ID Type,
Unique ID number, Address, Locality
& Email ID
F 0005 Enable user to be redirected on the
Payment gateway
F 0007 Enable user to receive confirmation
via mail & screen with generation of
Order ID
F 0007 Enable user to view following
information on the dashboard ,
Booking Status, Booking History
F 0008 Enable user to raise cancellation
request
Functional & Non Functional User Requirements- VENDOR CASE(S)
F 0001 Enable Vendor to Sign In/Register
 F 0002 Enable User to Manage profile with
following details: Business Details,
Aircraft Details, Availability Details,
Payment Information, Free Legs,
Crew Information
F 0003 Enable vendor to view booking details
with following parameters: Flight Type
booked, Scheduled date and time,
traveler details
F 0004 Enable vendor(s) to view payment log
along with status
Functional & Non Functional User Requirements- Admin/Moderator
F 0001 Enable Admin to login
F 0002 Enable Admin to create/disable users
F 0003 Enable Admin to create user roles;
Admin & Moderator
F 0004 Enable Admin to view all the
submitted queries from users
F 0005 Enable Admin to accept/reject queries
F 0007 Enable Admin to view booking details
and payment status
F 0007 Enable Admin to approve/disapprove
vendor registration
F 0008 Enable Admin to allocate user queries
to vendors
User Access/Security Requirements
F 0001 Encryptions to be enabled for all input
fields
F 0002 Enabling Client & Server side
encryptions of transmitting data
F 0003 Enabling validations for protecting
SQL injection
F 0004 Installing & Enabling SSL certificate

Support and Maintenance Requirements

F 0001 Six month support on Security
vulnerability
F 0002 One month support for server side
issues
F 0003 One month support for bug fixtures in
existing functionality
F 0004 One month handover support for
admin functionalities
TIMELINE(S)

1) DESIGN PHASE: 2 WEEKS

2) DEVELOPMENT PHASE: 3-4 WEEKS
3) TESTING & DEPLOYMENT: 1 WEEK
4) GO LIVE : 1 DAY