You should apply source-code analysis to identify risks and problems: Both statical (lines-of-code, coupling, cyclomatic complexitx etc) and dynamical analysis (i.e. test coverage, performance-/thread analysis) can help identify risks or problems.
Member of the 42 family
The practical framework for requirements engineering.
The proven template for documenting software architecture. You are on docs.arc42.org, its documentation.
Agentic engineering based on req42 and arc42.
You should apply source-code analysis to identify risks and problems: Both statical (lines-of-code, coupling, cyclomatic complexitx etc) and dynamical analysis (i.e. test coverage, performance-/thread analysis) can help identify risks or problems.