IoT Design Principles - sedioben/IoTproject GitHub Wiki

The IoT design principles are underlying common principles across different applications. The principles can be determined using metaphors or observation and automation. While in metaphors, the technology should react in the same way as a user to imitate user behavior through the technologies, in observation the users are observed and domain knowledge is included. In the following, the four principles "Embedding", "Invisibility", "Manual Override" and "Feedback" will be considered in more detail: [1]

Embedding

A fundamental principle of IoT solutions is to embed the technologies and associated services into real objects and processes. Although the computers are no longer perceived as such, the objects are still fully recognizable and usable. Thus, a seamless integration into the existing environment is achieved without media breaks or other recognizable interruptions. [1]

The Come'N'Eat service follows the concept of the embedded service. It aims to significantly reduce media disruptions within the food delivery process by creating a seamless E2E IoT solution where the food deliverer provides the prepared meal to the customer's home and offers the customer a home dining experience. There are several embedded systems and smart objects involved in enabling our scenario. The central component is the backend service that provides the analysis of the personal profile (health data, fitness data, movement data, nutrition preferences) and the offering of the meal suggestion as well as the authentication for the deliverer's access to the customer's apartment. Connected are:

  • the smartphone with an application to the backend service
  • the NFC tag, authenticating access of the deliverer through the smartphone app
  • the smart lock that is connected through a bridge with the central component
  • the Amazon Echo, coordinating the deliverer specific to the user preferences in the apartment

Invisibility

An IoT application is invisible if the technology works in the background, i.e. the user does not have to operate the technology explicitly and separately from the object and additionally no separate GUI is required: [1]

The Come'N'Eat Service fulfills the criteria of "Invisibility" for the following scenarios:

  • Analysis of health data for meal suggestions
  • Automatic triggering of the order and delivery of the food
  • Auto-detection for Just-in-Time delivery according to the geolocation of the customer
  • Validation and authentication of the supplier and granting access to the customer's home

The only GUI, the user needs, is in the selection of food suggestions.

Manual Override

With manual override, the user has the possibility to intervene manually. The system must recognize and accept this so that the automatic settings are overwritten. [1]

The Come'N'Eat Service fulfills the criteria of "Manual Override" for the following scenarios:

  • Manual setting of the delivery time by the customer
  • Rejection of the meal suggestions by the customer
  • Order of other meals than the suggested ones
  • Access authorization for the supplier is withdrawn by the customer

Feedback

Feedback means that the interaction of IoT is still traceable and the system behavior is comprehensible. The principle of invisibility must be in accordance with the comprehensibility of the behavior. [1]

The Come'N'Eat Service fulfills the criteria of "Feedback" for the following scenarios:

  • Customer receives notifications about meal suggestions, triggering of the order, deliverer entering and leaving the apartment and when the meal is ready for dining

Source: [1] Decker, C.: Lecturer Slides: Chapter 05 - IoT Anwendungen (2019)