Product Architecture: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
<imagemap> | <imagemap> | ||
Image:2.2-ProductArchitecture.png|frameless|1000px|Ignite AIoT - Product Architecture | Image:2.2-ProductArchitecture.png|frameless|1000px|Ignite AIoT - Product Architecture | ||
rect | rect 0 0 642 133 [[AIoT_Execution_and_Delivery|Agile AIoT Grid]] | ||
rect | rect 642 0 1492 133 [[Product_Organization|Leadership and Organization]] | ||
rect | rect 1497 0 1900 133 [[Sourcing_and_Procurement|Sourcing]] | ||
rect 1904 0 2547 133 [[Service_Operations|Service Operations]] | |||
rect | rect 2768 128 3539 257 [[Artificial_Intelligence|AI Implementation]] | ||
rect | rect 2768 257 3539 385 [[Product_Architecture|Architecture]] | ||
rect | rect 2768 385 3539 518 [[AIoT_DevOps_and_Infrastructure|DevOps]] | ||
rect | rect 2768 518 3539 651 [[Trust_and_Security|Trust & Security]] | ||
rect | rect 2768 647 3539 784 [[Reliability_and_Resilience|Reliability & Resilience]] | ||
rect | rect 2768 779 3539 917 [[Verification_and_Validation|Verification & Validation]] | ||
desc none | desc none | ||
</imagemap> | </imagemap> | ||
__NOTOC__ | |||
== AIoT Framework: Product Architecture == | == AIoT Framework: Product Architecture == |
Revision as of 21:05, 9 April 2021
AIoT Framework: Product Architecture
The idea of a product architecture might seem old fashioned to somebody who is used to working in small, agile development teams. After all, the Agile manifesto itself values working software over comprehensive documentation and emphasizes The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. However, in large-scale, multi-team, multi-site projects, a certain amount of documentation is required in order to ensure that all teams and stakeholders are aligned and working in synch. Many AIoT projects will have this problem. Consequently, Ignite AIoT proposes to create and maintain an AIoT Solution Architecture which captures key requirements and design decision in a consistent manner. In order to achieve this, the following viewpoints are proposed:
- AIoT Business Viewpoint: Builds on the input from the Business Model, adds the capability perspective
- AIoT Usage Viewpoint: Focus on how users, assets and other system elements are using the AIoT solution
- AIoT Functional Viewpoint: Focus on the data and functional components of the AIoT solution
- AIoT Implementation Viewpoint: Focus on the implementation aspects
- AIoT Product Viewpoint: Mapping to the agile product development perspective
It is important to notice that Ignite AIoT is not proposing an excessive, RUP/waterfall-style model depth, as can be seen when looking at the individual templates. The general idea of collaboration between the different project stakeholders in the architecture management process is shown in the figure below.
The key to success here is to keep the AIoT Solution Architecture on a level of detail where it is meaningful but not overly complex. The agile teams must be able to apply their own mechanism (e.g. demand-driven design spikes) to derive requirements for their backlog and provide feedback to the overarching architecture in return.
Authors and Contributors
|