What is the primary purpose of documenting rationale and alternatives in architecture notes?

• A. To justify the final choice and facilitate future reviews.
• B. To document every line of code.
• C. To confuse new team members.
• D. To replace the need for code comments.

Answer: (A)

Documenting rationale and alternatives in architecture notes helps ensure decisions are understandable long after they’re made. The best choice emphasizes that architecture notes justify the final decision and make future reviews easier by recording the reasoning, trade-offs, and context that led to the path chosen. This isn’t just about what was decided; it’s about why it was chosen, what constraints and risks influenced that choice, and how the design meets the requirements now and as they evolve. This creates traceability so future team members can reassess the decision, adapt if needed, and learn from the reasoning when onboarding or performing reviews. The other options miss the point: documenting every line of code belongs to implementation details, not high-level architecture notes; architecture notes aren’t meant to confuse readers, and they don’t replace code comments, which explain the actual implementation rather than the design rationale.