Component Responsibility Block
Document what a component does and what it does not do. Capture responsibilities, boundaries, dependencies, and owned data for clear architecture communication.
Component responsibility blocks document the purpose and boundaries of architectural components. They answer: What does this component do? What does it NOT do? What data does it own? What does it depend on? Clear responsibility documentation prevents scope creep and clarifies ownership.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Component Name | Yes | Name of the component |
| Responsibilities | Yes | Array of things this component does |
| Description | No | Brief description of the component's purpose |
| Out of Scope | No | Array of things this component explicitly does NOT do |
| Inputs | No | Array of what the component receives |
| Outputs | No | Array of what the component produces |
| Owned Data | No | Array of data this component is authoritative for |
| Dependencies | No | Array of other components this depends on |
| Status | No | Current state: proposed, active, or deprecated |
| Notes | No | Additional context or observations |
Status Values
Example: Payment Service
A core service with clear responsibilities and boundaries.
Example: Notification Service
A supporting service focused on delivery channels.
Example: Search Service
An infrastructure service with technical responsibilities.