Customers in the Guelph-Kitchener region can get mobile auto repair services from Osas Mechanics, a business situated in Guelph, Ontario. They run a convoy of cars that go to the customer's house. The company currently employs about 250 people, and as they widen their service area, they anticipate continued growth. This entails expanding their service area to encompass Waterloo and Cambridge and providing more auto-related services like vehicle washes.

Currently, a central office handles all appointments for auto repairs. The business wants customers to be able to schedule their own appointments on an application in the future. The office staff in charge of scheduling appointments may get overburdened by the volume of calls, which worries the stakeholders, as the company expands. Customers have two options once the application is lauched: they can book on the application or keep contacting the office. Additionally, the business prefers that customers pay for their services through the app rather than by paying mechanics personally.

A solution where clients have more control over their appointment scheduling and the mechanics are not in charge of processing payments is what the firm envisions for the project. Customers that have registered on the app will do both duties.

We will have to develop an application with a customer database to hold the client's personal and financial information to realise this objective. The database must also contain details about the customer's vehicle. Customers should be able to access the app, check the timings of the available appointments for auto repair in their area, and then schedule an appointment. They should then receive an invoice from the app to start the payment procedure after the appointment is over.

Part 1: Describe your scope In a paragraph. describe the solution you are building for your client the scope ofyour project. Provide enough detail that the requirements you document in Parts 2 and 3 are fully contextualized. Part 2: Functional Requirements You are expected to write a total of 25 functional requirements. 0 You may organize them into as many or as fewfeatures as you choose, I Under the heading for each feature. include a brief description of the purpose of that feature within the solution. 0 Each functional requirement should be given a unique ID. 0 Support your functional requirements with basic wireframes. REMEMBER: Wireframes do not need to be exhaustive. They simply need to clarify and support your functional requirements. Part 3: Nonfunctional Requirements You are expected to write a total of 5 nonfunctional requirements. 0 You may organize them into as many or as few quality attributes as you choose. 0 Each functional requirement should be given a unique ID