Goals

Ease of use

It should be easy to analyze source code and view the results with coderadar. Minimal configuration. User friendly interface.

• automatically checks out a remote VCS repository and runs analyses over a set of commits

Incremental analysis

Source code analysis needs time and processing resources. For each commit in a VCS analysis runs only on those files that actually have changed.

• only run the plugins that have to run (i.e. when the codebase has a compile error, the plugins that need bytecode cannot be run, but the plugins that need source code should run nevertheless)

Refactoring support

Coderadar should be able to interpret VCS metadata to recognize which files have been renamed or moved and not treat a renamed/moved file as a new one and thus distort source code metrics.

Quality Profiles

Users should be able to select which metrics are most important to them and combine them to a "quality profile". With such a profile they should be able to monitor quality changes for each commit to the codebase.

Incremental Quality Monitoring

Quality metrics should be made available for each commit into a VCS. The user should be able to view quality metrics for each commit and compare them to thos of another commit.