• Hardware
• Software
• Applications
• • Healthcare
  • Emergency response
  • Maintenance
  • • Objectives of the user tests
    • Participants in the tests
    • Task scenario
    • Experiment setup
    • Testing methodology and procedure
    • Data collection and analysis
    • Results
  • Production

By following the approach “start with the simple and go to the complex” the application developer took the opportunity to use the WUI-Toolkit not only to implement the final application but also to design the first mock-up. The concept of the WUI-Toolkit allows starting developing an application for wearables without taking care of any design or hardware issues. Only structural issues in the abstract user interface (AUI) have to be taken into account in the beginning of the development. In iterative steps the application gets more and more concrete by adding content, refining the structure and taking other constraints (e.g. hardware availability) into account.
The development team took the decision to work on a cabin scenario that is one of the subtasks of the “Removal and Installation Scenario” and deals with the removal and installation of a passenger seat in the cabin. This task offers on the one hand a potential of a benefit by introducing wearables and on the other hand the possibility of the implementation of innovative wearable concepts. The following steps give an overview of the task that has to be per-formed to remove a cabin seat:

Open scheduled procedures (Jobcard)
1. Open circuit breaker to disable electrical entertainment system
2. Walk to seat
3. Remove seat-track covers
4. Mark position of seat
5. Disconnect electrical connector under the seat
6. Loose seat stops at the back of the seat
7. Loose screws at the front of the seats
8. Push seat backwards with hammer
Job close up

After having designed the AUI first constraints were taken into account, such as content constraints, hardware constraints, and usability constraints. Content constraints were mainly caused by the Aircraft Maintenance Manual (AMM) that is only available in paper format for most of the aircrafts. The usability constraints strongly correlated with the content constraints in a way that usability requires appropriate representation of content in order to enable usability. For this reason, usability tests were performed previously by addressing the operators’ needs. The results of the usability tests and the content constraints caused a creation of customized content in the form of different media (audio, video and images) that induced a rework of the WUI-Toolkit addressing the framework developer for integration of services that can deal with different types of media. In a very similar way the application developer dealt with the hardware constraints.
Taking into account which I/O devices the final application will support should not be the focus of an application developer. Again, the application developer does not care about the I/O hardware devices, because the WUI-Toolkit handles the device issues like navigation devices and, e.g., HMDs. While getting more and more concrete, other constraints arose that were solved either by the application developer or by the framework developer depending on the type of constraint.