AIoT Usage Viewpoint: Difference between revisions

No edit summary
Line 13: Line 13:
</imagemap>
</imagemap>


==  Usage Viewpoint ==
The goal of the usage viewpoint is to provide a holistic view of how the product will be used. This can include, for example, a refined AIoT Solution Sketch, User Journeys, as well as mockups / wireframes.
__TOC__


== <span id="Sketch"></span>AIoT Solution Sketch ==
== <span id="Sketch"></span>AIoT Solution Sketch ==

Revision as of 15:50, 6 June 2021

Business ViewpointUsage ViewpointData/Functional ViewpointImplementation ViewpointProduct ViewpointProduct ArchitectureAIoT Usage Viewpoint


AIoT Solution Sketch

The AIoT Solution Sketch from the Business Model can be refined in this perspective, adding additional layers of detail, in a slightly more structured way of presenting it.

AIoT Solution Sketch

User Journeys

Similarly, User Journeys from the Business Model can be used as a starting point. Often it can be a good idea in this phase of the product design to create individual journey maps for different scenarios, adding more detail to the original, high-level journey.

Customer Journey

UX / HMI Strategy

The UX/HMI strategy will have a huge impact on useability. Another important factor is the question, how much the supplier will be able to learn about how the user is interacting with the product. This is important, for example, for product improvements, but also potentially for up-selling and digital add-on services.

UX/HMI Strategy

Mockups / Wireframes

UI mockups / wireframes are a powerful way of communicating the interactive parts of the product design, e.g. web interfaces and apps for smart phones or tablets. They should initially be kept on the conceptual level. Tools like Balsamiq offer a comic-style way of creating mockups, making sure that they are not mistaken for detailed UI implementation designs.

Mockup