Create an EBNF specification for the following language as described below. Please note that the EBNF does not indicate WHAT the keywords do, simply the syntax of the language: (in this description, keywords are in bold.) The language has a very simple syntax in which you can assign values to variables, perform basic arithmetic operations on these variables, and print the values of variables. There is no string manipulation, but there is string output. All tokens must be separated by a space or whitespace. A variable is declared by using the keyword var and then the variable name. You may only declare one variable per line. Assignment statements are in the form of a variable name, and equal sign, and then an expression that evaluates to a numeric answer. For the sake of simplicity, assume only integers and floating-point numbers (in other words, you do not need to worry about scientific notation). Variables names must start with a letter and then may contain letters, numbers, or the character. Variable names must be no longer than 63 characters. To print something, use the. keyword followed by a variable, constant, or a list of variables or constants separated by commas or semicolons. A comma indicates that you want a space between the items in the output and a semicolon means no space between the two items. You may also include strings as constants by enclosing them in double quotes. The output will automatically go to the next line unless the line ends with a comma or semicolon. The input statement is the -> operator, followed by a space and then a single variable that will receive the input. Comments begin with // and proceed to the end of the line. They must be on a line by themselves. Math operators are +- */% (modulo) and ^ (exponent) Parentheses are allowed in math expressions and behave as you would expect. You may not define functions. A program must start with the keyword begin and must end with the keyword end. These keywords must appear on lines by themselves.

Tell me about a moment when you struggled to get your ideas across in an online class or assignment. Do you have any thoughts about how we might solve these issues?

Click to select the general guidelines to improve the quality of documentation text. Here, you have to arrange the options given in the list into their correct order.  Guidelines to improve the quality of documentation text   Use e‐prime style.   Use consistent terms.   Use parallel grammatical structures.   Use simple language.   Use the passive voice.   Use friendly language. Sequencing of the selected item is not required. Click to select items.

Write down the things that are most important to you in your job and explain why they are important.