Product / Solution Design: Difference between revisions
Line 22: | Line 22: | ||
Due to the complexity of most AIoT products and solutions, the design will need to capture many different perspectives. Consequently, the AIoT Playbook defines a number of design viewpoints, which will be introduced in the following. | Due to the complexity of most AIoT products and solutions, the design will need to capture many different perspectives. Consequently, the AIoT Playbook defines a number of design viewpoints, which will be introduced in the following. | ||
Of course the design needs to be closely aligned with the requirements. In traditional, often waterfall-oriented projects, a clear differentiation between requirments and design is made. However, agile best practices have led to an approach which merges requirements and design, at least to a certain extend: agile user stories are a mixture of requirements and feature | |||
= The Agile Approach = | = The Agile Approach = |
Revision as of 19:24, 8 August 2021
Requirements and Product / Solution Design
The design of the smart, connected product or solution will have a significant impact on user acceptance and business success. It is important to notice that design is a living thing, and will evolve over time. Especially for products, the software and AI-enabled parts are likely to undergo constant change, based on customer feedback and product performance. However, it is important to notice that certain design decisions made in the early stages of product development will be difficult to be changed. This includes fundamental system architecture decisions including software and AI, as well as everything related to hardware - be it the IT-side of hardware, the mechatronical side, or product body or chassis.
Due to the complexity of most AIoT products and solutions, the design will need to capture many different perspectives. Consequently, the AIoT Playbook defines a number of design viewpoints, which will be introduced in the following.
Of course the design needs to be closely aligned with the requirements. In traditional, often waterfall-oriented projects, a clear differentiation between requirments and design is made. However, agile best practices have led to an approach which merges requirements and design, at least to a certain extend: agile user stories are a mixture of requirements and feature
The Agile Approach
Story Maps
Example: AIoT Story Map & User Stories
AIoT System Design
AIoT Design Viewpoints
AIoT Viewpoint Details
Click HERE for more details on AIoT product / solution design viewpoints.