plz solve this with code A workshop specializing in the sale/installation/repair of air conditioners wants to improve the management of its maintenance service. He asks you to create a mini-application in c language allowing him to follow up requests and acts of repair of air conditioners according to the operation described below. The workshop has a maintenance unit made up of 3 teams: Reception: reception and follow-up of repair requests Diagnosis: diagnose the equipment and establish a list of repair actions Repair (technical): repair the equipment according to a check list given by the team of diagnostic The "reception" team begins by registering each new repair request (details below). To do this, it enters the characteristics of the air conditioner to be repaired (brand, model, power, etc.) as well as information relating to the owner (surname/first name, tel) then delivers the equipment to the diagnosis team. The "diagnosis" team draws up a report of repair actions (interventions) required. This step corresponds to entering a checklist of repairs required (see below) Once the diagnosis has been established, the equipment is directed to the technical team which will provide the repair. The latter consults the diagnostic checklist and repairs the act by act, it will note (in the same check list) the result of each act of repair (successful, fails, not performed) A repair request includes the following information: A reference, data relating to the air conditioner: o An air conditioner is defined by: an owner (name, phone) a description of the air conditioner (a text to define the model, the power, etc). a textual description of the failure formulated by the owner, the status of the request (ED) to ensure follow-up. Four states are defined: 0: (default) saved. [This value is assigned automatically when of the registration of the request] 1: diagnosed, [ED automatically changes to 1 once the diagnostic team saves his check list of remedial actions (see details below)] 2: repaired, [value automatically assigned if all repairs were successful] 3: not repaired [value automatically assigned if at least one repair action failed] The check list (table) of acts of reparation where each act has two fields: o Code: The reference of the repair act (this number is defined by the team diagnostic) o ER: Its state of repair it is 0 (not realized) by default, it is modified to 1 (completed) by the technical team after the successful completion of the repair or another value >1 on failure NB: The check list table is initialized to zero when the check is saved. request by the reception team, the codes will be entered by the diagnostic team and the state ER will be updated by the repair team The technical team carries out the repair step by step by following the checklist and recording for each act, its state of repair ER (1 or another value greater than 1 corresponding to a failure code). Once all the actions on the checklist have been processed and validated by the team technical, The status of the repair request (ED) automatically changes to 2 "repaired" if all the repair states have been carried out (value 1) otherwise it takes the value 3 "Not repaired" Required work : You are asked to code the application, using the following data structures: DemRep (repair request), ListDem (the list of repair requests), FileDiag and FileRep (two queues containing the references of the requests of repair in waiting for diagnosis and waiting for repair), Knowing that: When a new repair request (DemRep) is recorded, it is stored at the end of an optimized simple linked list (ListeDem) containing all the requests managed by the service. At the time of registration of the request, the reference of the request is, in addition, threaded into a diagnostic Queue called (FileDiag) awaiting the diagnostic. After the diagnosis, each reference is scrolled from FileDiag to be inserted into the repair queue called (FileRep). It will be scrolled from the latter once the repair completed. 1. Define the File library (File.h and File.c) comprising the File structure as well as the primitives CreateFile(..), IsFileEmpty(..), First(..), Thread(..), Scroll(..) , Display(..) 2. Define the Repair library: (Reparation.h and Reparation.c) grouping the data structures: DemRep, ListeDem , FileDiag and FileRep Requests in a "requests.rep" file References of requests awaiting diagnosis in the file diag.rep The references of the requests awaiting repair in the file Rep.rep o When starting the application, load the data into the structures of data from associated files "