An Efficient and Collaborative Way to Define your Software Architecture Playground. For more details see Architecture Inception Canvas.
Here is your WHY Brief description of the business case or economic driver behind the software system.
This is your product box The most important functional requirements at a high level.
The key drivers of architecture The three most important quality goals for the architecture, which have the highest priority for the most important stakeholder.
Explore the context and get the scope Separate your system under construction as a black box from all its communication partners. Communication partners are neighbouring external systems and users.
Your limitation of freedom Any organisational requirement that limits the software architects freedom of decision.
Your limitation of freedom Any technical requirement that limits the software architects freedom of decision.
Create your first high-level architectural hypotheses based on your current knowledge Resulting architectural hypotheses and important, expensive, large-scale or risky decisions, including justifications.
What are the upcoming challenges and the resulting risks? Identified current known challenges and technical risks.
What is the core business case or economic driver?
-
For whom are we creating value?
-
Who are the customers?
-
Who is paying?
-
Who is contributing?
Most important functions?
Supported processes or activities
Speed, scalability, reliability, usability, security, safety, capacity, flexibility or similar.
Important external interfaces or neighbouring systems, including important actors or user roles
Which decisions lead to the current state?
Major building blocks of the system, important subsystems, modules, services.
Important technologies used for development and operation.
-
Potential problems and risks?
-
What information is missing or has gotten lost?
-
What is hindering the team from delivering better value faster?