This requires a preset architecture standard that explains specifically what boxes and arrows are, and how boxes/arrows interact. Lots of software smears a logical box out over several folders in the code, sometimes even with entirely different names. I don't just mean people write non-cohesive code, I mean frameworks tend to prefer organisation by layer ("the views go in the view folder!") instead of organisation by module ("These things work and change together with a defined boundary").
You can have what you're asking for if you agree to a predefined architecture and everyone agrees to write code that way.
You can have what you're asking for if you agree to a predefined architecture and everyone agrees to write code that way.