SE401:Group32:July 4

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

Meeting with Ian

Architecture

  • Sticking to the scenario that Sakura proposed (Sending over the entire test script instruction set to be executed on the phone).
    • Send the actual application along with Testing.java.
  • Look into extending the XML schema to be applicable to all devices. E.g. If an Image is too large to be displayed on a particular device then that images or test case should be omitted.
  • Stick with the Bluetooth technology and put aside Java RMI.
  • Focus on Functional testing for now, performance later.
  • The bluetooth connection will be left open. Later if we figure it out, we can try closing the connection to save resources.
  • Mobile does all the gathering of data, PC puts it in a legible format
    • Make PC figure out the testing results

Concrete scenarios

  • Need to looking into more complex/interesting scenarios that take into account the mobile devices execution environment. E.g. Network issues such as unavailability, Power Consumption on the mobile device, Timing issues (non-functional) and also possibly bandwidth issues with bluetooth.
  • Basically a look into conditional constraints that address these matters.
  • Want to be able to specify/test the general layout of a form. E.g. Given a component x, it should be left of component y, and below component z.
  • Look into multi-homing. That is given a set of communication methods (e.g. Bluetooth, WiFi or GPRS) which is the best candidate to use for a particular situation. Again this goes back to looking into the mobile devices execution environment.

Scenario revision

  • Scenario 7 - not feasible
  • Scenario 9 - functional component focus, not performance
  • Scenario 10 - Look at it in more detail => it is an interesting case
  • Scenario 11 - execution environment for the device
  • Scenario 12 - Definitely should be done, simple to do
  • Scenario 13 - Usability testing, important
  • Scenario 14 - Express constraints as percentage
  • New scenario 1 - Have a subset of components that should be displayed on the small screen
  • New scenario 2 - Measure energy levels, battery consumption

Conference Paper

  • Ian is to identify a suitable structure for the conference paper relating to the project and to draft what should go in each of the sections.
  • Ian will also take a look at some of the references that have been brought to light during the course of the project.
  • Once a structure is formed, specific sections will be allocated to begin writing.

For next time

  • Revise scenarios
    • How we're going to express all these scenarios in XML
  • Implement fully the testing application i.e. simulate events on phone and send data back to PC


◄ Main Page