architecture

Turns architecture context, options, and consequences into a tangible result by naming the decision, describing context, and capturing consequences.

Core question: Which architecture decision needs to be recorded, and what context, options, decision, and consequences must a future reader understand?

15-45 min

1-3

Turns architecture context, options, and consequences into a tangible result by capturing goals and stakeholders, scoping context, and linking risks and decisions.

Core question: Which architecture decisions, structures, and quality attributes does the reader need in order to understand, operate, and evolve the system?

1-2 Tage

1-4

Turns architecture context, options, and consequences into a tangible result by drawing system context, identifying containers, and adding code-level detail only when needed.

Core question: How can the system be described at the right level of detail for communication and decisions?

1-4 h

1-5

Turns architecture context, options, and consequences into a tangible result by collecting stakeholder goals, eliciting quality scenarios, and documenting architecture implications.

Core question: Which Quality Attributes with which concrete scenarios are architecture-critical for the system, and in which order must they be addressed?

2-4 h

5-15

Turns architecture context, options, and consequences into a tangible result by defining the problem, collecting goals and constraints, and determining next investigations.

Core question: Which minimal architecture decision covers the goals, constraints, and stakeholder needs without prematurely closing options?

1-2 h

3-8

Turns architecture context, options, and consequences into a tangible result by clarifying the communication goal, collecting stakeholders and audiences, and deriving a communication plan.

Core question: Which architecture message reaches which target group in which format, so that decisions, acceptance, or implementation are supported?

60-120 min

2-8

Turns architecture context, options, and outcomes into a tangible result by naming the system and goals, gathering stakeholders and constraints, and documenting decisions and questions.

Core question: Which components, interfaces, decisions and cross-cutting concerns together form a consistent architecture that satisfies the quality attribute scenarios?

1-2 h

3-10

Turns architecture context, options, and outcomes into a tangible result by identifying stakeholders, selecting views, and validating completeness.

Core question: Which views address which stakeholders with which quality concern, and which cross-view information binds them into a consistent picture?

1-3 Tage

1-4

Moves architecture context, options, and consequences toward a concrete result through "place the architecture diagram or plan in the center", "set risk categories such as technical, organizational, and external", and "assign an owner and next steps for each top risk".

Core question: Which risks are embedded in this architecture or plan artifact, and which of them need action before the next iteration?

60-90 min

4-12

Uses a structured proposal and review process to make non-trivial technical or product changes discussable and decidable.

Core question: Which change does the team propose, with which rationale, alternatives and tradeoffs, and who decides by when?

1-3 Wochen vom Draft bis zur Entscheidung

3-20 Reviewer