Batch that runs the analyzers.

Stores:

• configuration of Sonar
• snapshots

Check = Coding Rule.

A good coding practice. Violating coding rules leads to quality flows.

Coding rules can check quality on files, unit tests or packages.

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.

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

A set of coding rules.

Each snapshot is based on a single quality profile.

A set of measures and violations on a given resource at a given time.

A snapshot is generated for each Sonar analysis.

When a resource does not comply with a coding rule, Sonar logs a violation into the snapshot.

A violation can be logged on a file or on a unit test or on a package.

Web page that provides a way to display any data stored in the database.

A dashboard is a set of widgets.

See Dashboards.

It is a box that displays data on a dashboard.

There are two types of widget:

• Global widget that can display data from multiple projects
• Project widget that only displays data from a specific project