[Spring] Thesis document feedback

[dluman]

This feedback spans both the document and overall artifact. The two categories are labeled below.

Document

• the Experiments section would benefit more from results being captured in tabular form and discussed at a higher level; SQL queries are less helpful as they don't show results, only ways that a reader might get results given the same or self-generated data
  • suggestion: replace SQL with the data discussed in the paragraphs below
• the Method of Approach section contains too much code; one way to address this is to create diagrams of functionality rather than a copied/pasted source
  • this would also help you add more figures to the document and make diagrams explain rather than show static content
• in the Method of Approach section, much of the content takes the same rationale as the API, that it's self-explanatory; given that readers are likely to not have access to any of this information, more tables/figures would describe the process of integrating the technology behind the application
• the writing should discuss what we've realized about the application: that it allows large-scale betting simulation on what you've referred to as a previously-unexplored betting behavior
  • how could this application further research?

Artifact

• you've acknowledged aesthetic changes that you'd like to make; the largest opportunity is in betting history; what could be done to make this feature easier to user when a user needs it and less apparent when they want to ignore it?