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.



  • ITS issues changed lifetime ( ITS_CHANGED )

    Provided by: EclipseIts

    Used by:

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

    Number of updates on issues during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Update means an operation on a ticket changing its state, or adding information. Opening and closing a ticket are considered as updates. Identities of updaters are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar 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).

  • ITS issues changers lifetime ( ITS_CHANGERS )

    Provided by: EclipseIts

    Used by:

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

    Number of distinct identities updating tickets during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Update means an operation on a ticket changing its state, or adding information. Opening and closing a ticket are considered as updates. Identities of updaters are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar 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).

  • ITS issues closed lifetime ( ITS_CLOSED )

    Provided by: EclipseIts

    Used by:

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

    Number of issues closed during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Opened means that the ticket information was submitted to the issue traking system for the first time for that ticket. Identities of openers are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar 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). Number of lines are those calculated at the end of the period of analysis.

  • Number of issue closed during last month ( ITS_CLOSED_30 )

    Provided by: EclipseIts

    Used by: QM_ITS

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

    Number of distinct identities opening tickets during the last month in the issue tracking system.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Opened means that the ticket information was submitted to the issue traking system for the first time for that ticket. Identities of openers are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar 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). Number of lines are those calculated at the end of the period of analysis.

  • ITS issue closers lifetime ( ITS_CLOSERS )

    Provided by: EclipseIts

    Used by:

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

    Number of distinct identities closing tickets during during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Update means an operation on a ticket changing its state, or adding information. Opening and closing a ticket are considered as updates. Identities of updaters are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar 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).

  • ITS closers ( ITS_CLOSERS_30 )

    Provided by: EclipseIts

    Used by: QM_ITS

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

    Number of distinct identities closing tickets during the last month in the issue tracking system.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Update means an operation on a ticket changing its state, or adding information. Opening and closing a ticket are considered as updates. Identities of updaters are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar 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).

  • ITS issues opened lifetime ( ITS_OPENED )

    Provided by: EclipseIts

    Used by:

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

    Number of issues opened during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Opened means that the ticket information was submitted to the issue traking system for the first time for that ticket. Identities of openers are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar 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). Number of lines are those calculated at the end of the period of analysis.

  • ITS issue openers lifetime ( ITS_OPENERS )

    Provided by: EclipseIts

    Used by:

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

    Number of distinct identities opening tickets during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Opened means that the ticket information was submitted to the issue traking system for the first time for that ticket. Identities of openers are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar 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). Number of lines are those calculated at the end of the period of analysis.


Page generated by Alambic 3.3 on Wed Aug 23 23:03:16 2017.