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.



  • 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).


Page generated by Alambic 3.3.2 on Mon Oct 23 13:32:06 2017.