BMAD-METHOD/bmad-agent/templates/architecture-decision-recor...

207 lines
5.8 KiB
Markdown

# Architecture Decision Record
## Document Information
| Document Details | |
|-----------------|--------------------------------------|
| **Title** | Architecture Decision Record |
| **Decision ID** | [Unique Identifier, e.g., ADR-001] |
| **Status** | [Proposed/Accepted/Superseded/Deprecated] |
| **Date** | [Decision Date] |
| **Deciders** | [Names of decision-makers] |
| **System/Domain**| [System or Domain Name] |
## 1. Context
### 1.1 Decision Statement
[Clearly state the architectural decision that needs to be made. Frame it as a specific question that requires resolution.]
### 1.2 Business Context
[Describe the business context that makes this decision necessary, including business drivers, objectives, and constraints.]
### 1.3 Technical Context
[Describe the technical context surrounding this decision, including existing architecture, technical constraints, and dependencies.]
### 1.4 Decision Drivers
[List the key factors that are driving this decision.]
| Driver | Description | Priority |
|--------|-------------|----------|
| [Driver] | [Description] | [High/Medium/Low] |
| [Driver] | [Description] | [High/Medium/Low] |
| [Driver] | [Description] | [High/Medium/Low] |
## 2. Options Considered
### 2.1 Option 1: [Option Name]
#### 2.1.1 Description
[Provide a detailed description of this option, including how it would be implemented and its key characteristics.]
#### 2.1.2 Alignment with Decision Drivers
| Driver | Alignment | Notes |
|--------|-----------|-------|
| [Driver] | [Strong/Moderate/Weak] | [Notes] |
| [Driver] | [Strong/Moderate/Weak] | [Notes] |
| [Driver] | [Strong/Moderate/Weak] | [Notes] |
#### 2.1.3 Benefits
- [Benefit 1]
- [Benefit 2]
- [Benefit 3]
#### 2.1.4 Risks and Concerns
- [Risk/Concern 1]
- [Risk/Concern 2]
- [Risk/Concern 3]
#### 2.1.5 Cost and Implementation Considerations
[Describe the cost, effort, and implementation considerations for this option.]
### 2.2 Option 2: [Option Name]
[Repeat the structure for each option considered.]
### 2.3 Option 3: [Option Name]
[Repeat the structure for each option considered.]
## 3. Decision
### 3.1 Chosen Option
**Selected Option: [Option Name]**
[State the option that was selected and provide a brief explanation of why it was chosen.]
### 3.2 Justification
[Provide a detailed justification for the decision, explaining how the chosen option best addresses the decision drivers and business needs.]
### 3.3 Consequences
#### 3.3.1 Positive Consequences
- [Positive Consequence 1]
- [Positive Consequence 2]
- [Positive Consequence 3]
#### 3.3.2 Negative Consequences
- [Negative Consequence 1]
- [Negative Consequence 2]
- [Negative Consequence 3]
### 3.4 Compliance Requirements
[Describe any compliance requirements that the chosen option must meet, including standards, policies, and regulations.]
## 4. Implementation
### 4.1 Implementation Approach
[Describe the approach for implementing the decision, including phasing, dependencies, and key milestones.]
### 4.2 Required Changes
[List the changes required to implement the decision, including changes to systems, processes, and documentation.]
| Change | Description | Impact | Effort |
|--------|-------------|--------|--------|
| [Change] | [Description] | [Impact] | [High/Medium/Low] |
| [Change] | [Description] | [Impact] | [High/Medium/Low] |
| [Change] | [Description] | [Impact] | [High/Medium/Low] |
### 4.3 Validation Criteria
[Define criteria for validating that the decision has been implemented correctly and is achieving the desired outcomes.]
| Criterion | Description | Measurement Approach |
|-----------|-------------|---------------------|
| [Criterion] | [Description] | [Approach] |
| [Criterion] | [Description] | [Approach] |
| [Criterion] | [Description] | [Approach] |
## 5. Related Decisions
### 5.1 Prerequisite Decisions
[List any decisions that were prerequisites for this decision.]
| Decision ID | Title | Relationship |
|-------------|-------|-------------|
| [ID] | [Title] | [Description of relationship] |
| [ID] | [Title] | [Description of relationship] |
### 5.2 Dependent Decisions
[List any decisions that depend on this decision.]
| Decision ID | Title | Relationship |
|-------------|-------|-------------|
| [ID] | [Title] | [Description of relationship] |
| [ID] | [Title] | [Description of relationship] |
### 5.3 Related Decisions
[List any other decisions that are related to this decision.]
| Decision ID | Title | Relationship |
|-------------|-------|-------------|
| [ID] | [Title] | [Description of relationship] |
| [ID] | [Title] | [Description of relationship] |
## 6. Notes
### 6.1 Assumptions
[Document any assumptions made during the decision-making process.]
### 6.2 Constraints
[Document any constraints that influenced the decision.]
### 6.3 Open Questions
[Document any questions that remain open and may need to be addressed in the future.]
### 6.4 References
[List any references used in making the decision, including documents, standards, and research materials.]
## 7. Review and Approval
### 7.1 Review History
| Reviewer | Role | Date | Comments |
|----------|------|------|----------|
| [Name] | [Role] | [Date] | [Comments] |
| [Name] | [Role] | [Date] | [Comments] |
| [Name] | [Role] | [Date] | [Comments] |
### 7.2 Approval
| Approver | Role | Date | Signature |
|----------|------|------|-----------|
| [Name] | [Role] | [Date] | [Signature] |
| [Name] | [Role] | [Date] | [Signature] |
| [Name] | [Role] | [Date] | [Signature] |
## 8. Revision History
| Version | Date | Author | Description of Changes |
|---------|------|--------|------------------------|
| [Version] | [Date] | [Author] | [Description] |
| [Version] | [Date] | [Author] | [Description] |
| [Version] | [Date] | [Author] | [Description] |
```