...
This interface focuses on a fusion between a command line approach and a drawing approach. Information about shots can be input into the text field at the bottom and their direction can be drawn onto the onscreen court. After shots are input into the system, they go into one of the rows on the right side of the screen. If an error was made, the user can cancel that entry and redo it. Furthermore, a video of the game is being kept, as shown in the top left corner of the screen. This allows for each shot that is input to be mapped to a portion of the video, which allows users to better contextualize the recorded statistics.
Storyboard Designs 
The game is underway and the next serve goes to MIT’s number 50. As soon as the ball leaves his hands, the recorder is already halfway done recording the hit, entering the command representing the unsuccessful serve out of the court’s bounds on Harvard’s end. As soon as he begins typing, the controller interprets his instruction, updating the display of the translated command into its real-time visualization next to the command prompt. Finishing his command, he presses enter to add the translated statistic to the command stack and starts preparing for the next serve. An issue has come up, however: in the process of inserting commands the user didn’t realize that Harvard’s server was the player responsible for serving the previous out of bounds case. Thanks to the slightly delayed display of the game (as recorded via the user’s external camera) the user notices the discrepancy and presses the F4 key to edit the corresponding value in the command stack. As soon as he hits enter, focus returns back to the command prompt, allowing him continue tying efficiently and record the stats.
...