Four-step smart hardware exception case

This article has been published by the author Yu Zhenzhen authorized Netease cloud community.

Welcome to the Netease cloud community to learn more about the operation experience of Netease technology products.

Compared with software, smart hardware products are more complicated due to the status of hardware and software. Due to the slow iteration and update of hardware products, once the product is launched with problems, it is much more difficult than the software, which leads to operational confusion and product unavailability, therefore, designers must take all the situations into consideration during the product design process.

Exception case sorting is typically performed by enumeration based on the product use scenario and operation sequence. This method is time-consuming, laborious, and easy to omit. For example, when you use an app to connect to the hardware, the hardware is accidentally powered off, the mobile phone Bluetooth is not enabled, and the hardware broadcast delay is abnormal, however, the designer cannot determine whether the exception case on this operation node is comprehensive, missing, and reasonable.

For the first time, intelligent hardware is indispensable for all kinds of pitfalls. However, in this process, we gradually find a more intuitive way to troubleshoot intelligent hardware exceptions, the exception case I sorted out in this way is more comprehensive than the case reported to me by the engineer. It is available for test. You may try it.

In the Netease cloud music on-board Bluetooth player project, the Netease cloud music app must check whether communication between hardware and software is normal for each step of hardware operations, therefore, I mainly applied this tool in case of Bluetooth connection exceptions.

Step 1: Split and combine the status. Split the software and hardware status (or exception case). For example, split the software into two States: A and B; the hardware is split into two States: 1 State, 2 state, and then combine various States to get the A-1, A-2, B-1, B-2 four states.

By splitting and restructuring the Bluetooth status of software and hardware, you can get the mobile phone Bluetooth on-player Bluetooth on, mobile phone Bluetooth on-player Bluetooth off, mobile phone Bluetooth off-player Bluetooth on, mobile phone Bluetooth off-player Bluetooth status. All exception cases are caused by these four States (causes.

Step 2: sort the task flow and determine the key contacts for interaction. Users can sort and sort the interactive touch points in the product process according to the application scenario. The interaction touch points can be detailed based on the current product design stage. The procedure of using the on-board Bluetooth player is divided into four steps: first use, first set frequency, non-first set frequency, exit.

Step 3: Create a query table to sort out abnormal cases. The preceding four key contacts and four States form a matrix. In the matrix, the exception situations under the corresponding interaction contact points and hardware and software status (exception case cause) are sorted out.

Step 4: design a solution for each exception case. The most important thing is to design the corresponding prompt text and form based on the exception case, the occurrence scenario, and the task node.

In this product design, whether the hardware Bluetooth is enabled or not is connected by the logo light on/OFF and breathing/always on to remind the user; in case of software exceptions, various pop-up windows and pages in the app can be used with different text prompts, note that exception cases caused by the same reason may have different prompts on different nodes.

Such a look-up table is intuitive and comprehensive, and all project participants can easily understand product exception cases based on it.

 

Some Supplement tips for table creation:

1. multi-person cooperation. The interaction designer can organize product planning and software and hardware engineers to participate in the tabulation. The participants of the project can ensure that everyone understands the problem, reach consensus, and improve the efficiency of subsequent communication.

2. The interaction contact points mentioned in step 2 can be changed according to the stages used in The lookup table. For example, in the early stage of product planning, you can use a look-up table to predict abnormal cases of products in each stage. In the middle and late stages of design, you can place specific interaction nodes on the task flow coordinates, it is convenient for us to capture the nodes when exceptions occur and check for missing vacancies.

3. The software and hardware status and interaction contact point are common dimensions, but they are not unique. Depending on the project, you can adjust the dimension of the query as appropriate. The principle of "most useful" for the project is as follows.

Free trial of cloud security (yundun) content security, verification code and other services

For more information about Netease technologies, products, and operations, click.

Related Articles:
[Recommendation] Android view partially disappears

Four-step smart hardware exception case