List the terminal images and non-terminal images, (c) List the terminal images and non-terminal images, and count the creation rules both in the first syntax and in the sentence structure in your response to part (b). Demonstrate the beginning image in the two sentence structures. [2 marks] (d) Define a sort or types (in C, Java, or ML) appropriate for holding a theoretical For example, the prototype should show where the relevant button locations, how much information would be presented on each screen etc. Low- fidelity prototyping is mainly to allow designers to produce alternative designs expediently without having to go into depth or functionality. Think of low-fidelity prototyping as the 5D tool for: design, draft, decide, discard and do-over. Feedback and Survey: Perform an interim evaluation of your design by creating a method of feedback and asking 3-4 potential users (e.g. friends, family members, classmates, etc.) to complete the feedback for your low-fidelity paper prototype. Carry out the evaluation according to prescribed methods found in the textbook (Shneiderman & Plaisant, 2017) or from other scholarly sources. Use appropriate survey techniques. Analyse the data you have collected from the user evaluation and note down any recommendations as to how you could refine and improve on your initial design. High-Fidelity Prototype: Based on the user test feedback and recommendations develop a high-fidelity prototype. The high- fidelity prototype should be an online mock-up of your proposal and should demonstrate some navigation, although it does not need to work as a complete interface. A minimum of 4 screens should be produced in correspondence to your storyboard. The high-fidelity prototype must be computer based and any software is acceptable including PowerPoint, storyboarding, etc. Evaluation Plan: Create evaluation plan with recommendations on the tools and methods you intend to use to evaluate the usability of your interface. After all of the methods are verified, comment out the test code in the client application and add two RV instances to the program whose location and color are passed to the three-parameter constructor. Output these vehicles to the system console and the game board and then output them again after the user inputs a new color and a new (x, y) location for each vehicle. The formatting details for the attributes printed out are: All labels will be aligned to the right, on a field of exactly 230 characters wide. All values will be aligned to the left, on a field of exactly 303 characters wide the label is separated from the value by : (space-colon-space). the filling character is a dot (.) Review the sample_output.txt for hints. A TennisLog is a class that will manage a dynamic array of TennisMatches and keep a count of how many are being stored. This class will define the following member functions: Default constructor = A one argument constructor that receives a filename as a parameter (review the file tennis-data.csv to understand its format) from which we will populate the current object. This function will: read the file to count the number of matches in the file (note the heading line in the file is not describing an actual match so do not count that line) allocate dynamic memory for the array of matches based on the number found reread the file from the beginning to load the actual match data into the array addMatch() is a modifier that receives a TennisMatch object and returns nothing. addMatch will attempt to append the parameter to the dynamic array of matches held by the current object. Resize the array appropriately to accommodate the new object and avoid memory leaks. findMatches() is a query that receives a name of a player as a parameter and returns a TennisLog object. findMatches will return a TennisLog that contains all of the matches where either the winner or loser's name matches the parameter. operator[](size_t) a query that will return the TennisMatch in the dynamic array at the index provided. If the array isn't populated then return an empty TennisMatch instead. operator size_t() is a casting operator that will convert the current object to a size_t value. The return value for this will be the size of the dynamic array of TennisMatches held by the current object. To review the syntax for reading from a text file using an std::ifstream object see the chapter in your notes entitled Custom File Operators. Add any other private members that your design requires (without changing the specs above)! Sample Output - When the program is started with the command:ws tennis-data.cs the output should look like the one from the sample_output.txt file. Test Your CodeTo test the execution of your program, use the same data as shown in the output example above. Upload your source code to your matrix account. Compile and run your code using the latest version of the g++ compiler (available at /usr/local/gcc/10.32.0/bin/g++) and make sure that everything works properly. Then, run the following command from your account (replace profname.proflastname with your professor's Seneca userid): ~profname.proflastname/submit 3435_w2_p31 and follow the instructions. This part represents a milestone in completing the workshop and is not marked! -Part3 2 (1030%) For this part of the workshop, upgrade the TennisLog class to include the Rule-of-35 and its associated functions. Also, add a new class called Timer, that will be useful in measuring how much time an operation takes. This class should have the following public members: start(): a modifier that starts the timer (takes the current timestamp and stores it in an attribute). stop(): a modifier that stops the timer (takes the current timestamp) and returns how many nanoseconds passed since the timer has started as a long long value. Refer to the following reference documents on std::chrono to get started (there are examples in these pages that show exactly how to take a timestamp, calculate a duration between two timestamps, and print that duration to screen): When the program is started with the command: ws tennis-data.csv the output should look like the one from the sample_output.txt file.