AIoT Usage Viewpoint: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
<imagemap> | <imagemap> | ||
Image:2.2-v-UsageViewpoint.png|800px|frameless|center|AIoT Usage Viewpoint | Image:2.2-v-UsageViewpoint.png|800px|frameless|center|AIoT Usage Viewpoint | ||
rect 540 234 694 407 [[AIoT_Usage_Viewpoint#Sketch|AIoT Solution Sketch]] | rect 540 234 694 407 [[AIoT_Usage_Viewpoint#Sketch|AIoT Solution Sketch]] | ||
| Line 8: | Line 6: | ||
rect 869 232 1014 407 [[AIoT_Usage_Viewpoint#Mockup|AIoT Mockups / Wireframes]] | rect 869 232 1014 407 [[AIoT_Usage_Viewpoint#Mockup|AIoT Mockups / Wireframes]] | ||
rect | rect 2 759 134 836 [[Product_Architecture|Product/Solution Architecture]] | ||
rect | rect 333 26 1156 205 [[AIoT_Business_Viewpoint|AIoT_Business_Viewpoint]] | ||
rect | rect 337 437 1160 616 [[AIoT_Data_and_Functional_Viewpoint|AIoT Data/Functional Viewpoint]] | ||
rect | rect 337 642 1162 821 [[AIoT_Implementation_Viewpoint|AIoT Implementation Viewpoint]] | ||
rect 1178 26 1493 823 [[AIoT_Product_Viewpoint|AToT Product Viewpoint]] | |||
desc none | desc none | ||
</imagemap> | </imagemap> | ||
Revision as of 08:54, 31 January 2021
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.
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.
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.
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.
