Software Architecture Management in SonarQube
summary
SonarQube extracts a current architecture on every scan and displays it as a navigable map (classes, packages, modules) with pan/zoom and high‑level views; teams build an intended architecture model of containers and allowed relationships, add placeholders or request moves/renames, and the scanner flags mismatches — deviations create SonarQube issues that link to offending lines of code. The demo shows automated detection of cyclic tangles, surfacing specific class-to-class references and directives that drive developer remediation.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:37The Three Core Architecture Capabilities
- 1:18Turning Architecture Deviations into Actionable Issues
- 2:19Architecture Dashboard Overview
- 2:52Exploring the Current Architecture Map
- 4:45Tracing Dependencies and Using High-Level Architecture View
- 6:39Building the Intended Software Architecture Model
- 7:49Defining Allowed Relationships Between Components
- 9:42Detecting Architecture Deviations After a Scan
- 10:36Handling Structural Changes: Placeholders, Moves, and Renames
- 14:06Identifying Architecture Flaws and Dependency Tangles
- 16:11Getting Started with Architecture Governance in Sonar
related talks
50mVisualise, Document & Explore Your Software Architecture
01h 15mHow to measure your architecture
46mSoftware Architecture vs Code
42mSoftware Architecture vs Code
58mTesting Software Architecture
48mDown the Ivory Tower towards Agile Architecture
54mResolving technical debts in software architecture
49mBottom-up Architecture: Bridging the Architecture-Code Gap
