SE401:Group32:August 25

Meeting with Ian

Conference paper

• Ian has read the evaluation section and had a few comments:
  • Include the specifications for the task that the participants had to do
  • Include the specifications that show of more of the fancy stuff that Hermes does. But say that only a small scope was chosen for the evaluation
  • Mention the things that cannot be done manually
    • Perhaps have this represented in a tabular format
  • State the reasons for why we did the experiment the way that we did
    • I.e. why we chose two groups, A and B? Reasons for the timing? etc
  • Describe what were the things you were seeking from the questionnaire for the survey
  • Show a screen shot of one of the applications that we got the users to test, so that we can tie this into the specifications
  • Don't call them errors, perhaps deviations
  • Spell out exactly what the faults were. I.e. functional navigation
  • Regarding the graphs, be careful about colours as it will be printed in black and white. Also note this for the FR.
  • Mention the differences between vendor emulators and Sun emulators
  • Justify the conduction of the experiment, using HCI best practices
  • Look at the design section and try to bring up to date

Extensibility

• Image capture is a good scenario
  • Can be used to describe the viewing of tables that can't fit on the screen.
• Another extensibility to Hermes is the design of a tool that shows a visual model of the GUI, which states the names of components and the associated component types
• Rename Performance to Performance environment