Constraint Block
Document project constraints that limit design choices. Track technical, regulatory, commercial, and organisational constraints with their sources and impacts.
Constraints are limitations that restrict architecture choices. Unlike requirements that describe what the system must do, constraints describe what the system cannot do or must work within. Documenting constraints helps explain why certain decisions were made.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Statement | Yes | The constraint being imposed, expressed clearly |
| Description | No | Detailed explanation of the constraint and its context |
| Type | No | Category: technical, organisational, regulatory, legal, legacy, or commercial |
| Rigidity | No | Whether the constraint is hard (non-negotiable) or soft (potentially flexible) |
| Source | No | Where this constraint originates from |
| Authority | No | Who imposed or can change this constraint |
| Impact on Design | No | How this constraint affects architecture decisions |
| Workarounds | No | Possible alternatives or mitigations if any exist |
| Status | No | Current state: active, pending, or expired |
| Review Date | No | When to re-evaluate if the constraint still applies |
| Notes | No | Additional context or observations |
Type Values
Rigidity Values
Example: Budget Constraint
A commercial constraint that limits infrastructure spending.
Example: Regulatory Constraint
A compliance requirement that mandates specific data handling.
Example: Legacy Integration Constraint
A technical constraint from an existing system that cannot be changed.
Example: Organisational Constraint
A soft constraint from organisational preferences that could potentially be negotiated.