17-05-2014, 10:37 AM
airline reservation system
airline reservation.pptx (Size: 466.27 KB / Downloads: 9)
INTRODUCTION
Purpose:
The web based “airline reservation system” project is an attempt to stimulate the basic concepts of airline reservation system. The system enables the customer to do the things such as search for airline flights for two travel cities on a specified date, choose a flight based on the details, reservation of flight and cancellation of reservation. The system allows the airline passenger to search for flights that are available between the two travel cities, namely the “Departure city” and “Arrival city” for a particular departure and arrival dates. The system displays all the flight’s details such as flight no, name, price and duration of journey etc.
After search the system display list of available flights and allows customer to choose a particular flight. Then the system checks for the availability of seats on the flight. If the seats are available then the system allows the passenger to book a seat. Otherwise it asks the user to choose another flight. To book a flight the system asks the customer to enter his details such as name, address, city, state, credit card number and contact number. Then it checks the validity of card and book the flight and update the airline database and user database. The system also allows the customer to cancel his/her reservation, if any problem occurs.
The main purpose of this software is to reduce the manual errors involved in the airline reservation process and make it convenient for the customers to book the flights as when they require such that they can utilize this software to make reservations, modify reservations or cancel a particular reservation.
DATA FLOW DIAGRAM
The DFD was first developed by larry Constantine as a way of expressing system requirement in a graphical form. A DFD is also known as “bubble chart” has the purpose clarifying system requirements and identifying major transformation that will become programs in system design so it is the starting point of design phase that functionally down to the lowest level of bubbles joined by lines. The bubbles represent the data flow in the system.
The data flow diagram (DFD) shows the flow of data the process and the areas where they are stored. It is a commonly used structured tool for displaying the logical aspects of the system under the study. Decision tables are used as a supplement when complex decision logic cannot be represented clearly in a DFD.
The DFD describes the logical data flow rather than how the data is processed. So it does not depend on hardware, software, data structure or file organization. The key concept of DFD is to specify what major transformation must occur for input to be correctly transformed onto output.
ENTITY-RELATIONSHIP DIAGRAM
An Entity-Relationship Diagram (ERD) is crucial to creating a good database design. It is used as a high level logical data model, that is useful in developing a conceptual design for database.
An entity is a real-world item or concept that exists on its own. Entities are equivalent to database tables in a relational database, with each row of the table representing an instance of that entity.
An attribute of an entity is a particular property that describes the entity. A relationship is the association that describes the interaction between entities. Cardinality, in the context of ERD, is the number of instances of one entity that can, or must, be associated with each instance of another entity. In general, there may be one-to-one, one-to-many, or many-to-many relationships.
For example, let us consider two real-world entities, an Employee and his Department. An Employee has attributes such as an Employee Number, Name, Department Number, etc. Similarly, Department Number and Name can be defined as attributes of a Department. A Department can interact with many employees, but an employee can belong to only one department, hence there can be a one-to-many relationship, defined between Department and Employee.
In the actual database, the Employee table will have department number as a foreign key, referencing from Department table, to enforce the relationship.