Airline Ticket agency

 Normalization of the Relation drawn using the ER Diagram Codes using MySQL workbench

  Identification of Actors An actor specifies a role played by the user or any other system that interacts with the subject. it may represent roles played by human users, external hardware, or other subjects. In this scenario, we got 3 actors they are,        1. Airline ticket agency.       2. Passenger.        3. System. Business Processes First when someone needs to travel that person looks for a ride. it may be any transportation method. if someone chooses flight they are our stakeholders. when they chose our agency they are our customers, when a customer (passenger) books a fight A separate booking reference number is given to each passenger. An airplane has several seats that seats have a unique number each number given to each passenger. An airline agency takes a booking fee from a passenger in return they give them a ride that's the whole business process of an airline ticket agency. Requirements for the new system Requirements are a statement that identifies the functional

                Airline Booking System Entities and Attributes Entities An entity is an object that exists. An entity can be a single thing, person, place, or object. data can be stored about such entities. 1. Ticket Agency Entity 2. Flight Entity 3. Airline ticket 4. Passenger Entity Attributes An attribute defines the information about the entity that needs to be stored. An entity will have zero or more attributes, and each of those attributes applies only to that entity. 1 . Ticket Agency: Agent, phone_number, email_addrest, Ticket_type, Booking_number 2. Flight :   total_seats,  Arrival_date & time, Departure date & time , Flight_ticket,  destination airport 3. Airline ticket: Ticket_id, description, seat number 4 . Passenger : Name , passport_number, email Relationships There are three types of relationships in this chosen scenario. They are one to one, one to many, many to many. 1. Ticket agency has tickets (one to many) 2. Ticket agency has flight (one to many) 3. Ticke

Introduction to case study... Greetings !!! Our case study scenario is  An airline ticket agency does the seat bo oking for passengers. The purpose of this case study is to improve our knowledge about how to develop a system to manage the day-to-day business of this agency. we are team 3, members of this project are Y.C Withanage(S92084699) and G.W.G.H.N jayakodi(S92074816).hope you guys enjoy.