How Do We Read Formal Claims? Eye-Tracking and the Cognition of Proofs about Algorithms
Hammad Ahmad, Zachary Karas, Kimberly Diaz, Amir Kamil, Jean-Baptiste Jeannin, Westley Weimer
Abstract
Formal methods are used successfully in high-assurance software, but they require rigorous mathematical and logical training that practitioners often lack. As such, integrating formal methods into software has been associated with numerous challenges. While educators have placed emphasis on formalisms in undergraduate theory courses, such courses often struggle with poor student outcomes and satisfaction. In this paper, we present a controlled eye-tracking human study (n = 34) investigating the problem-solving strategies employed by students with different levels of incoming preparation (as assessed by theory coursework taken and pre-screening performance on a proof comprehension task), and how educators can better prepare low-outcome students for the rigorous logical reasoning that is a core part of formal methods in software engineering. Surprisingly, we find that incoming preparation is not a good predictor of student outcomes for formalism comprehension tasks, and that student self-reports are not accurate at identifying factors associated with high outcomes for such tasks. Instead, and importantly, we find that differences in outcomes can be attributed to performance for proofs by induction and recursive algorithms, and that better-performing students exhibit significantly more attention switching behaviors, a result that has several implications for pedagogy in terms of the design of teaching materials. Our results suggest the need for a substantial pedagogical intervention in core theory courses to better align student outcomes with the objectives of mastery and retaining the material, and thus bettering preparing students for high-assurance software engineering.
Ask about this paper
Your agent reads all of it.
Lune indexed this paper to the last equation, along with the top-tier papers that cite it. Ask a question and the answer quotes them.
Cited by top-tier papers1
Ask how each one uses itBuilds on2
- Neurological divide: an fMRI study of prose and code writingRyan Krueger, Yu Huang, Xinyu Liu, Tyler Santander et al.ICSE 2020 · 38 citations
- Biases and differences in code review using medical imaging and eye-tracking: genders, humans, and machinesYu Huang, Kevin Leach, Zohreh Sharafi, Nicholas McKay et al.FSE 2020 · 37 citations
Related papers
- I see an IC: A Mixed-Methods Approach to Study Human Problem-Solving Processes in Hardware Reverse EngineeringRené Walendy, Markus Weber, Jingjie Li, Steffen Becker et al.CHI 2024 · 1 citation
- Forge: A Tool and Language for Teaching Formal MethodsTim Nelson, Ben Greenman, Siddhartha Prasad, Tristan Dyer et al.OOPSLA 2024 · 8 citations
- The Role of Working Memory in Program TracingWill Crichton, Maneesh Agrawala, Pat HanrahanCHI 2021 · 13 citations
- Barriers for Students During Code Change ComprehensionJustin Middleton, John-Paul Ore, Kathryn T. StoleeICSE 2024 · 7 citations
- Lean-STaR: Learning to Interleave Thinking and ProvingHaohan Lin, Zhiqing Sun, Sean Welleck, Yiming YangICLR 2025
