SE401:Group32:August 19

From Marks Wiki
Revision as of 05:21, 3 November 2008 by Mark (Sọ̀rọ̀ | contribs) (2 revision(s))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Experiment/Evaluation wrap up and Meeting with Ian

Experiment/Evaluation wrap up

  • Finished collecting evaluation study from the test subjects
  • Should start to collate the data from the evaluation

Meeting with Ian

  • Discussed the evaluation
    • Summarized the main points regarding the evaluation
    • The XML generator part would be solved if given more time
  • Emulators
    • Found that the Sun emulators return incorrect layout information about the components on the screen. However this seems to be fine for the vendor specific emulators.
    • Regarding the vendor specific emulators inconsistencies with the following were found:
        1. The component size - Emulator for the particular device did not return the correct width and height of a component
        2. The Image screen space usage - Images displayed on the emulator took up a different amount of screen space than when executed on the physical device.
        3. Memory usage - Different memory consumption values were returned for the execution of a test script.
    • Develop examples showing layout and timing behavior
    • Also add functionality to connect to other devices using Bluetooth.
  • J2ME API
    • The Java ME API is limited in what kind of information can be retrieved about a mobile device. E.g. The battery level cannot be found. However counter to this example, the Motorola vendor allows for the access to the battery level via a request of a system property.
  • Conference Paper
    • Start writing the evaluation section for the conference paper.
    • Might be good to incorporate things like example scripts in the evaluation section.
    • Focus on getting all the text out, and then can work on filtering out repetition later.

By Next Meeting (Mon 25 Aug 1pm)

  • Aim to have the battery level thing done
  • Do a bluetooth connectivity test
  • Try to think of where it would be possible to have a new kind of check supported!