[10 Points] Description In this assignment you will translate a system description into a FSM state diagram and then transform it into a FSM controller circuit in Logisim by utilizing a truth table and Boolean equations. It is heavily recommended to watch the supplemental video and work on the optional assignment before you attempt this assignment. The video shows step-by-step how this process works using a complex example. Watching and understanding this video, will help you greatly with this assignment. System Description \& State Diagram First task: Transform the following system description into a FSM state diagram (you can use any tool to create this diagram, which allows you to draw circles and connect arrows between them; hand-drawn diagrams will not be accepted). Make sare you are using the correct notation for the state diagram. Use the given labels for everything. don't pick your own labels. Everything is defined and you don't have to choose your own labels at any point during this assignment. Use minterms for every transition event in the state diagram (each event must be a specific configuration of all inputs) to avoid incomplete and non-exclusive transitions. If the state does not change for certain events, make sure to model this behavior with an appropriate transition. The system represents an underground parking access elevator in an office building. There are four levels, which are accessible through the elevator: Entrance floor, employee parking, underground parking 2, underground parking 3. Customers and employees will control the elevator with two buttons: Up and Down. The employee parking level is only accessible by employees using a specific button combination. If this specific button combination is pressed, the elevator will go from any level directly to the employee parking level. Below is the detailed system description, which will be used to create the state diagram of this system. - The system has four states, which represent the current level of the elevator (in order from highest level to lowest level): Entranoe Floor (ground level), Employee Parking (first underground level), Underground Parking 2 (one level below employee parking), Underground Parking 3 (two levels below employee parking) - The system has two 1-bit inputs: Up (label: u), Down (label: d) - The system has one 2-bit output: Level (label: L or L1 and LO for each individual bit, where index 1 indicates the MSB and index the LSB) - If the Up button is pressed, the elevator goes to the level above. If the elevator is already in the highest level, pressing the Up button will have no effect and will stay in the current level. In case the level above is the employee parking, the elevator will skip this level and go directly to the level above it. - If the Down button is pressed, the elevator goes to the level below. If the elevator is already in the lowest level, pressing the Down button will have no effect and will stay at the current level. In case the level below is the employee parking, the elevator will skip this level and go directly to the level below it. - The employee parking button combination is the following: Pressing both buttons, Up and Down, at the same time. This is the only input that will allow the elevator to move from any level direetly to the employee parking level. If the elevator is already in the employee parking, this combination will have no effect and will stay at that level. - While the elevator is in the employee parking level, pressing Dourn will move the elevator to the level below it. Pressing Up will move the elevator to the level above it. - If no button is pressed, the elevator will do nothing and stay in the current level. - The 2-bit output L will indicate the level in binary for Entrance Floor (00), Employee Parking (01), Underground Parking 2 (10) and Underground Parking 3 (11). - The developer of this elevator - unfortunately - chose an encoding of the states that is different from the system output: The Entrance Floor is encoded with 11, Employee Parking with 10, Underground Parking 2 with 01 and Underground Parking 3 with 00 . Converting to Circuit Perform the following tasks after you transformed the previous system description into a state diagram: 1. Create the truth table to describe the complete behavior of the state diagram (all possible input combinations for all existing states must be covered). Use the given labels. Order columns for multi-bit inputs/outputs from MSB to LSB. Indicate which are inputs and which are outputs. Do not simplify the truth table with don't care-symbols. For the current state use label c (add index if multi-bit: c0 for LSB, cf, etc.) and for the next state use label n (add index if multi-bit: n for LSB, n1, ete.). 2. Derive the Boolean equations from the truth table for all outputs (next state and all system outputs). Use the same labels as in the truth table. Don't simplify the Boolean equations. 3. Create a working FSM controller circuit in Logisim. You can tse the built-in register component of Logisim for your state register. Rename the "main" circuit to "ParkingElevator". Notes: - Make sure to test it properly and thoroughly to confirm it is working as described in the System Description above. - To test the FSM, it is recommended to manually toggle the clock. This way you are able to see earh state change clearly. - In this system, not all system outputs are equal to an existing signal in the system. There are two possible approaches to generate system outputs: Create a combinational circuit based on the derived Boolean equations for the respective system outputs, or use a multiplexer to map the current state to the correct system outputs. - For the next state bits, you must include all system inputs including the current state. For the system outputs, since they only depend on the current state, you can derive these equations by just using the current state bits and can omit the system inputs. Deliverables Important: - Hand-drawn state diagrams and hand-written truth tables will not be accepted. Use proper software to create them. - Format your table properly (e.g. using the same content alignment for all cells, use of cell borders, make sure the table is not split and on a single page, etc.). Points will be deducted if the table is not properly formatted. - Make sure to submit both files in one submission. Only the files of the last submission will be graded. If one is missing, you will receive 0 points for the missing part. The deliverables must be submitted on Canvas before the due date as a single submission: 1. Logisim , circ file of the FSM controller circuit. Submit the file with the following naming convention: lastname_a6.cinc 2. Design document as , pdf that includes the state diagram, truth table and Boolean equations of the FSM. Submit a single file with the following naming convention: lastname_a6design.pdf