A Real Estate, Inc. (AREI), sells houses. People who want to sell their houses sign a contract with AREI and provide information on their house and their contact information. The house information includes the location, size, how many bedrooms, how many bathrooms, desired price, a short description of their house. The seller information includes the name, phone, email, and mailing address. Such information is kept in a database by AREI, and a subset of the information (house information) is sent to the citywide multiple listing service used by all real estate agents. AREI works with two types of potential buyers. When working with a new potential buyer, the buyer completes a buyer information form including his/her name, phone, email, mailing address. Some buyers have an interest in one specific house. In this case, AREI prints information from its database, which the real estate agent uses to help show the house to the buyer (a process beyond the scope of the system to be modeled). Other buyers seek AREIs advice in finding a house that meets their needs. In this case, the buyer provides a short description of the desired houses including the location, size, how many bedrooms, how many bathrooms, and desired price. The AREI real estate agents use such information to search AREIs database and the multiple listing service for houses that meet their needs. The results of these searches are printed and used to help the real estate agent show houses to the buyer.

Create a UML use case diagram for this scenario.