# SW-T01: Component responsibilities

Adrian Sutherland · Version 1.0 · Refreshed September 2026

© 2005–2026 Adrian Sutherland.
Source page: https://architectureportal.org/assets/systems

Map relevant questions into existing records; identify open decisions.

## Process areas

A Simple Architectural Framework (ASAF) describes four continuing areas of work.

Map the work to your actual stages and reviews. Areas may share a review or
repeat at different scopes. Keep the accepted starting point between cycles.

| ASAF process area | Question | Your activity, owner and retained record |
|---|---|---|
| Visioning | What future outcome and qualities should this change serve? | [fill] |
| Transforming | What changes, checks and handover are required? | [fill] |
| Operating | How will the result be run, supported and observed? | [fill] |
| Governing | Who accepts decisions, exceptions and any wider reconsideration? | [fill] |

## Purpose and scope

Which behaviour belongs here, and which business outcome does it support?

## Responsibilities

Name each component, its inputs, results and authority.

## Dependencies

Which interfaces separate meaning from delivery mechanisms? What must real adapters guarantee?

## State and failure

Who owns state, concurrency, unknown results and retries?

## Change and checks

Link versions, representative checks, support ownership and open choices.