Sonar Concepts

Concept	Definition	Related Topics
Check	Check = Coding Rule.
Client	Batch that runs source code analyzers to compute snapshots.	See Architecture Overview.
Coding Rule	A good coding practice. Violating coding rules leads to quality flows.
Database	Stores: configuration of Sonar snapshots	See Architecture Overview.
Metric	A property of a resource. Examples: number of lines of code, complexity, etc. A metric may be either: qualitative: gives a quality indication on the resource (ex: density of duplicated lines, line coverage by unit tests, etc.) or quantitative: does not give a quality indication on the resource (ex: number of lines of code, complexity, etc.) The value of the metric for a given resource is called measure.	See detailed documentation on metrics.
Measure	The value of a metric for a given resource at a given time. Examples: 125 lines of code on class myClass Density of duplicated lines of 30.5% on project myProject
Quality Profile	A set of coding rules. Each snapshot is based on a single quality profile.
Resource	A piece of software. Examples: project, package, module, file, etc.
Server	Web Server that is used to navigate the snapshots and make configuration	See Architecture Overview .
Snapshot	A set of measures and violations on a given resource at a given time. A snapshot is generated for each Sonar analysis.
Violation	When a resource does not comply with a coding rule, Sonar logs a violation to the snapshot.