Reasons for not needing |
When an architecture is under development, there are virtually no reasons not to record architectural decisions. This
artifact is not needed if the decisions have been captured elsewhere, but be sure you have captured the additional
information such as rationale and options considered.
|
Representation Options |
You may simply document Architectural Decisions as free format text with headings like problem, alternatives,
resolution, and justification. A tabular format in a document or spreadsheet is an effective way to organize
Architectural Decisions. A more sophisticated option is to use databases, collaboration tools, or requirements
management tools.
|