Repository navigation
Initial Call Conference (13.04.2019 Saturday)
Timothy Gillespie edited this page Apr 17, 2019
·
1 revision
- The typical user will be an university student.
- The user is studying about mathematical proofs.
- The user enters a proof to receive feedback about its correctness.
- The user enters a part of a proof to receive hints.
- The user enters a part of a proof to have it autocomplete (fully or partially).
- The user solves given exercises (in order to evaluate his or her learning progress or in order to study).
- implementing the evaluation of propositional logical proofs ("Aussagenlogik")
- sandbox mode (meaning the tasks are freely choosen and entered by the user and no tasks are given)
- creating an expandable base system (basic user interface, prolog <-> javascript interface and conversion)
- detection of vocabulary (i.e. "Es flogt [...]") and syntactical (i.e. or+5; A and or B) errors entered by the user
- Multiple natural expression will correspond to one mathematical object (i.e. "gdw" and "ist äquivalent" is both <->). User input should not be changed by the (prolog) -> (user input) interaction.
- vocabulary (i.e. "Es flogt [...]" as a mistyped version of "Es folgt [...]").
- syntactical (i.e. A and or B; 5*+3; and B)
- unrelated proof (i.e. given: A and B, task: show C, programm actually shows D / something else)
- disobeyed task restrictions (i.e. proof with mathematical induction, but induction has not been used)
- type errors (will be taken care of by diproche; i. e. A * 5 while A is a set)
- semantic errors (will be taken care of by diproche; i.e. (not A or A) <=> false
- static vs dynamic
- how to store static exercises
- simple navigation bar
- user input via textarea object (asthetic akin to Slack's Post Editor?)
- buttons to submit a proof or to receive hints/help
Link to the taken notes: https://drive.google.com/file/d/1TgyAJ3EYj2rNTkrpuZrLR-SbmxqQz1Py/view?usp=sharing