Sequoyah/archive/EmulatorUseCases

Discussion on Emulator Framework Use Cases

Actors

• Vendor: Vendors are mobile device manufacturers. Vendors typically create and distribute emulators for the devices they produce.
• Developer: Developers are the users of the development environment and/or tools. Developers typically use device emulators to test and debug the applications they develop.

Vendor Use Cases

Support to creation and packaging of device emulators is not yet planned. For one thing, device vendors may have completely different emulator structures, so it is not yet clear whether it is advantageous or not to have tools to support emulator creation by vendors.

Developer Use Cases

UC001: Install a Device Emulator

• Actor: Developer.
• Description: The developer installs or updates a device emulator plug-in containing all components needed to create instances of the device emulator.
• Preconditions: The device emulator plug-in package and a compatible version of the Eclipse platform must be available.
• Result: The device emulator must be installed or updated without affecting any other device emulator on the system; the new emulator must be available for selection when creating an instance of a device emulator.

UC002: Create an Instance of a Device Emulator

• Actor: Developer.
• Description: The developer creates an instance of a device emulator. Some device emulators may not support multiple instances; in such cases, if the developer tries to create another instance, the system must tell the developer that the operation is not permitted.
• Preconditions: The device emulator must be installed on the system.
• Result: A new instance of the selected device emulator must be created and configured; the new emulator instance can be run and used for application deployment and testing.

UC003: Configure an Instance of a Device Emulator

• Actor: Developer.
• Description: The developer modifies properties of an existing instance of a device emulator, e.g. network (IP) address.
• Preconditions: The device emulator instance must have been created.
• Result: The new configuration must be applied to the emulator instance without affecting any other instances of the same emulator or of other emulators.

UC004: Start an Instance of a Device Emulator

• Actor: Developer.
• Description: The developer starts an existing instance of a device emulator, which is equivalent to turning on the device.
• Preconditions: The device emulator instance must have been created.
• Result: The device emulator instance must execute the power up sequence of the emulated device.

UC005: Stop an Instance of a Device Emulator

• Actor: Developer.
• Description: The developer stops an existing instance of a device emulator, which is equivalent to turning off the device.
• Preconditions: The device emulator instance must have been started.
• Result: The device emulator instance must execute the power down sequence of the emulated device.

UC006: Deploy an Application onto an Instance of a Device Emulator

• Actor: Developer.
• Description: The developer selects executable file(s) generated for a compatible device or device emulator and deploys the file(s) into an emulator instance.
• Preconditions: The device emulator instance must have been started, and the selected executable file(s) must be compatible with it.
• Result: The executable file(s) must be transferred to the device emulator and unpackaged and/or installed so that the application can be executed.

UC007: Start an Application on an Instance of a Device Emulator

• Actor: Developer.
• Description: The developer starts the execution of an application on an instance of a device emulator.
• Preconditions: The application must have been previously deployed into the device emulator instance.
• Result: The application is executed on the emulator instance.

UC008: Stop an Application on an Instance of a Device Emulator

• Actor: Developer.
• Description: The developer stops the execution of an application on an instance of a device emulator.
• Preconditions: The application must have been running on the device emulator instance.
• Result: The application is stopped on the emulator instance.

UC009: Provide Input to an Instance of a Device Emulator

• Actor: Developer.
• Description: The developer uses the development environment to send input events to an instance of a device emulator.
• Preconditions: The device emulator instance must have been started.
• Result: The input events are sent to the device emulator as if they were produced on the actual device.

UC010: Visualize Output from an Instance of a Device Emulator

• Actor: Developer.
• Description: The developer uses the development environment to visualize output from an instance of a device emulator.
• Preconditions: The device emulator instance must have been started.
• Result: Output must be sent from the emulator instance to the development environment and displayed in a way that is meaningful to the developer.