Question 1 (15 Marks): Create a UML Class Diagram using Microsoft Visio 2007or any UML software that represents an Online shopping system. In this diagram, you should represent the concept of a person, consisting of a social security number, a first name, and last name. There are two types of people, customers and ticket agents. A customer is identified by his or her credit card number, and also includes information about the type of credit card and its expiration date, as well as a frequent flyer number and frequent flyer miles accumulated. A ticket agent is identified by a ticket agent number. The user can get and set the name and the last name of the person. He can also get the credit card number of the customer. You also need to represent the concept of a flight, which consists of a unique flight number, a source city, a destination city, a date, departure time, and arrival time. A ticket is assigned by a ticket agent to a customer for a particular itinerary (route). Tickets have information regarding the price. In effect, the ticket binds the agent, the itinerary and the customer together in a unique relationship. Each ticket is associated with exactly one customer, one agent and one itinerary. But any customer, agent or itinerary could have any number of tickets. The user can set departure and arrival time. He can also calculate the price of the ticket An itinerary is associated with at least one flight, and possibly several. Each flight may be associated with any number of itineraries, including none. The association between itineraries and flights includes information about the seat assignment. Finally, flights are associated with airlines in a tight binding; flights cannot exist without the airlines to which they are associated. Each flight is associated with only one airline, and airlines should have at least one flight but maybe more. Each airline is identified by a unique name. You are required to show the following in your diagram: Classes and their attributes including primary keys. Operations of each classes, if any Associations between classes and multiplicity. Generalization, aggregation and composition relationships, if any. Note: Associations' names are not required in this