Create a thorough GOMS model for contacting a professor to ask for explanation of a grade. In doing so$,$ make sure to $($a$)$ identify the initial situation, $($b$)$ describe the selection rules, $($c$)$ outline several methods, $($d$)$ identify the operators that comprise those methods $($along with the estimated amount of time each operator takes to execute$),$ and $($e$)$ describe the ultimate goal.

You are not required to use the visualization schema seen in the lectures: you could use a simple outline format instead. However, your GOMS model should stand on its own with no explanatory text: every part of your submission should be a part of the initial situation, selection rules, methods, operators, or the final goal.

Hint: Note that for screen real estate, the GOMS models shown in the lectures do not actually show selection rules or execution times for individual operators. For selection rules, you can phrase these as either boxes that precede the method $($e$.$g$.$ a box that says $$Message is formal$$ prior to a method regarding email$)$ or as a separate list of conditionals $($e$.$g$.$If the message is formal, choose the $$email$$ method; if a back and forth conversation is expected, choose the $$go in person$$ method.$).$

Question $4($~$1\mathrm{.}5$ pages$)$

Create a hierarchical task analysis of the task of submitting this assignment to Canvas and subsequently receiving one$$s grade and feedback. We recommend creating this as plaintext outline instead of in a graphical form as shown in the lectures.

Your operators for this hierarchical task analysis should be very low$-$level: entering a URL, scrolling down, clicking a link, and selecting a file from the file browser would all be operators.

These operators should be grouped into larger tasks that will ultimately accomplish the goal. We would expect at least three levels of hierarchy above the operator level: the top level can be the task as a whole $($Complete an assignment$),$ further subdivided into sub$-$tasks and sub$-$sub$-$tasks before the operator level. You$$re welcome to include more layers to the hierarchy if you feel they$$re appropriate.

Your model should stand on its own; there should be no paragraphs of text supporting the answer to this question. However, text can be placed within the model to annotate, explain, or enhance the model$$s contents if you$$d like $($but this is not required$).$

Hint: The semantics of hierarchical task analyses don$$t need to be quite as specific as GOMS models. For example, you could include triggers for tasks $($such as a task being triggered when an email is received$)$ or waiting times $($such as waiting a week before completing a follow$-$up task$).$