Documentation Metrics


All metrics used in the quality model are described thereafter, with useful information and references. They are classified according to their source. Please note also that several other metrics may be retrieved but not used in the quality model.



  • Number of jobs ( CI_JOBS )

    Provided by: Hudson , Jenkins

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

    The total number of jobs defined on the Hudson engine.

  • Number of failed jobs one week ( CI_JOBS_FAILED_1W )

    Provided by: Hudson , Jenkins

    Used by: QM_ACTIVITY

    Scale: 1 < 10 ≤ 2 < 5 ≤ 3 < 3 ≤ 4 < 0 ≤ 5

    The number of jobs that failed during last week on the Hudson engine.

  • Number of green jobs ( CI_JOBS_GREEN )

    Provided by: Hudson , Jenkins

    Used by:

    Scale: 1 < 0 ≤ 2 < 3 ≤ 3 < 5 ≤ 4 < 10 ≤ 5

    The number of green (successful) jobs on the Hudson engine.

    Green (or blue) jobs in Hudson define successful builds.

  • Ratio of green jobs ( CI_JOBS_GREEN_RATIO )

    Provided by: Hudson , Jenkins

    Used by: QM_REL_ENG

    Scale: 1 < 25 ≤ 2 < 50 ≤ 3 < 75 ≤ 4 < 95 ≤ 5

    The number of green (successful) jobs on the Hudson engine, divided by the total number of jobs.

    Green (or blue) jobs in Hudson define successful builds.

  • Number of red jobs ( CI_JOBS_RED )

    Provided by: Hudson , Jenkins

    Used by:

    Scale: 1 < 10 ≤ 2 < 5 ≤ 3 < 3 ≤ 4 < 0 ≤ 5

    The number of red (failed) jobs on the Hudson engine.

    Red jobs in Hudson define failed builds.

  • Number of yellow jobs ( CI_JOBS_YELLOW )

    Provided by: Hudson , Jenkins

    Used by:

    Scale: 1 < 10 ≤ 2 < 5 ≤ 3 < 3 ≤ 4 < 0 ≤ 5

    The number of yellow (unstable) jobs on the Hudson engine.

    Yellow jobs in Hudson define unstable builds. According to Hudson's documentation, a build is unstable if it was built successfully and one or more publishers report it unstable. For example if the JUnit publisher is configured and a test fails then the build will be marked unstable.

  • ITS Authors ( ITS_AUTHORS )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of different authors who created issues during the lifetime of the project.

    A high number of authors shows diversity and improves the bus factor of the project.

  • ITS authors last month ( ITS_AUTHORS_1M )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by: QM_DIVERSITY

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of authors who created issues during last month. If today is 2017-02-01 then the range is from 2017-01-01 to 2017-02-01.

  • ITS authors last week ( ITS_AUTHORS_1W )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of authors who created issues during last week. If today is Wed. 2017-02-01 then the range is from Wed. 2017-01-25 to Wed. 2017-02-01.

  • ITS authors last year ( ITS_AUTHORS_1Y )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of authors who created issues during last year. If today is 2017-02-01 then the range is from 2016-02-01 to 2017-02-01.

  • ITS issues created last month ( ITS_CREATED_1M )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of issues created during last month. If today is 2017-02-01 then the range is from 2017-01-01 to 2017-02-01.

  • ITS issues created last week ( ITS_CREATED_1W )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of issues created during last week. If today is Wed. 2017-02-01 then the range is from Wed. 2017-01-25 to Wed. 2017-02-01.

  • ITS issues created last year ( ITS_CREATED_1Y )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of issues created during last year. If today is 2017-02-01 then the range is from 2016-02-01 to 2017-02-01.

  • ITS Total issues ( ITS_ISSUES_ALL )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Number of issues registered in the database, whatever their state is.

  • ITS Late issues ( ITS_LATE )

    Provided by: GitLabIts , JiraIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of issues with a past due date.

    It is considered good practice to keep this number low. Either fix it or maintain its due date.

  • ITS Open issues ( ITS_OPEN )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by: QM_RELIABILITY

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Number of issues with a state 'open' at the time of analysis.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ITS Open issues (%) ( ITS_OPEN_PERCENT )

    Provided by: Bugzilla , JiraIts

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Percentage of open issues compared to the overall number of issues registered in the system.

  • ITS Pending issues ( ITS_OPEN_UNASSIGNED )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Number of issues in state open with no assignee (i.e. pending).

    It is considered to be good practice to keep this number low. In an active project, people would either work on the bug (i.e. assign it) or triage it (pass it to some other state or assigning it).

  • ITS issues updated last month ( ITS_UPDATED_1M )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by: QM_ACTIVITY , QM_SUPPORT

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of issues updated during last month. If today is 2017-02-01 then the range is from 2017-01-01 to 2017-02-01.

  • ITS issues updated last week ( ITS_UPDATED_1W )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of issues updated during last week. If today is Wed. 2017-02-01 then the range is from Wed. 2017-01-25 to Wed. 2017-02-01.

  • ITS issues updated last year ( ITS_UPDATED_1Y )

    Provided by: Bugzilla , GitLabIts , JiraIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of issues updated during last year. If today is 2017-02-01 then the range is from 2016-02-01 to 2017-02-01.

  • User ML Authors ( MLS_USR_AUTHORS )

    Provided by: EclipseForums

    Used by:

    Scale: 1 < 2 ≤ 2 < 5 ≤ 3 < 20 ≤ 4 < 40 ≤ 5

    The total number of different identities found in the User mailing list.

    Having many different authors is a sign of diversity and activity. It makes the support more reliable (i.e. increased presence of people) and more complete (i.e. more eyes to solve a problem).

  • User ML Authors ( MLS_USR_AUTHORS_1M )

    Provided by: EclipseForums

    Used by: QM_DIVERSITY , QM_SUPPORT

    Scale: 1 < 1 ≤ 2 < 3 ≤ 3 < 5 ≤ 4 < 8 ≤ 5

    The total number of different identities found in the User mailing list during last month.

    Having many different authors is a sign of diversity and activity. It makes the support more reliable (i.e. increased presence of people) and more complete (i.e. more eyes to solve a problem).

  • User ML Authors ( MLS_USR_AUTHORS_1W )

    Provided by: EclipseForums

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 5 ≤ 5

    The total number of different identities found in the User mailing list during last week.

    Having many different authors is a sign of diversity and activity. It makes the support more reliable (i.e. increased presence of people) and more complete (i.e. more eyes to solve a problem).

  • User ML Authors ( MLS_USR_AUTHORS_1Y )

    Provided by: EclipseForums

    Used by:

    Scale: 1 < 2 ≤ 2 < 5 ≤ 3 < 20 ≤ 4 < 40 ≤ 5

    The total number of different identities found in the User mailing list during last year.

    Having many different authors is a sign of diversity and activity. It makes the support more reliable (i.e. increased presence of people) and more complete (i.e. more eyes to solve a problem).

  • User ML Posts ( MLS_USR_POSTS )

    Provided by: EclipseForums

    Used by:

    Scale: 1 < 5 ≤ 2 < 50 ≤ 3 < 100 ≤ 4 < 500 ≤ 5

    The total number of posts found in the User mailing list.

    Having many posts shows the mailing list is active. It encourages people to participate, ask and answer questions.

  • User ML Posts ( MLS_USR_POSTS_1M )

    Provided by: EclipseForums

    Used by: QM_ACTIVITY

    Scale: 1 < 5 ≤ 2 < 10 ≤ 3 < 20 ≤ 4 < 50 ≤ 5

    The total number of posts found in the User mailing list during last month.

    Having many posts shows the mailing list is active. It encourages people to participate, ask and answer questions.

  • User ML Posts ( MLS_USR_POSTS_1W )

    Provided by: EclipseForums

    Used by:

    Scale: 1 < 2 ≤ 2 < 5 ≤ 3 < 10 ≤ 4 < 20 ≤ 5

    The total number of posts found in the User mailing list during last week.

    Having many posts shows the mailing list is active. It encourages people to participate, ask and answer questions.

  • User ML Posts ( MLS_USR_POSTS_1Y )

    Provided by: EclipseForums

    Used by:

    Scale: 1 < 5 ≤ 2 < 50 ≤ 3 < 100 ≤ 4 < 500 ≤ 5

    The total number of posts found in the User mailing list during last year.

    Having many posts shows the mailing list is active. It encourages people to participate, ask and answer questions.

  • User ML Threads ( MLS_USR_THREADS )

    Provided by: EclipseForums

    Used by:

    Scale: 1 < 5 ≤ 2 < 20 ≤ 3 < 50 ≤ 4 < 200 ≤ 5

    The total number of threads (one question followed by zero or more answers) found in the User mailing list.

    Having many threads shows the mailing list is active. It encourages people to participate, ask and answer questions.

  • User ML Threads ( MLS_USR_THREADS_1M )

    Provided by: EclipseForums

    Used by: QM_SUPPORT

    Scale: 1 < 2 ≤ 2 < 5 ≤ 3 < 10 ≤ 4 < 20 ≤ 5

    The total number of threads (one question followed by zero or more answers) found in the User mailing list during last month.

    Having many threads shows the mailing list is active. It encourages people to participate, ask and answer questions.

  • User ML Threads ( MLS_USR_THREADS_1W )

    Provided by: EclipseForums

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 5 ≤ 4 < 10 ≤ 5

    The total number of threads (one question followed by zero or more answers) found in the User mailing list during last week.

    Having many threads shows the mailing list is active. It encourages people to participate, ask and answer questions.

  • User ML Threads ( MLS_USR_THREADS_1Y )

    Provided by: EclipseForums

    Used by:

    Scale: 1 < 5 ≤ 2 < 20 ≤ 3 < 50 ≤ 4 < 200 ≤ 5

    The total number of threads (one question followed by zero or more answers) found in the User mailing list during last year.

    Having many threads shows the mailing list is active. It encourages people to participate, ask and answer questions.

  • Number of releases ( PMI_REL_VOL )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 1 ≤ 2 < 3 ≤ 3 < 5 ≤ 4 < 10 ≤ 5

    The number of releases recorded in the PMI.

    Milestones are retrieved from the PMI file and are counted whatever their target release is. Milestones are useful to assess the maturity of the release and improves predictability of the project's output, in terms of quality and time.

  • Access information ( PROJECT_ACCESS_INFO )

    Provided by: EclipsePmi , GitLabProject

    Used by: QM_DOC

    Scale: 1 < 0 ≤ 2 < 1 ≤ 3 < 2 ≤ 4 < 3 ≤ 5

    Is the access info (downloads, update sites..) correctly filled in the PMI records?

    The project management infrastructure file holds information about how to access binaries of the project. This test checks the number of access-related entries defined in the PMI: download_url, downloads, update_sites.

  • CI information ( PROJECT_CI_INFO )

    Provided by: EclipsePmi , GitLabProject

    Used by:

    Scale: 1 < 0 ≤ 2 < 2 ≤ 3 < 4 ≤ 4 < 6 ≤ 5

    Is the continuous integration info correctly filled in the PMI records?

    The project management infrastructure file holds information about the location of CI services. This test checks the number of ci-related entries defined in the PMI.

  • Doc information ( PROJECT_DOC_INFO )

    Provided by: EclipsePmi , GitLabProject

    Used by: QM_DOC

    Scale: 1 < 0 ≤ 2 < 2 ≤ 3 < 4 ≤ 4 < 6 ≤ 5

    Is the documentation info correctly filled in the PMI records?

    The project management infrastructure file holds information about various documentation and manuals. This test checks the number of doc-related entries defined in the PMI: build_doc, documentation, documentation_url, forums, gettingstarted_url, mailing_lists, website_url, wiki_url.

  • ITS information ( PROJECT_ITS_INFO )

    Provided by: EclipsePmi , GitLabProject

    Used by: QM_DOC

    Scale: 1 < 2 ≤ 2 < 3 ≤ 3 < 4 ≤ 4 < 5 ≤ 5

    Is the bugzilla info correctly filled in the PMI records?

    The project management infrastructure file holds information about one or more bugzilla instances. This test checks that at least one bugzilla instance is defined, with a product identifier, a create_url to enter a new issue, and a query_url to fetch all the issues for the project.

  • Number of releases ( PROJECT_REL_VOL )

    Provided by: EclipsePmi

    Used by: QM_REL_ENG

    Scale: 1 < 1 ≤ 2 < 3 ≤ 3 < 5 ≤ 4 < 10 ≤ 5

    The number of releases recorded in the PMI.

    Milestones are retrieved from the PMI file and are counted whatever their target release is. Milestones are useful to assess the maturity of the release and improves predictability of the project's output, in terms of quality and time.

  • SCM information ( PROJECT_SCM_INFO )

    Provided by: EclipsePmi , GitLabProject

    Used by: QM_DOC , QM_SCM

    Scale: 1 < 0 ≤ 2 < 1 ≤ 3 < 1 ≤ 4 < 2 ≤ 5

    Is the source_repo info correctly filled in the PMI records?

    The project management infrastructure file holds information about one or more source repositories. This test checks that at least one source repository is defined, and accessible.

  • SCM authors ( SCM_AUTHORS )

    Provided by: Git

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 18 ≤ 5

    Total number of identities found as authors of commits in source code management repository.

    Source code management repositories are those considered as such in the project documentation. Commits in all branches are considered. Date used for each commit is 'author date' (when there is a difference between author date and committer date). An identity is considered as author if it appears as such in the commit record (for systems logging several identities related to the commit, authoring identity will be considered).

  • SCM authors one month ( SCM_AUTHORS_1M )

    Provided by: Git

    Used by: QM_DIVERSITY , QM_SCM

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 18 ≤ 5

    Total number of identities found as authors of commits in source code management repositories dated during the last month.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as a one month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • SCM authors one week ( SCM_AUTHORS_1W )

    Provided by: Git

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 18 ≤ 5

    Total number of identities found as authors of commits in source code management repositories dated during the last week.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as a one week period starting the day before the data retrieval.

  • SCM authors one year ( SCM_AUTHORS_1Y )

    Provided by: Git

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 18 ≤ 5

    Total number of identities found as authors of commits in source code management repositories dated during the last year.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as a one year period starting the day before the data retrieval (example: if retrieval is on Feb 3rd 2016, period is from Feb 3rd 2015 to Feb 3rd 2016, both included).

  • SCM Commits ( SCM_COMMITS )

    Provided by: Git

    Used by:

    Scale: 1 < 2 ≤ 2 < 5 ≤ 3 < 13 ≤ 4 < 121 ≤ 5

    Total number of commits in source code management repositories.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date).

  • SCM Commits one month ( SCM_COMMITS_1M )

    Provided by: Git

    Used by: QM_ACTIVITY , QM_SCM

    Scale: 1 < 2 ≤ 2 < 5 ≤ 3 < 13 ≤ 4 < 121 ≤ 5

    Total number of commits in source code management repositories dated during the last month.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as a one month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • SCM Commits one week ( SCM_COMMITS_1W )

    Provided by: Git

    Used by:

    Scale: 1 < 2 ≤ 2 < 5 ≤ 3 < 13 ≤ 4 < 121 ≤ 5

    Total number of commits in source code management repositories dated during the last week.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as a one week period starting the day before the data retrieval.

  • SCM Commits one year ( SCM_COMMITS_1Y )

    Provided by: Git

    Used by:

    Scale: 1 < 2 ≤ 2 < 5 ≤ 3 < 13 ≤ 4 < 121 ≤ 5

    Total number of commits in source code management repositories dated during the last year.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as a one year period starting the day before the data retrieval (example: if retrieval is on Feb 3rd 2016, period is from Feb 3rd 2015 to Feb 3rd 2016, both included).

  • SCM committers ( SCM_COMMITTERS )

    Provided by: Git

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 18 ≤ 5

    Total number of identities found as committers of commits in source code management repository.

    Source code management repositories are those considered as such in the project documentation. Commits in all branches are considered. Date used for each commit is 'committer date' (when there is a difference between author date and committer date). An identity is considered as committer if it appears as such in the commit record.

  • SCM committers one month ( SCM_COMMITTERS_1M )

    Provided by: Git

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 18 ≤ 5

    Total number of identities found as committers of commits in source code management repositories dated during the last month.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'committer date' (when there is a difference between author date and committer date). Time range is measured as a one month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • SCM committers one week ( SCM_COMMITTERS_1W )

    Provided by: Git

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 18 ≤ 5

    Total number of identities found as committers of commits in source code management repositories dated during the last week.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'committer date' (when there is a difference between author date and committer date). Time range is measured as a one week period starting the day before the data retrieval.

  • SCM committers one year ( SCM_COMMITTERS_1Y )

    Provided by: Git

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 18 ≤ 5

    Total number of identities found as committers of commits in source code management repositories dated during the last year.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'committer date' (when there is a difference between author date and committer date). Time range is measured as a one year period starting the day before the data retrieval (example: if retrieval is on Feb 3rd 2016, period is from Feb 3rd 2015 to Feb 3rd 2016, both included).

  • SCM Changed Lines ( SCM_MOD_LINES )

    Provided by: Git

    Used by:

    Scale: 1 < 1000 ≤ 2 < 5000 ≤ 3 < 50000 ≤ 4 < 500000 ≤ 5

    Total number of changed lines (added, removed, changed) in source code management repositories.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date).

  • SCM Changed Lines one month ( SCM_MOD_LINES_1M )

    Provided by: Git

    Used by: QM_ACTIVITY

    Scale: 1 < 20 ≤ 2 < 50 ≤ 3 < 100 ≤ 4 < 500 ≤ 5

    Total number of changed lines (added, removed, changed) in source code management repositories dated during the last month.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as a one month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • SCM Changed Lines one week ( SCM_MOD_LINES_1W )

    Provided by: Git

    Used by:

    Scale: 1 < 10 ≤ 2 < 20 ≤ 3 < 50 ≤ 4 < 100 ≤ 5

    Total number of changed lines (added, removed, changed) in source code management repositories dated during the last week.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as a one week period starting the day before the data retrieval.

  • SCM Changed Lines one year ( SCM_MOD_LINES_1Y )

    Provided by: Git

    Used by:

    Scale: 1 < 50 ≤ 2 < 100 ≤ 3 < 500 ≤ 4 < 1000 ≤ 5

    Total number of changed lines (added, removed, changed) in source code management repositories dated during the last year.

    Source code management repositories are those considered as such in the project documentation. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as a one year period starting the day before the data retrieval (example: if retrieval is on Feb 3rd 2016, period is from Feb 3rd 2015 to Feb 3rd 2016, both included).

  • Stack Overflow Answers (5Y) ( SO_ANSWERS_VOL_5Y )

    Provided by: StackOverflow

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    The number of answers to questions related to the project's tag posted on Stack Overflow during the last 5 years.

    Having many answers posted about the project indicates a strong interest from the community, and a good support. The list of questions and their answers associated to the tag can be browsed on the Stack Overflow web site.

  • Stack Overflow Answer rate (5Y) ( SO_ANSWER_RATE_5Y )

    Provided by: StackOverflow

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 4 ≤ 4 < 5 ≤ 5

    The average number of answers per questions related to the project's tag on Stack Overflow during the last 5 years.

    Having many answers posted about the project indicates a strong interest from the community, and a good support. The list of questions and their answers associated to the tag can be browsed on the Stack Overflow web site.

  • Stack Overflow Askers (5Y) ( SO_ASKERS_5Y )

    Provided by: StackOverflow

    Used by:

    Scale: 1 < 1 ≤ 2 < 3 ≤ 3 < 5 ≤ 4 < 10 ≤ 5

    The number of distinct people asking questions related to the project's tag posted on Stack Overflow during the last 5 years.

    Having many people ask questions about the project indicates a strong interest from the community, and a good support. The list of questions and their answers associated to the tag can be browsed on the Stack Overflow web site.

  • Stack Overflow Questions (5Y) ( SO_QUESTIONS_VOL_5Y )

    Provided by: StackOverflow

    Used by:

    Scale: 1 < 5 ≤ 2 < 50 ≤ 3 < 400 ≤ 4 < 800 ≤ 5

    The number of questions related to the project's tag posted on Stack Overflow during the last 5 years.

    Having many questions posted about the project indicates a strong interest from the community. The list of questions associated to the tag can be browsed on the Stack Overflow web site.

  • Stack Overflow Views (5Y) ( SO_VIEWS_VOL_5Y )

    Provided by: StackOverflow

    Used by:

    Scale: 1 < 100 ≤ 2 < 1000 ≤ 3 < 2500 ≤ 4 < 5000 ≤ 5

    The total number of views for questions related to the project's tag on Stack Overflow during the last 5 years.

    Having many views on questions about the project indicates a strong interest from the community. The list of questions and their answers associated to the tag can be browsed on the Stack Overflow web site.

  • Stack Overflow Votes (5Y) ( SO_VOTES_VOL_5Y )

    Provided by: StackOverflow

    Used by:

    Scale: 1 < 10 ≤ 2 < 100 ≤ 3 < 250 ≤ 4 < 500 ≤ 5

    The total number of votes on questions related to the project's tag on Stack Overflow during the last 5 years.

    Having many votes on questions about the project indicates a strong interest from the community. The list of questions and their answers associated to the tag can be browsed on the Stack Overflow web site.

  • Number of comment lines ( SQ_COMMENT_LINES )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 500 ≤ 2 < 1000 ≤ 3 < 10000 ≤ 4 < 50000 ≤ 5

    Number of lines containing either comment or commented-out code.

    Non-significant comment lines (empty comment lines, comment lines containing only special characters, etc.) do not increase the number of comment lines.

    For Java, file headers are not counted as comment lines (as they usually define the license).

    Lines containing the following instructions are counted both as comments and lines of code: AUTHOR, INSTALLATION, DATE-COMPILED, DATE-WRITTEN, SECURITY.

  • Comment lines density ( SQ_COMR )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 10 ≤ 2 < 20 ≤ 3 < 30 ≤ 4 < 40 ≤ 5

    Density of comment lines = Comment lines / (Lines of code + Comment lines) * 100.

    With such a formula, 50% means that the number of lines of code equals the number of comment lines and 100% means that the file only contains comment lines

  • Commented code ( SQ_COM_CODE )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 40 ≤ 2 < 30 ≤ 3 < 20 ≤ 4 < 10 ≤ 5

    Commented lines of code

    See more information about commented code on SonarQube doc web site. There is a well-documented debate on Stack Overflow as well.

  • Test coverage ( SQ_COVERAGE )

    Provided by: SonarQube45

    Used by: QM_MAINTAINABILITY , QM_RELIABILITY

    Scale: 1 < 10 ≤ 2 < 20 ≤ 3 < 40 ≤ 4 < 50 ≤ 5

    Overall test coverage.

  • Branch coverage ( SQ_COVERAGE_BRANCH )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 10 ≤ 2 < 20 ≤ 3 < 40 ≤ 4 < 50 ≤ 5

    Branch test coverage.

  • Line coverage ( SQ_COVERAGE_LINE )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 10 ≤ 2 < 20 ≤ 3 < 40 ≤ 4 < 50 ≤ 5

    Line test coverage.

  • Total complexity ( SQ_CPX )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

    It is the complexity calculated based on the number of paths through the code. Whenever the control flow of a function splits, the complexity counter gets incremented by one. Each function has a minimum complexity of 1. This calculation varies slightly by language because keywords and functionalities do.

    For more information on line counting for each language, see https://docs.sonarqube.org/display/SONAR/Metrics+-+Complexity.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • File complexity ( SQ_CPX_FILE_IDX )

    Provided by: SonarQube45

    Used by: QM_RELIABILITY

    Scale: 1 < 10 ≤ 2 < 20 ≤ 3 < 30 ≤ 4 < 40 ≤ 5

    Average complexity by file.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Duplicated lines (%) ( SQ_DUPLICATED_LINES_DENSITY )

    Provided by: SonarQube45

    Used by: QM_MAINTAINABILITY

    Scale: 1 < 40 ≤ 2 < 30 ≤ 3 < 20 ≤ 4 < 10 ≤ 5

    Density of duplication = Duplicated lines / Lines * 100.

  • Number of files ( SQ_FILES )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 100 ≤ 2 < 500 ≤ 3 < 1000 ≤ 4 < 5000 ≤ 5

    The total number of files analysed.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Number of functions ( SQ_FUNCS )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 300 ≤ 2 < 500 ≤ 3 < 3000 ≤ 4 < 5000 ≤ 5

    Number of functions. Depending on the language, a function is either a function or a method or a paragraph.

    For Java, constructors are considered as methods and accessors are considered as methods if the sonar.squid.analyse.property.accessors property is set to false.

    For Cobol, it is the number of paragraphs.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Number of lines of code ( SQ_NCLOC )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 500 ≤ 2 < 1000 ≤ 3 < 10000 ≤ 4 < 50000 ≤ 5

    Number of physical lines that contain at least one character which is neither a whitespace or a tabulation or part of a comment.

    For Cobol, generated lines of code and pre-processing instructions (SKIP1, SKIP2, SKIP3, COPY, EJECT, REPLACE) are not counted as lines of code.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Package Tangle index ( SQ_PACKAGES_TANGLE_IDX )

    Provided by: SonarQube45

    Used by: QM_MAINTAINABILITY

    Scale: 1 < 0.05 ≤ 2 < 0.1 ≤ 3 < 0.2 ≤ 4 < 0.5 ≤ 5

    The Package tangle index, as defined in SonarQube.

  • Public API ( SQ_PUBLIC_API )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 500 ≤ 2 < 1000 ≤ 3 < 5000 ≤ 4 < 10000 ≤ 5

    Number of public Classes + number of public Functions + number of public Properties

  • Public documented API (%) ( SQ_PUBLIC_API_DOC_DENSITY )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 40 ≤ 2 < 30 ≤ 3 < 20 ≤ 4 < 10 ≤ 5

    Density of public documented API = (Public API - Public undocumented API) / Public API * 100

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Sqale Debt ratio ( SQ_SQALE_DEBT_RATIO )

    Provided by: SonarQube45

    Used by: QM_MAINTAINABILITY

    Scale: 1 < 0.05 ≤ 2 < 0.1 ≤ 3 < 0.2 ≤ 4 < 0.5 ≤ 5

    The Technical Debt Ratio, as defined in Sqale.

  • Technical debt ( SQ_SQALE_INDEX )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 5000 ≤ 2 < 1000 ≤ 3 < 500 ≤ 4 < 100 ≤ 5

    Effort to fix all maintainability issues. The measure is stored in minutes in the DB.

  • Maintainability rating ( SQ_SQALE_RATING )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 0.05 ≤ 2 < 0.1 ≤ 3 < 0.2 ≤ 4 < 0.5 ≤ 5

    Rating given to your project related to the value of your Technical Debt Ratio. The default Maintainability Rating grid is: A=0-0.05, B=0.06-0.1, C=0.11-0.20, D=0.21-0.5, E=0.51-1.

    The Maintainability Rating scale can be alternately stated by saying that if the outstanding remediation cost depends on the time that has already gone into the application: A <=5% , B between 6 to 10%, C between 11 to 20%, D between 21 to 50%, and anything over 50% is an E.

  • Number of statements ( SQ_STATEMENTS )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 500 ≤ 2 < 1000 ≤ 3 < 10000 ≤ 4 < 50000 ≤ 5

    Number of statements.

    For Java, it is the number of statements as defined in the Java Language Specification but without block definitions. Statements counter gets incremented by one each time a following keyword is encountered: if, else, while, do, for, switch, break, continue, return, throw, synchronized, catch, finally..

    Statements counter is not incremented by a class, method, field, annotation definition, package declaration and import declaration.

    For Cobol, a statement is one of move, if, accept, add, alter, call, cancel, close, compute, continue, delete, display, divide, entry, evaluate, exitProgram, goback, goto, initialize, inspect, merge, multiply, open, perform, read, release, return, rewrite, search, set, sort, start, stop, string, subtract, unstring, write, exec, ibmXmlParse, ibmXmlGenerate, readyReset, mfCommit, mfRollback.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Number of blocker issues ( SQ_VIOLATIONS_BLOCKER )

    Provided by: SonarQube45

    Used by: QM_RELIABILITY

    Scale: 1 < 100 ≤ 2 < 50 ≤ 3 < 10 ≤ 4 < 1 ≤ 5

    The total number of issues (violations) found by SonarQube with a severity equal to BLOCKER.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Number of critical issues ( SQ_VIOLATIONS_CRITICAL )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 500 ≤ 2 < 100 ≤ 3 < 50 ≤ 4 < 10 ≤ 5

    The total number of issues (violations) found by SonarQube with a severity equal to CRITICAL.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Number of info issues ( SQ_VIOLATIONS_INFO )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 5000 ≤ 2 < 1000 ≤ 3 < 500 ≤ 4 < 100 ≤ 5

    The total number of issues (violations) found by SonarQube with a severity equal to INFO.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Number of major issues ( SQ_VIOLATIONS_MAJOR )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 500 ≤ 2 < 100 ≤ 3 < 50 ≤ 4 < 10 ≤ 5

    The total number of issues (violations) found by SonarQube with a severity equal to MAJOR.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Number of minor issues ( SQ_VIOLATIONS_MINOR )

    Provided by: SonarQube45

    Used by:

    Scale: 1 < 500 ≤ 2 < 100 ≤ 3 < 50 ≤ 4 < 10 ≤ 5

    The total number of issues (violations) found by SonarQube with a severity equal to MINOR.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5


Page generated by Alambic 3.3.3-dev on Fri Jul 20 10:13:11 2018.