| | 1 | |
| | 2 | == GUI Requirements == |
| | 3 | |
| | 4 | * the GUI needs to show a view of the source code |
| | 5 | ** the source code will usually consist of multiple files, these should be shown in separate windows or tabs |
| | 6 | ** the source view must show line numbers |
| | 7 | * GUI needs to show a view of the AST in a hierarchical way |
| | 8 | * GUI needs to show a view of the CIVL model in a hierarchical way |
| | 9 | * the GUI needs to guide the user through all commands which can be executed through the command line |
| | 10 | ** verify, run, parse, etc. |
| | 11 | ** the GUI should guide the user by showing the options available to each command in some way and letting the user select those options in a graphical way (buttons, menus, etc.) |
| | 12 | ** the GUI should allow the user to specify by inputs by showing the list of input variables in a table, with one row for each input. The table should show the type of the input variable. |
| | 13 | ** for a boolean input variable, the options should be unspecified (always the default), true, or false. |
| | 14 | ** for an integer input variable, the options should be unspecified (again, the default), or some concrete integer that can be typed into a field |
| | 15 | ** etc. |
| | 16 | * the GUI needs to display the trace and allow the user to interact with the trace if a counterexample is found |
| | 17 | * the GUI needs to display the statistics resulting from execution in formatted way (such as a table) |
| | 18 | |
