Many developers have asked: "Why can't I find the exact bug or pinpoint precise code changes just by looking at a software architecture diagram?"
The answer might seem frustrating, but it's fundamentally straightforward - Software Architecture is merely a model of the actual software and hardware used in a specific project.
By definition, a model serves to:

• Represent reality in a simplified, comprehensible manner
• Illustrate relationships between different components
• Explain how a system works or potentially could work
• Selectively include or exclude attributes and functionalities of a real object

In essence, your software architecture diagram may sometimes provide specific details to help locate exact code sections. However, in most cases, it functions as a blueprint of the overall solution.
Primarily, a software architecture diagram helps answer two critical questions:

"In which component should I investigate potential code issues?"
"What is the purpose of this component, and how does it integrate with other system components?"

For developers unfamiliar with a project or seeking a comprehensive understanding, the software architecture documentation (often stored in collaboration platforms like Confluence) is the ideal starting point. It provides a high-level overview that guides deeper investigation and understanding of the system's structure and interactions.
Think of a software architecture diagram as a map—it won't show you every tree and rock, but it will help you navigate the terrain and understand the landscape of your software ecosystem.