When code changes, what should you do with related diagrams and API references?

• A. Keep diagrams unchanged
• B. Remove diagrams
• C. Update diagrams to reflect changes
• D. Add new diagrams but not update old ones

Answer: (C)

Keeping documentation visuals in sync with code changes is essential. Diagrams and API references illustrate how components interact and what behavior is available, so when code is updated, the visuals must reflect those changes. If diagrams aren’t updated, they can mislead developers about current architecture, dependencies, or interfaces, leading to mistakes, miscommunication, and maintenance headaches. Updating diagrams to reflect changes keeps the documentation accurate, helps new developers understand the system, and supports correct usage of the API.

Leaving diagrams unchanged preserves outdated information, which can mislead readers. Removing diagrams eliminates a valuable guidance resource. Adding new diagrams without updating the existing ones creates inconsistency and fragmentation in the documentation.