A) FalseB) FalseC) TrueD) TrueE) TrueF) True
A) Agile approaches make written documentation unnecessary. In such cases, verbal communication can substitute for documentation.
False. Even in agile approaches, written documentation is important for maintaining a clear and consistent understanding of the architecture among team members and stakeholders1.
B) Written documentation makes verbal reiteration unnecessary.
False. Verbal communication is essential for clarifying and reinforcing the content of written documentation, especially when addressing complex or nuanced architectural issues2.
C) Despite written documentation, verbal communication of architectural interrelationships is important.
True. Verbal communication plays a crucial role in explaining the rationale behind architectural decisions and interrelationships that may not be fully captured in documentation2.
D) Documentation and communication should use identical terms and rationale.
True. Consistency in terminology and rationale between documentation and verbal communication helps prevent misunderstandings and ensures that all parties have a common understanding of the architecture2.
E) Documentation should be created primarily for project participants who either cannot or do not want to read the system’s source code.
True. Documentation serves as a guide for those who may not be directly involved in coding but need to understand the architecture, such as managers, new team members, or external stakeholders2.
F) Communication and documentation complement each other: verbal communication helps architects determine what must be recorded in writing.
True. Verbal communication often reveals what aspects of the architecture are most important or confusing to team members, guiding what should be emphasized in written documentation
Submit