Software solutions must be maintainable in the long term, and a good architecture supports this. But how do you know whether the originally defined structure is still viable? How do you find out where improvements are needed? In this session, we investigate forensic code analysis, which examines source code and historical information from your source code control system to uncover valuable hidden patterns. Using a typical application, we discuss what’s behind Hotspots, Change Coupling, and Team/Code Alignment and what they tell us about your architecture. By the end, you will know how to use Forensic Analysis to ensure long-term maintainability for your solutions. Key Takeaways: - How to evaluate your architecture with a forensic analysis? - What's behind Hotspot Analysis and how to interpret results? - What's behind Change Coupling Analysis and how to interpret results? - What's behind Team/Code Alignment Analysis and how to interpret results? - What are the limitations of a forensic analysis?