SRS - EmamulHassan/Travel_Management_-System-TMS GitHub Wiki
Emamul Hassan- 1731250042
Md Abir Hossain- 1731597042
Md. Rownak Islam Dip- 1731336042
- 1 Introduction
- 1.1 Purpose
- 1.2 Intended Audience
- 1.3 Intended Use
- 1.4 Product Scope
- 1.5 Risk Definition
- 2 Overall Description
- 2.1 User Classes and Characteristics
- 2.2 User Needs
- 2.3 Operating Environment
- 2.4 Constraints
- 2.5 Assumptions
- 3 Requirements
- 3.1 Functional Requirements
- 3.2 Non Functional Requirements
- Appendices
- A Glossary
- 03.07.2021- Emamul Hassan
- 04.07.2021- Md Abir Hossain
- 05.07.2021- Md. Rownak Islam Dip
The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the project "Travel Management System" (TMS). This SRS will allow the team to understand what to expect from this system and how to approach and create this system step by step. The clear understanding of the system and it’s functionality will allow the team to successfully develop the project. From this SRS, the Travel Management System can be designed, constructed, and finally tested.
The purpose of this document is to create a list of detailed requirements for Travel Management System (TMS). This SRS will be used by the development team and users to fully understand and test the features of the system. The Travel Management System Website will allow a user to search and find a place they like to visit from home. A user can easily search a travel plan and travel their desired location without any hassle.
- Project Development Team as Admins.
- Users as Testers.
- Project Development Team/ Admins: Developers can use this SRS to easily understand what’s the project about, which part they should focus more, which part to improve, find if there is any scope to add new features or function for any upgrade.
- Online Users/ Testers: Testers can use this SRS to test the software as per requirements. This will make the testing more organised as from SRS testers can easily get the idea where to look and what error or bug they should be looking for.
The project is basically a Travel Booking Website for people to book a flight from home. This Project will help a user to book a flight and choose a travel class which will ease up the process.
Features of this website(For Users):
- View Travel Options.
- Make Reservations.
- Track Orders.
- Give Feedbacks.
- View Feedbacks.
Features of this website(For Admins):
- Login Panel.
- Register Panel.
- Manage Order Section.
- Create Branch Section.
- Manage Branch Section.
- Manage Feedback Section.
- View Customer Feedbacks.
Objective of the website is to:
- Help people book a travel easily.
- Easily manage their booking orders.
- Too many server request is not controllable for the server.
- Too much user at a same time can cause server traffic.
This section will provide overview of the system, its perspective and main functions. TMS- Travel Management System is a website which customers can check to book a travel destination and confirm his/her booking.
There are two user levels in this TMS website.
- Customers: Customer is the main stakeholder of the software intensive system. Customer would be able to check available Travel Locations. Customer can select and sort Travels Reservation the way they like. Enter personal and payment details while confirm the booking. Customer input is required for making successful reservation.
- Admins: Admin is the administrative stakeholder of the software intensive system. TMS admins would able to update the information about listed Travels, see User Orders and update the booking information.
Users will use this website for book a place to travel. This works like any other travel agency except a user can order from home and give required information online to book. After a successful order a user can track his/her orders through the websites ’Order Tracker’ to check if the order is confirmed or not. Then they can visit their desired location around the world.
Operating environment for the Travel Management System is listed below:
- Operating System: Any Operating System that supports browsing.
- Database: MySQL.
- Front-end: HTML, CSS.
- Programming Language: PHP, Javascript.
- Framework: Bootstrap, Laravel
- We have to develop the website in mentioned Languages in operating environment
- The developed system must work in the client’s operating environment, which is Windows.
- We have to finish the project within 2 months.
- Users can read and write English.
- Users have devices that support internet service.
- Users are familiar with internet browsing and can interact with website.
- Users have decent internet connection.
- Users have decent knowledge of how websites work.
This section illustrates the functional requirements for TMS web interface which is having multiple different web pages that enables customer to select and reserve Travel Location online.
Functional requirements define the fundamental actions that system must perform. Two categories in Functional Requirements.
- Reservation/Booking
- Management
Reservation/Booking:
- As a user,
I want to Select a travel destination. so that I can travel to that destination.
Confirmation,
- User has to select his desired destination.
- The system will Show him his desired location and give him the option to reserve that location.
- As a user,
I want to order a travel package. so that I can get to travel my desired travel destination.
Confirmation,
- User has to input his name, phone number, email(optional) in the travel form.
- User has to choose an available Travel destination and a package from our collection.
- User has to put a date and suitable flight time.
- As a user,
I want to check my order. so that, I can know details of my travel.
Confirmation,
- User has to find 'track your order' option in the website.
- User has to put his unique order id in the track order field.
- User can then check the details of his travel destionation.
- As a user,
I want to select a travel destination. so that I can travel to that destination.
Confirmation,
- User has to select for his desired destination.
- The system will show details of his desired location and give him the option to reserve that location..
- As a user,
I want to write feedbacks or reviews. so that, I can help people make a decision on which travel destination to choose or which package to choose for themselves.
Confirmation,
- User has to go to Write Feedback page.
- In that page, user must put their travel information i.e. Order ID, Name, Email, etc. and write feedback.
- The system will save that feedback in database and immediately show that in Check Feedback page.
- As a user,
I want to check feedbacks or reviews. so that, I can make a decision on which travel destination to choose or which package to choose.
Confirmation,
- User can view other users feedback from Check Feedbacks page.
Management:
- As an admin,
I want to login to the Admin Panel.
Confirmation,
- Admin must go to Admin Panel URL.
- They will enter their unique and correct admin username and password.
- If the login credentials matches it will land admin to the Admin Panel page.
- As an admin,
I want to manage the order details of a user upon request from that user.
Confirmation,
- Admin must go to Manage Order page in Admin Panel.
- From there he/she can change order details and save them for user.
- After a successful Save Changes user can see the changes in track order section.
- As an admin,
I want to confirm a user order.
Confirmation,
- Admin must go to Confirm Order page in Admin Panel.
- If there is no problem with the order, an admin can confirm the order with a button.
- After an order gets confirmed, a user cannot edit or request to edit changes to that order.
- As an admin,
I want to check/manage feedbacks.
Confirmation,
- Admin must go to manage feedback page in Admin Panel.
- Admin can view feedbacks from the user.
- Admin can remove any feedbacks if it violates the TOS.
- As an admin,
I want to add branches for the company.
Confirmation,
- Admin must go to manage branch page in Admin Panel.
- Admin can view current branches information in manage branch.
- Admin can add create any branch for the company in needed in future.
Chapter 3: Requirements 8
This section defines the needs in terms of performance requirements, security requirements, logical database requirements, safety requirements, design constraints, availability, maintainability, and error handling.
Performance Requirements:
- The system must have enough resources to load the website.
- The system must not accumulate high numbers of users without any fault.
Security Requirements:
- System will use secure MySQL database and valuable user information will be encrypted in the Database to preventing data leaks.
Error Handling:
- OS must handle expected or non-expected errors in ways that prevent loss in information and long down time period.
Safety Requirements:
- System should be secured and use must not cause any harm to users.
SRS: SRS stands for Software Requirements Specification. A software requirements specification (SRS) is a document that describes what the software will do and how it will be expected to perform. It also describes the functionality the product needs to fulfill all stakeholders (business, users) needs.
TMS: TMS stands for Travel Management System. A travel management system helps travel managers book, track, and analyze travels. Typically, a travel management system refers to a platform that offers travel inventory, travel policies, and reporting, but this can also refer to the overall process of managing corporate travel.