FixAuto" is a chain of vehicle repair shops in Sydney. Because of the prevailing COVID 19pandemic and increasing competition, the owners want to develop software in order to automate the business for improved services to their customers.

As a system analyst, you are required to analyse and design a Vehicle Repair Management System (VRMS) that should be able to perform tasks such as to track the repair jobs for the vehicles they repair, the items that are used for each repair job, the labour costs for each repair job, the mechanic performing each repair job, and the total cost of each repair job.

The system should be able to accept a new repair job, allocate the job to the available mechanic for repair and send the relevant information to the customer along with the details of calculated cost as well as the approximate vehicle pick up date and time. The staff should be able to provide any discounts based on any special conditions and process the payments made by the customer. The system should also allow authorised access to the staff and management to generate and view customised reports for the proposed system.

Overall, the system is required to have the following features for a variety of users.

o Customer Management operations (Creating, deleting, updating, searching customer)

o Repair Management operations (Checking for available mechanic, tracking details of items required for repair job, information of vehicles repaired and associated cost)

o Payment processing functions (Processing customer payments, Issuing online receipts)

o Login Management functions (Creating or removing system users)

o Report Generation functionalities (Generating reports of repairs, mechanics, customers etc.

You may also add other possible functions that you deem necessary to function in this business case.

You as a system analyst, are hired by 'FixAuto' authorities, to analyse and design the proposed system that should be able to perform tasks according to the details provided in the above case study. This will also require you to make necessary assumptions and document all your assumptions in your report. Make sure to provide the appropriate references for the information that is accessed from the external resources.

The report must contain at least the following sections

7. Domain Model Class Diagram: Provide the domain model class diagram for the proposed system. (2marks)

8. Use Case Diagram: Provide the name and complete description of a use case for the proposed system and draw a use case diagram.

User Interface: Provide a final user interface design using dialog and screen prototypes for any of the use case listed above. (2 marks)

9. Conclusion: