Question 1 You are working for a certain county and you want to convert the records of the county's register of real property sales to an electronic database The county has several municipalities (towns, villages, cities, etc.), and for each one you want to storea name, a type (city, township, borough, etc.) and date of incorporation Each municipality has numerous buildings, each of which is identified by a block number and lot number (each building within a given municipality has a unique combination of block number and lot number). For each building, you want to store a street address, zip code, and the year in which it wa:s constructed. Assume that you have access to a table that includes the zip codes and corresponding cities in your county (the county is in only one State, so that information is not required in this table); include this table in your database. Note that zip codes may not correspond perfectly to municipalities -- some municipalities may have multiple zip codes, and the boundaries of zip codes and municipalities may not be perfectly aligned, in other words, in some cases there is no correspondence whatsoever between zip codes and municipalities. Each building may have been sold many times; for each sale, you want to record its price, date, and the name of the person or company the building was sold to (you record owners' names using a single, long "name" field because some owners are corporations) Finally, a small percentage of buildings in the county are in the national register of historic places; for these buildings, you want to record a 255-character description of the unique features of the building, the date it was inducted into the historic register, and the ID number the register assigned to it. Create a database design outline and entity-relationship diagram for a database appropriate for this information. Set up your database so that the records for non-historic buildings do not have to store empty fields for historic-register-related data