Table of Contents 1. Introduction 1.1 Purpose 1.2 Document Conventions 1.3 Intended Audience and Reading Suggestions 1.4 Project Scope 1.5 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. System Features 4. External Interface Requirements 4.1 User Interfaces 4.2 Hardware Interfaces 4.3 Software Interfaces 4.4 Communications Interfaces 5. Other Nonfunctional Requirements 5.1 Performance Requirements 5.2 Safety Requirements 5.3 Security Requirements 5.4 Software Quality Attributes
The purpose of this document is to provide the software requirement specification report for the airline database.
1.2 DOCUMENT CONVENTIONS
Data base Distributed Data base Entity relationship DB DDB ER
1.3 INTENDED AUDIENCE AND READING SUGGESTIONS
This project is the college level project and is implementing under the guidance of college professors. This project is useful to everyone who travels in flights.
1.4 PROJECT SCOPE
The purpose of the online system is to create convenient and easy-to-use online system for passengers, trying to buy airline tickets. The system is based on a relational database with its flight management and reservation functions. We will have a database supporting dozens of major cities around the world as well as hundreds of flights by various airline companies. Above all, we hope to provide a comfortable user experience along with the best pricing available.
● www.laynetworks.com ● fundamental of database systems by ramez elmarsi and shamkant b.navathe.
2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
A distributed Airline database System stores the following information as shown below . ● THEFLIGHT DETAILS: It includes the originating flight terminal and destination terminal, along with stops in between, number of seats booked/available seats between two destination etc. ● CUSTOMER DESCRIPTION: It includes customer code, name, address and phone number. This information may be used for keeping the records of customer for any emergency or for any other kind of information. ● RESERVATION DESCRIPTION: It includes customer code number, flight number, date of booking, date of traveling .
2.2 PRODUCT FEATURES
The major features of airline data base system as shown in below data flow diagram
layout of airline database system
2.3 USER CLASS AND CHARECTERSTICS
Users of the system should be able to retrieve flight information between two given cities with the given dates/times of travel from the database. A route from city A to city B is a sequence of connecting flights from A to B such that: a) there are at most two connecting stops, excluding the starting city and destination city of the trip, b) the connecting time is between one to two hours. The system will support two types of user privileges, Customer and Employee. Customers will have access to customer functions, and the employees will have access to both customer and flight management functions. The customer should be able to do the following functions:
● Make a new reservation. o One-way o Round-Trip o Multi-city o Flexible Date/time o Confirmation. ● Cancel an existing reservation. ● View his itinerary. The Employee should have following management functionalities: ● CUSTOMER FUNCTIONS. o Get all customers who have seats reserved on a given flight. o Get all flights for a given airport. o View flight schedule. o Get all flights whose arrival and departure times are on time/delayed. o Calculate total sales for a given flight. ● ADMINISTRATIVE o Add/Delete a flight o Add a new airport o Update fare for flights. o Add a new flight leg instance. o Update departure/arrival times for flight leg instances. Each flight has a limited number of available seats. There...