Low Level Design of a Circular Array Queue In class, we worked through the Low Level Design for the Linked List implementation of the Queue Abstract Data Type (ADT). This design consisted of the pseudocode for the operations that we would need to implement for the concrete LinkedQueue class. You are to repeat this process for a Circular Array Queue. An overview of the Circular Array is shown below, as well as the High Level Design (class diagram). You are to write the pseudocode for the operations defines on CircularArrayQueue. Remember that you are not writing Java code! Pseudocode is written in English/Math, but can look like Java if it is clear. Note that in the design, the data elements(the class attributes) have already been specified for you Please note that pseudocode should describe HOW an operation is to be completed, not just what the operation is supposed to do. For example, for the operation size() don't say that it should return how many elements are in the Queue. We all know that! How will it calculate the size? Will you have a separate attribute or will you compute it from some of the others? For each operation, Including the constructor, describe what specifically will happen with each affected attribute. Turn in a Word document that lists the the pseudocode for each of the six CircleArrayQueue operations Notes: .Do not write code. Do not turn in a .java file. N-1 ront count Low Level Design of a Circular Array Queue In class, we worked through the Low Level Design for the Linked List implementation of the Queue Abstract Data Type (ADT). This design consisted of the pseudocode for the operations that we would need to implement for the concrete LinkedQueue class. You are to repeat this process for a Circular Array Queue. An overview of the Circular Array is shown below, as well as the High Level Design (class diagram). You are to write the pseudocode for the operations defines on CircularArrayQueue. Remember that you are not writing Java code! Pseudocode is written in English/Math, but can look like Java if it is clear. Note that in the design, the data elements(the class attributes) have already been specified for you Please note that pseudocode should describe HOW an operation is to be completed, not just what the operation is supposed to do. For example, for the operation size() don't say that it should return how many elements are in the Queue. We all know that! How will it calculate the size? Will you have a separate attribute or will you compute it from some of the others? For each operation, Including the constructor, describe what specifically will happen with each affected attribute. Turn in a Word document that lists the the pseudocode for each of the six CircleArrayQueue operations Notes: .Do not write code. Do not turn in a .java file. N-1 ront count