| 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. | |
| Dashboard | Web page that provides a way to display any data stored in the database. A dashboard is a set of widgets. | See Dashboard. |
| Database | Stores:
| See Architecture Overview. |
| Filter | TODO | See Filters. |
| Metric | A property of a resource. Examples: number of lines of code, complexity, etc. A metric may be either:
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:
| |
| 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. | |
| Widget | TODO |
Labels

