Call Graph Output
call-graph-output owns presentation, not design.
Would this known relationship be easier to understand as a graph?
Use when
Section titled “Use when”- explaining an execution path
- documenting service/component relationships
- showing production vs test call paths
- rendering a responsibility or delegation trace
Don’t use when
Section titled “Don’t use when”Do not use the graph format to invent architecture or make decisions that have not been established.
Example
Section titled “Example”Production:
HTTP handler → BookingService.create → ConflictPolicy.check → BookingRepository.insert
Tests:
BookingService.create → real ConflictPolicy → test database repository