Next you will look at the detailed database table design for the airline ticket booking system. The application will not have the airline entity unfortunately, you have to live with this limitation until the specification is updated. For this reason, you will denormalize store redundant information of the airline entity in the flight entity. For this MVC application, the columns of the airline and flight entities after normalization will not be the same, so you cannot use this level of normalization. Hence, if you need to define a relationship between two entities, EJB 2.0 mandates that the relationship columns between the two entities must be the same in terms of name and datatypes. Normalized relationships in EJB 2.0 are not yet cleanly handled. Logical Entity-Relationship diagram for the airline ticket booking system. Because passengers purchase tickets for a flight, relationships are also defined between the passenger and ticket_info entitites and the ticket_info and flight entities. Flights can have different departure dates hence, the flight entity can be further refined into a flight entity and flight_details entity. These entities will need to be normalized to establish proper relationships. After studying the requirements, you can identify the different entities involved in the application, such as the airline, passenger, flight, and ticket_info. E-R Diagramįigure 2.5 shows the logical E-R diagram for the airline ticket booking system. Hence, the design discussion for the airline ticket booking system will include the Entity-Relationship (E-R) diagram and the class diagram. These two approaches are required because the application needs to persist data. You will be approaching the design of the airline ticket booking system in two ways: the database design and the class design. Also, even though the credit card details of the user are captured, these will not be used to generate any billing information. There will be no arrival date or arrival time displayed on the ticket. A user can book only a single one-way ticket to the required destination. The airline ticket booking system will have some major limitations because you wish to keep the application simple. The final step for the user is to confirm the order the application will then allocate a seat on that flight to the user. Only registered users will be allowed to book a ticket hence, while booking the ticket, the user has the option either to provide authentication details or, if not registered, to register with the application.Īfter either a valid authentication or a valid registration, the user will be prompted with a confirmation screen that displays the booking details and asks for a confirmation from the user.
After finding and selecting the flight required, a user can book a ticket. Users of the airline ticket booking system will have the ability to search for flights available for a certain destination on a certain date. You'll begin by briefly outlining the features that will be provided by your airline ticket booking system. Clearly, the consumer is the winner!Īs a part of your learning experience using WebLogic Server, you will build a simple airline ticket booking system, which will model a real-world, Web-enabled airline ticket booking system. Now you have many Web sites from both third-party vendors and airlines offering anything from cars to cruises to vacation packages, with deal comparisons and what have you. Remember the days when to buy tickets for a vacation, you had to call up ticket agents, find the airlines, search for deals, and so on? Well, since the Internet took off, things haven't been the same. The Internet- and Web-enabled applications have revolutionized the way businesses are carried out.