You operate a tour company that operates tours of local historical and natural attractions. You have several dozen different tour packages, each with a name (such as "Exploring Native Ruins" or "Bird-Watching Hike"), a scheduled duration in minutes, a per-guest price, and a maximum number of guests. You also have a staff of dozens of guides, for each of which you want to store a first name, middle initial, last name, and date hired. For each guest who has ever taken or has booked a reservation to take one of your tours, you want to store a first name, middle initial, last name, gender, date of birth, and mobile phone number. You group guests into households, for each of which you want to store address information (street address, city, state, and zip code), and a primary credit card number. Assume that you have access to a national zip-code table you wish to include in your database design, and that each guest can be a member of only one household. A tour consists of one of your guides taking a group of guests on one of the tour packages. For each tour, you want to your system to remember what tour package it was, which guide conducted it and which guests participated. You also want to store a scheduled start date and time, and an actual completion time (blank for tours that are in the future). Over time, guests can participate in more than one tour. Draw an entity-relationship diagram and write a database design outline for a database appropriate for this information.