-
Notifications
You must be signed in to change notification settings - Fork 1
Solution Architecture Canvas
Wayne Phillips edited this page Mar 25, 2019
·
10 revisions
Architecture Canvas is a single page representation of architecture depicting the key elements that capture the architecture of a solution, thereby functioning as a conversation starter. It enables key stakeholders from diverse backgrounds, such as product owners, devops engineers, architects, and developers to come together and discuss and collaborate on architecture from a simple, single page visual.
- The vision and business objective section is used to introduce the business context. It specifies the business vision and the key business objectives that the architecture will realize.
- The Data Integrations section briefly describes the systems and data sources the solution will access.
- The key business scenarios indicate the key problem frames and the scenarios that the architecture is solving for, typically described using up to three high-level user stories. The solution should identify the Mean Viable Product features that need to be delivered.
- Conceptual view of target state is a quick sketch describing architecturally significant components and their interaction that enables the target state solution.
- Cloud Native Principles are the 9 principles the solution architecture should adhere to when the build cloud-native solutions. Not every project will need to adhere to each principle. However, it is up to the solution architect to help determine which principles adhere to based on the business requirements.
- Key capabilities impacted provides a high-level snapshot of impacted capabilities. This is typically categorized as business applications, services, information stores, technology infrastructure, etc., and it can also indicate which of the components are new to the architecture, which are being modified, and which are being made redundant and being removed.
- Key assumptions, risks, and decisions list the set of key assumptions and risks taken into account while working on the architecture, and also some architecturally significant decisions made in the process.