31:T55a,md`### Domain Problem Characterization This level covers the initial task of defining the domain problem. The author notes the importance of needing to ensure that the problem is specific enough that it can then properly serve as input to the next level. An important step in defining one's domain space is interviewing users. ### Data Abstraction Design In order for the outputs of this level to properly serve as inputs to the next, the researcher must work to abstract the information from the domain characterization into a series of _operations_ that are more readable from an information visualization standpoint. The author writes about how many different researchers have classified different operations for this step and how it's an important step that people often skip in an attempt to jump to the third step, leading to useless or counterproductive visualizations. ### Visual Encoding and Interaction Design The author speaks to the important of consdiering visual encoding and interaction design together, as they are mutually interdependent, but writes that they've been discussed extensively in other literature and doesn't dwell much on them here. ### Algorithm Design Like the previous level, the author notes that algorithm design is something of great focus in computer science literature and does not speak much at all about the subject here.`32:T428,md`### Domain Problem Characterization One of the most pertinent threats outlined at this level is the threat of incorrectly asserting that the tartget audience would benefit from a visualization tool, when they may in fact not. ### Data Abstraction Design The threat at this level is that the operations and data types that the reseracher chooses do not adequetly solve the problem that the target audience has characterized. ### Visual Encoding and Interaction Design The described threat for this level of visualization design can be summed up as ineffective communication. If the visualization is inefficient at properly communicating the information to the target audience, that's definitely a threat to it's success as a tool. ### Algorithm Design For algorithm design, a big threat is speed and resource requirements. The algorithm should not be slower than previously designed algorithms or too slow in regards to theoretical predicitions. Additionally, the algorithm should not be more resource-intensive than previous or theoretical assumptions.`33:T787,md`## Visualization Analysis For **two visualizations**, you are going to use the Nested Model of visualization design to describe what _you believe_ to be the intention of the work. For each one, you should first _display the visualization_ (either by importing it from a Notebook, or putting an \`\` or \`