You are modeling a small part of an online flight reservation system, according to the following description. A flight is a sing
le non-stop hop between a pair of cities. A booking can include several flights and travelers (think of a family vacation hitting multiple cities), with the requirement that all the travelers are on all the flights in a booking. Furthermore, every booking has a single owner who is one of the travelers on that booking (think one family member booking the tickets for the entire family), and the owner can manage functionality on the system that other travelers cannot. A separate ticket is issued and priced individually for each traveler on a booking, and the ticket applies to all flights within that booking. Draw the most appropriate UML diagram for your model. Identify entities (classes/abstract classes/interfaces) clearly, and separate them according to their functionality--the separation should be faithful to the description above. Set up relationships between entities as precisely as possible. Inside each class in the diagram, only list the class name and minimal number of attributes required to characterize objects of that class (no operations needed). For the attributes, you are not required to show access level. For any ONE association, code the classes involved, detailing the fields ONLY.
1 answer:
You might be interested in
