A friend of yours owns two houses at Football City, the site of the next Super Bowl. Your friend wants to rent those two houses for the Friday, Saturday, and Sunday of the Super Bowl weekend. House #1 has 3BR (3 Bedrooms), 3BA (3 Baths), and house #2 has 1 BR, 1BA. For this project, concurrency is not an issue; you should assume that two customers will never access your system at exactly the same time. You should also assume that the management-side software and the customer-side software will never run at the same time. We can assume that we run the management-side software first, then the customer-side software. This friend has asked you to build a file-based reservation system enabling the following: A. Management-side software: Your friend controls the rental price and may change it every day. He/she sends you a change file every day; this file may be empty, in which case there are no pricing changes. If the file is not empty, pricing has changed (for one or more houses, or for one or more days). You are in charge of this project, and therefore, you are in charge of specifying the file format; however, this must be simple text file because your friend is not a computer person. You do not have to simulate the act of sending the file by your friend; you should assume that the file is a text file in your directory and that you only need to read the data. Your management-side software needs to read this file and update a different file, with which you control the reservation system. You can create your own design for the structure of that file. Of course, prices for existing reservations cannot be changed. Finally, your management-side software should write to a file the status of the reservations; that is, which house is rented to whom, when, and for what price.