What should documentation of decisions and trade-offs include?

• A. Document only the final choice without context.
• B. Record rationale, alternatives considered, and recommended choices in project docs or architecture notes.
• C. Keep decisions private to avoid external confusion.
• D. Write lengthy theory unrelated to decisions.

Answer: (D)

Documenting decisions and trade-offs should capture the rationale, the alternatives considered, and the recommended path in project or architecture notes. This creates a traceable record of why a particular direction was chosen, what other options were weighed, and how the decision aligns with goals, constraints, and risks. Including the rationale and the considered alternatives helps future team members understand the context, reassess decisions when requirements change, and evaluate impact if changes are needed. It also supports onboarding, governance, and maintenance.

Why this is the best approach: it goes beyond just noting a choice and provides the reasoning, evidence, and alternatives that informed it, which makes decisions repeatable and easier to revisit.

Why the other options don’t fit: documenting only the final choice omits context and rationale; keeping decisions private reduces transparency and future maintainability; writing theory unrelated to the decision fails to provide any practical guidance or traceability.