Super practical Four steps to help you handle the smart hardware exception case

The first time to do intelligent hardware, without all kinds of pit, but in this process is also gradually explore a more intuitive intelligent hardware abnormal case to check the method, through this method I combed out of the exception than the engineer reported to me a comprehensive, pro-test available, you may wish to try.

Compared with the software, intelligent hardware products because of the hardware and software involved in the two-side state, its exception case to be more complex. Because the hardware product iteration update is slow, once brings the problem on-line to be more troublesome than the software, the light causes the operational confusion, the heavy causes the product to be unable to use, therefore the designer must in the product design process all circumstances to be considerate.

The usual way to comb the exception case is to enumerate the product using scene and operation order one by one, which is time-consuming, laborious and easy to omit. For example, when using the app to connect the hardware, the user accidentally gives the hardware power off, the phone does not open, hardware broadcast delay, and other abnormal case, but the designer can not determine whether the operation node on the abnormal case has been exhaustive, no omission and the corresponding hint is reasonable.

The first time to do intelligent hardware, without all kinds of pit, but in this process is also gradually explore a more intuitive intelligent hardware abnormal case to check the method, through this method I combed out of the exception than the engineer reported to me a comprehensive, pro-test available, you may wish to try.

NetEase Cloud Music in-car Bluetooth player project, NetEase Cloud Music app to hardware every step of the operation to detect the communication between hardware and software is normal, so I mainly apply this tool in the comb Bluetooth connection abnormal case.

　　The first step is to split the state into groups

Split the state of the hardware and software (or the exception case reason) For example, the software is split into two states--a state and B state, hardware split into two state--1 state, 2 state, and then combine various states, that is, A-1, A-2, B-1, B-24 states.

By splitting and reorganizing the software and hardware Bluetooth status can get mobile phone Bluetooth open-player Bluetooth open, mobile phone bluetooth on-player Blue jaw, mobile phone blue teeth-player Bluetooth open, mobile phone blue teeth-player blue jaw four states. All the exception case is caused by these four states (causes).

　　The second step is to comb the task flow and determine the interaction key contacts.

According to the use scenario, the user uses the interactive contact points in the product flow to comb and sort, and the level of the interaction points can be determined according to the current product design stage. The process of using the car Bluetooth player is divided into four steps: First use, first set frequency, not the first set frequency, exit.

　　The third step, the establishment of the check table, sorting out abnormal case

Make a crosstab table of 4 key contacts and 4 states that were previously sorted out. In the table, the corresponding interaction point and the hardware and software state (abnormal case reason) under the exception of the collation.

　　The fourth step is to design a solution for each abnormal case

The most important point is based on the exception case and the occurrence of the scene, task node design corresponding hint copy and form.

In this product design, the hardware Bluetooth is open and whether the connection is through the logo lights on/off and breathing/illuminated steady to prompt the user, and the software exception case can be through the app in various window, the page with different copy tips, One thing to note is that the exception case that is caused by the same reason may have different prompts on different nodes.

Such a checklist is intuitive and comprehensive, and all project participants can easily understand the product exception case according to it.

Some additional tips for making a checklist:

1. Multi-person cooperation. Interactive designers can organize product planning and software and hardware engineers to participate in the production of the checklist, the participation of project stakeholders to ensure that everyone's understanding of the problem, reach a consensus, improve the follow-up communication efficiency.

2. The interactive contact points referred to in step II may vary according to the stage used by the look-up table. For example, in the early stage of product planning, we can check the abnormal case of the products at various stages, and in the middle and later of the design, we can put the specific interaction nodes on the task flow coordinates, so as to facilitate us to catch the opportunity node of abnormal case and check the vacancy.

3. Hardware and software states and interactive contacts are relatively easy to check the dimension, but not the only. According to different projects, can be adjusted to check the dimensions, everything to the project "most useful" as the principle.

Welcome to the public number of NetEase cloud music Chinese: