Scenario: Software System for Peter's Rental Peter runs a rental car agency operating in the Puget Sound Region. He knows renters expect to pay tolls, but he's afraid that his company will be stuck paying the bills due to slow processing, paperwork, and hassle. The GoodToGo.com information claims billing will be easy, but Peter is skeptical. Peter enrolls his rental car business with GoodToGo.com G_ using his favorite browser. After creating a corporate account, he is taken to the information page. Peter is surprised to see that the GoodToGo.com interface works with his billing software. He launches his software, enters the connection information provided by GoodToGo.com, and then authenticates using his new corporate account. His billing software asks how frequently to update, and Peter enters 15 minutes-the time recommended by GoodToGo.com. Now all Peter has to do is submit his rental car fleet data. Peter goes to his fleet management system and exports the fields listed on the GoodToGo.com information page. He then imports the resulting CSV file directly into GoodToGo.com using the link provided on the information page. GoodToGo.com validates his fleet information and confirms the connection with Peter's billing software. The page says, "You're good to go!" Because it's more than 15 minutes from the nearest toll to his rental car agency, Peter's renters have all their tolls on their bill by the time they return their car. The bill indicates the time and code for each toll, which renters can use to dispute charges on GoodToGo.com. Peter can't believe how easy and hassle-free it is for him, his business, and his renters. He considers opening more Puget Sound locations. Note (from Wikipedia): Good to Go, stylized as Good To Go!, is the electronic toll collection system used by the Washington State Department of Transportation on all current toll projects in the U.S. state of Washington. Good to Go customers prepay a balance into an account and the tolls are then electronically deducted as the customer passes through an electronic toll collection location. Note: the scenario in this assignment was created by Prof. Socha for requirement building exercise. The description for Good To Go system here may not accurately reflect what the system does in reality. Task: Based on the information above, produce at least 10 (ten) functional requirements. (Note: We will cover non-functional requirements in a later sprint so be sure to focus on functional requirements.) These functional requirements are to describe how the system is supposed to behave or function to serve the user's needs. Note: this task is for the SW system of Peter's Rental and its stakeholders in the context of Good To Go! use. The functional requirements are NOT for Good To Go! system. Functional Requirement Format (refer to lecture slide (User Requirements/System Requirements, and Sommerville p.92): - Example: "The system shall provide